all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
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 defines a data fetching utility for a decentralized exchange (DEX) or liquidity pool. It primarily manages `CetusTick` and `CetusStatus` objects, which are emitted as events. The single entry function, `fetcher`, takes a reference to a `Pool` object and a vector of `u32` tick indices. It iterates through the provided tick indices, retrieves tick information (sqrt_price, liquidity_net, liquidity_gross) from the `Pool`'s `TickManager`, and emits a `CetusTick` event for each. Finally, it fetches the current tick index, square root price, and liquidity of the `Pool` and emits a `CetusStatus` event. There are no notable patterns like signature/allowlist gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties.
This Sui package, `bluefin`, primarily manages `BluefinPoolStatus` objects, which store an index, square root price, liquidity, and amounts of two assets (amount_a, amount_b). The single public entry function, `fetch_all`, takes a reference to a `Pool` object (from the `pool` module) and returns a vector of `TickInfo` (from the `tick` module) and a `BluefinPoolStatus` object. This function iterates through a range of tick indices, checks if each tick is initialized within the `TickManager` associated with the `Pool`, and collects the initialized tick indices. It then fetches detailed `TickInfo` for these collected indices and constructs a `BluefinPoolStatus` object using current data from the input `Pool`, including its current tick index, square root price, liquidity, and coin reserves. There are no notable patterns like signature/allowlist gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties in this module.
This package manages a primary object type called CoventNFT, which has fields for an ID, name, and image. The init function creates a new collection for CoventNFTs, a MintCap, a Publisher object, and various transfer policies including royalty and P2P listing enforcement. It also initializes a display object for the NFTs and sets up creator royalties. The mint_nft and mint_nft_large entry functions allow users to mint new CoventNFTs into a Kiosk, incrementing the supply via the MintCap. The init_policies function initializes an allowlist and an orderbook for CoventNFTs, and sets up a borrow request policy. The update_name function allows a Publisher to modify the name of an NFT within a Kiosk by borrowing it. Finally, enable_orderbook and disable_orderbook allow a Publisher to control the protection settings of the CoventNFT orderbook. The package utilizes admin caps (MintCap, Publisher, PolicyCap, AllowlistOwnerCap), royalties, and an allowlist for transfer policies.
This package primarily manages `BluefinPoolStatus` and `BluefinTick` objects, which are data structures representing the state of a liquidity pool and individual ticks within it, respectively. The single public entry function, `fetch_all`, takes a reference to a `Pool` object (from the `pool` module) and returns a vector of `BluefinTick` objects and a `BluefinPoolStatus` object. This function iterates through a range of tick indices, retrieving `TickInfo` from the `pool`'s `TickManager` and populating the `BluefinTick` vector with relevant data (index, liquidity_gross, liquidity_net). It also extracts the current tick index, square root price, liquidity, and coin reserves from the `Pool` object to construct the `BluefinPoolStatus`. The package uses external modules `pool` and `tick` for core pool and tick management functionalities, and `i128` and `i32` for integer operations. There are no explicit signature/allowlist gating, time-gating,
This Sui package, 'flowx', primarily manages liquidity pools and their associated tick information. It defines two primary object types: 'FlowXPoolTick' and 'FlowXPoolStatus', which are used to emit events. The public 'fetcher' function takes a 'PoolRegistry' object, a pool ID, and a vector of tick indices. It then borrows a specific pool from the registry and calls an internal function. This internal function iterates through the provided tick indices, retrieves the liquidity net and gross for each tick from the pool's tick table, and emits a 'FlowXPoolTick' event for each. Finally, it retrieves the current tick index, square root price, and total liquidity of the pool, emitting a 'FlowXPoolStatus' event. The package does not appear to mutate any on-chain objects directly through its public functions, but rather emits events containing pool and tick data. There are no explicit signature/allowlist gating, time-gating, admin caps, vault/escrow, or royalties patterns visible in the provided IR.
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": "0x4466fe25550f648a4acd6823a90e1f96c77e1d37257ee3ed2d6e02a694984f73",
"n_tx": 1061,
"n_successful_tx": 967,
"n_distinct_epochs": 167,
"n_distinct_sponsors": 1,
"first_seen_cp": 30347279,
"last_seen_cp": 190016503,
"first_seen_ts_ms": 1712018356487,
"last_seen_ts_ms": 1757892650019,
"total_gas_spent_mist": 11693406300,
"n_self_sponsored_tx": 1060,
"n_sponsored_tx": 1,
"gas_price_p50": 750,
"gas_price_p95": 758,
"active_hours_top24": [
17,
3,
22,
23,
18,
2,
19,
0,
16,
7,
21,
20,
15,
4,
14,
1,
12,
13,
5,
9,
6,
11
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely N. America (Central–Eastern).