all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
counterparties · funders · clusters
Move packages this wallet published on-chain — what it shipped, not what it used.
This package, `fetcher`, serves as a data retrieval utility for interacting with a `Pool` object. It defines a `TickData` struct to hold information about individual ticks within a pool. The `fetch_ticks` public function takes a vector of `u32` tick indices and a reference to a `Pool` object, then iterates through the provided indices to fetch the `sqrt_price`, `liquidity_gross`, and `liquidity_net` for each tick, returning them as a vector of `TickData`. The `fetch_update` public function takes a reference to a `Pool` object and returns a tuple containing the pool's reserves (two `u64` values), total liquidity (`u128`), current square root price (`u128`), and the current tick index (`I32`). The package primarily reads data from `Pool` and `Table` objects without mutating them.
This package defines a "HopGuess" object, which represents a unique guess with an ID, a number, a timestamp, and a launch guess string. The `init` function creates and transfers a `Publisher` object and a `Display<HopGuess>` object to the sender, which is a pattern for managing metadata. The `mint` entry function creates a new `HopGuess` object, assigning it a unique ID, a current number from the `MintState`, the current timestamp, and a provided launch guess string, then transfers it to the transaction sender. This `mint` function enforces that a minimum version is met, minting is enabled, and supply is available by calling functions on a shared `MintState` object. The `MintState` object, initialized with an `AdminCap` transferred to the sender, manages the minting process by tracking `min_version`, `minting_enabled`, `supply_available`, and `current_number`, which can be updated by an `AdminCap` holder.
This package, `fetcher`, primarily manages `TickData` objects, which represent tick information within a liquidity pool. It contains two public entry functions: `fetch_ticks` and `fetch_update`. `fetch_ticks` takes a starting tick index and a reference to a `Pool` object. It iterates through the pool's tick bitmap and tick information table to collect `TickData` objects, which include the tick index, square root price, gross liquidity, and net liquidity. This function effectively fetches a range of tick data from a given pool, stopping after 1000 ticks or when it exceeds the maximum tick. `fetch_update` takes a reference to a `Pool` object and returns the pool's reserves (two `u64` values), total liquidity (`u128`), current square root price (`u128`), and the current tick index (`I32`). This function provides a snapshot of key metrics from a specified liquidity pool. Notable patterns include the use of `table` for storing tick bitmap and tick
This package, `fetcher`, primarily interacts with `Pool` objects, which are generic over two type parameters, likely representing token types. It defines a `TickData` struct to store information about individual ticks within a pool. The `fetch_ticks` public function iterates through all possible ticks within a `Pool` (from `min_tick` to `max_tick`), checks if each tick is initialized, and if so, extracts its index, square root price, gross liquidity, and net liquidity, returning them as a vector of `TickData` objects. The `fetch_update` public function retrieves and returns the current reserves (two `u64` values), total liquidity (`u128`), square root price (`u128`), and the current tick index (`I32`) of a given `Pool` object. This package acts as a data retrieval layer for `Pool` and `Tick` information, without directly mutating any of these objects.
This Move package, `fetcher`, primarily interacts with `Pool` objects from the `pool` module. It defines a `TickData` struct to encapsulate information about individual ticks. The `fetch_ticks` public function takes a vector of `u32` tick indices and a reference to a `Pool` object. It iterates through the provided indices, calculates the square root price for each tick using `tick_math::get_sqrt_price_at_tick`, and retrieves the gross and net liquidity from the `Pool`'s internal tick table using `tick::get_liquidity_gross` and `tick::get_liquidity_net`. It then constructs and returns a vector of `TickData` objects. The `fetch_update` public function takes a reference to a `Pool` object and returns a tuple containing the pool's reserves (two `u64` values), its total liquidity (`u128`), its current square root price (`u128`), and its current tick index (`I32`). Neither function mutates
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
Where this wallet's SUI first came from, and what it seeded downstream. Observational: a CEX funder suggests a real/retail origin; a high-fanout non-CEX funder is a signal worth noting — not proof of anything.
{
"wallet": "0xc2c058dea3872029ed0c0427c75b258747407a0a6a8209cd8c7a17630cfccd06",
"n_tx": 134,
"n_successful_tx": 134,
"n_distinct_epochs": 39,
"n_distinct_sponsors": 0,
"first_seen_cp": 198209721,
"last_seen_cp": 280043746,
"first_seen_ts_ms": 1759856570742,
"last_seen_ts_ms": 1779829233517,
"total_gas_spent_mist": 517059314,
"n_self_sponsored_tx": 134,
"n_sponsored_tx": 0,
"gas_price_p50": 100,
"gas_price_p95": 556,
"active_hours_top24": [
20,
19,
15,
16,
14,
4,
21,
5,
13,
23,
17,
0,
1,
3,
9,
22
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).
area + brightness = call volume; hover for detail