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 implements an Automated Market Maker (AMM) for token swaps on Sui. It manages `Pool` objects, which hold reserves of two different token types (`Ty0`, `Ty1`) and track liquidity provider (LP) tokens. A `Global` object stores a registry of all pools and collects protocol fees, while a `PoolRegistry` maps pool IDs to `LPMetadata`. Public/entry functions allow users to `create_pool_with_lp_tokens` (which also mints initial LP tokens), `add_liquidity` to existing pools, and `remove_liquidity` by burning LP tokens. These functions mutate the `Pool`'s reserves, LP supply, and `lp_balances` table, and the `Global` object's `total_protocol_fees`. Notable patterns include the use of dynamic fields (`Table`) for `pools` and `lp_balances`, and events (`PoolCreated`, `SwapEvent`, `LiquidityEvent`) for tracking pool activities. The `create_pool_with_lp_tokens` function
This package implements an Automated Market Maker (AMM) for token swaps. It primarily manages Pool objects, which represent liquidity pools for two token types (Ty0, Ty1), and LPToken objects, which represent a user's share of a liquidity pool. Public/entry functions allow users to create new liquidity pools (create_pool_with_lp_tokens), add liquidity to existing pools (add_liquidity), remove liquidity from pools (remove_liquidity), and manage their LP tokens by merging or splitting them (merge_lp_tokens, split_lp_token). These functions mutate the reserves of the Pool objects, the LP token supply, and user LP balances stored in a dynamic table within the Pool. The package also includes a Global object to track all pools and collect protocol fees in
This Sui package implements an Automated Market Maker (AMM) for token swaps and liquidity provision. The primary object types are `Global` (a singleton managing all pools and protocol fees) and `Pool<Ty0, Ty1>` (representing a liquidity pool for two token types). Public/entry functions allow users to create new liquidity pools (`create_pool_balance_based`), swap tokens (`swap_x_for_y`, `swap_y_for_x`), and manage liquidity (`add_liquidity`, `remove_liquidity`). These functions mutate the reserves within `Pool` objects, update `lp_balances`, and accrue fees to `Global` and `Pool` objects. Notable patterns include dynamic fields for LP balances within pools, a tiered fee structure for pool creation, and the use of `balance::join` and `balance::split` for managing token balances.
This package defines an Automated Market Maker (AMM) for swapping tokens. The primary object type it manages is the Pool, which holds reserves of two different token types (Ty0 and Ty1) and associated metadata. The public/entry functions allow users to create new pools and swap tokens. The create_pool function initializes a new Pool object, creates an associated LP token, and stores the pool's ID in a global table. The swap_x_for_y and swap_y_for_x functions enable users to exchange one token type for another within a pool, updating the pool's reserves and collecting fees. Notable patterns include the use of dynamic fields to store LP token metadata within the Pool object, and the management of various fees (flat fees, creator fees, and protocol fees) during swaps. The package also uses a Global object to track all pools and protocol-wide fees.
This package manages liquidity pools for token swaps. The primary object is the `Global` object, which holds a collection of `Pool` objects. The `Global` object also tracks a controller address, a beneficiary address, and a list of `PoolCreationTier`s. Public/entry functions allow a designated controller to pause/resume all operations or modify the controller address. A beneficiary can withdraw accumulated fees from a pool. New pools can be created, and liquidity can be added to or removed from existing pools. Tokens can be swapped between pools. Notable patterns include: - Admin Caps: The `controller` field in the `Global` object acts as an admin cap, gating access to `pause`, `resume`, and `modify_controller` functions. - Vault/Escrow: `Pool` objects hold `Balance`s of `coin_x`, `coin_y`, and their respective `fee_coin_x`, `fee_coin_y`, acting as vaults for these tokens. - Royalties: `PoolCreationTier`s define fees and
Wallets that share a funder, were co-funded by the same personal-scale source, or land in the same behavioral cluster. A heuristic, not proof of common control.
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": "0x38c703c9fca09d99bea7e87ce818646b9d5411dc3b4db4536f6a4676c729994a",
"n_tx": 146,
"n_successful_tx": 139,
"n_distinct_epochs": 7,
"n_distinct_sponsors": 0,
"first_seen_cp": 1634956,
"last_seen_cp": 271008584,
"first_seen_ts_ms": 1683185565676,
"last_seen_ts_ms": 1777650343963,
"total_gas_spent_mist": 2005080576,
"n_self_sponsored_tx": 146,
"n_sponsored_tx": 0,
"gas_price_p50": 740,
"gas_price_p95": 1000,
"active_hours_top24": [
6,
8,
5,
9,
7,
22,
10,
4,
1,
2,
15,
0,
21,
12,
11,
3
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Tinted amber on the bubble map when they appear in the expanded graph.
Top active hours by UTC. Circadian peak → likely E. Asia / Oceania.
area + brightness = call volume; hover for detail