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 vault system for managing staked assets and issuing a proportional token (pSui). The primary object types are `GlobalConfig` (admin settings), `Pools` (a registry of all staking pools), `PoolInfo<Ty0>` (details for a specific staking pool of type `Ty0`), and `UserRegistry<Ty0>` (user-specific staking data). Public/entry functions allow an admin to `create_pool` by providing metadata and linking it to a `SpoolAccount` for staking, and users can `deposit` assets into a pool, which mints pSui tokens to them and updates their staked amount. The `deposit` function also calls an internal `harvest` function, which likely distributes rewards, and it calculates the amount of pSui to mint based on the pool's balance and the total pSui supply. Notable patterns include admin-gating for `create_pool`, dynamic object fields to store `ListedPool` objects, and the use of a `PSUICONTROLLER` to manage the pS
This package manages Sacabam NFTs, which have a name, description, URL, and attributes. The init function creates a Collection, MintCap, Publisher, Display, RoyaltyDomain, TransferPolicy, and an Inventory object, sharing the Collection, TransferPolicy, Inventory, and an Allowlist publicly, and transferring the MintCap, Publisher, AllowlistOwnerCap, and TransferPolicyCap to the deployer. The mint_nft entry function allows minting new Sacabam NFTs into an Inventory object, incrementing the supply. The reveal function allows an authorized Publisher to link Fossil IDs to Sacabam IDs within the Inventory's revelation table, marking them as revealed. The redeem_nft function burns a Fossil, retrieves the corresponding Sacabam from the Inventory's warehouse based on the revelation table, and deposits it into a Kiosk. The package also includes functions to enable and disable orderbook protection for Sacabam NFTs, using a Publisher to control these actions.
This Sui package manages "Sacabam" NFTs, which are unique digital collectibles with a name, description, URL, and attributes. The `init` function creates a collection, mint cap, display object, royalty domain, transfer policy, and an orderbook for Sacabam NFTs, sharing most of these objects publicly. It also initializes an `Inventory` object, which acts as a warehouse for Sacabam NFTs and stores revelation data. The `mint_nft` entry function allows authorized users (holding a `MintCap`) to mint new Sacabam NFTs and deposit them into the `Inventory` warehouse. The `reveal` function allows a `Publisher` to link a `Fossil` ID to a `Sacabam` ID within the `Inventory`, marking the Sacabam as "revealed." The `redeem_nft` function allows users to burn a `Fossil` to redeem a revealed `Sacabam` NFT from the `Inventory` and deposit it into a Kiosk. The `enable_orderbook` and `disable_orderbook` functions
This Sui package defines a system for managing and revealing NFT collections, primarily focusing on the 'Sacabam' NFT type. The 'sacabam' module initializes a collection, display, royalty domain, transfer policy, and an orderbook for 'Sacabam' NFTs, transferring ownership caps to the deployer. Public functions allow minting new 'Sacabam' NFTs into an 'Inventory' object, revealing 'Sacabam' NFTs by mapping 'Fossil' IDs to 'Sacabam' IDs within the 'Inventory', and redeeming 'Fossil' NFTs for revealed 'Sacabam' NFTs, depositing them into a Kiosk. The 'warehouse' module provides generic storage for NFTs, using dynamic object fields to manage deposited NFTs and track the total count. Notable patterns include the use of dynamic object fields for NFT storage within the 'Inventory' and 'Warehouse', and the implementation of a royalty strategy and transfer allowlist for 'Sacabam' NFTs.
This Sui package defines a strategy for managing liquidity pool (LP) tokens, primarily through the `Strategy` object. Public/entry functions allow for creating new strategies, harvesting rewards from an associated liquidity pool (which involves collecting token and FLX rewards, swapping them on FlowX, adding liquidity back to the pool, and collecting to the vault), and depositing LP tokens into a strategy. These functions mutate the `Strategy` object's internal state, including earned tokens and the associated `Vault`, and also interact with external modules like `operator`, `router`, and `vault`. Notable patterns include the use of dynamic fields to store `Strategy` objects keyed by `StrategyDfKey`, an `AdminCap` for privileged operations like creating strategies, and a `State` object that tracks the number of strategies and a paused status, which gates the `deposit` function. The `harvest` process is multi-step, managed by a `HarvetReceipt` object, and involves a performance fee deducted from harvested rewards before they are deposited into the strategy's vault.
botRule-based labels, conservative precision.
area + brightness = call volume; hover for detail
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": "0xebe561651702e42544dba42e439f39c3ed86de8b24b92e0ae0b9ac2463336585",
"n_tx": 3475,
"n_successful_tx": 3467,
"n_distinct_epochs": 8,
"n_distinct_sponsors": 0,
"first_seen_cp": 15715417,
"last_seen_cp": 19289951,
"first_seen_ts_ms": 1697447828476,
"last_seen_ts_ms": 1701002822645,
"total_gas_spent_mist": 4411046796,
"n_self_sponsored_tx": 3475,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
9,
10,
11,
12,
8,
7,
4,
3,
6,
15,
5,
2
],
"primary_archetype": "bot",
"labels": [
"bot"
],
"label_confidence": [
0.92918825
],
"bot_score": 0.4,
"bot_signals": [
"timing_automation"
],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely E. / SE Asia.