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 Sui package defines a staking mechanism for "Stork" NFTs, managed by a singleton `StakingVault` object. Users can stake their Stork NFTs from a Kiosk, which records the staking timestamp and the owner's address using dynamic fields and tables within the `StakingVault`. Staked NFTs are stored as dynamic object fields on the `StakingVault`'s ID. Users can unstake their Stork NFTs, receiving them back into their Kiosk, and claim `STORKTOKEN` rewards based on the staking duration, which are withdrawn from a `ProtocolTreasury` and transferred to the user. The `StakingVault` tracks the total number of staked Storks and uses tables to manage owners, reverse owners (address to staked IDs), Kiosk IDs, and staking timestamps for each Stork. All public/entry functions check that the `StakingVault`'s version is 0, implying a potential upgrade mechanism or a single, immutable version.
This Sui package manages a primary object type called `Stork`, which represents an NFT with fields for `id`, `name`, `description`, `url`, and `attributes`. The `init` function initializes the collection, minting capabilities, display information, creator royalties, and transfer policies, sharing several objects publicly and transferring administrative capabilities to the deployer. Public entry functions allow users to `mint_nft` into a `Warehouse`, `reveal_nft` (or `reveal_nft_two`) to update an NFT's metadata (URL, attributes, name, description) while it's borrowed from a Kiosk, `burn_nft`, and `enable_orderbook`/`disable_orderbook` to control orderbook protection. The package also includes functions to `enable_staking` and `disable_staking` for `Stork` NFTs, which are gated by the `Publisher` object. Notable patterns include the use of `MintCap` for controlled minting, `Publisher` for administrative gating, `RoyaltyDomain` for creator royalties, `TransferPolicy
This Sui package defines a staking mechanism for "Stork" NFTs and manages a "STORKTOKEN" cryptocurrency. The primary objects are `StakingVault` which tracks staked NFTs, their owners, and staking timestamps, and `ProtocolTreasury` which holds the STORKTOKEN supply for staking rewards and airdrops. The `stake` entry function allows users to stake their Stork NFTs from a Kiosk, recording the NFT's ID, the staker's address, and the staking timestamp in the `StakingVault` using dynamic object fields and tables. The `unstake` entry function enables users to retrieve their Stork NFTs and claim STORKTOKEN rewards from the `ProtocolTreasury`, calculating rewards based on the staking duration and transferring the STORKTOKEN to the user and the NFT back to their Kiosk. Notably, the `unstake` function includes checks to ensure the caller is the owner of the staked NFT and the Kiosk, and it caps the reward at the remaining staking supply.
This Sui package defines a staking mechanism for "Stork" NFTs and manages a "STORKTOKEN" cryptocurrency. The primary object types are StakingVault, which stores staked Stork NFTs and their associated data, and ProtocolTreasury, which manages the STORKTOKEN supply for staking and airdrops. Public and entry functions allow users to stake individual Stork NFTs (stake), stake multiple Stork NFTs (stake_all), unstake individual Stork NFTs (unstake), unstake all their staked Stork NFTs (unstake_all), and claim earned STORKTOKEN (claim). Staking functions transfer Stork NFTs from a user's Kiosk into the StakingVault, recording the owner and timestamp. Unstaking functions return the Stork NFT to the user's Kiosk and distribute calculated STORKTOKEN rewards from the ProtocolTreasury. Claiming rewards also distributes STORKTOKEN from the ProtocolTreasury based on the staking duration. Notable patterns include the use of dynamic object fields within the StakingVault to store individual Stork NFTs, and tables to map
This Sui package, "stork," defines and manages a primary object type called `Stork`, which represents an NFT with fields for `id`, `name`, `description`, `url`, and `attributes`. The `init` function initializes the collection, mint capabilities, display information, creator royalties, and various policies (transfer, borrow, withdraw) for `Stork` NFTs, transferring administrative caps to the deployer and sharing core objects publicly. Public entry functions allow for minting new `Stork` NFTs into a `Warehouse`, revealing or updating NFT metadata (name, description, URL, attributes) for NFTs held in a `Kiosk`, and burning `Stork` NFTs. The package also includes functions to enable or disable orderbook protection and enable staking for `Stork` NFTs. Notable patterns include the use of `MintCap` for controlled minting, `Publisher` for administrative actions, `TransferPolicy` for royalty enforcement, and `Allowlist` for access control.
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
botnft_whalenft_collectorRule-based labels, conservative precision.
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": "0x015ef4a7d4800fd1c8e557add32880ff6e945fa5beaf00cd6540deb03c337b41",
"n_tx": 5558,
"n_successful_tx": 5537,
"n_distinct_epochs": 130,
"n_distinct_sponsors": 2,
"first_seen_cp": 1612279,
"last_seen_cp": 112043918,
"first_seen_ts_ms": 1683162173767,
"last_seen_ts_ms": 1739417490861,
"total_gas_spent_mist": 162173023144,
"n_self_sponsored_tx": 5555,
"n_sponsored_tx": 3,
"gas_price_p50": 895,
"gas_price_p95": 895,
"active_hours_top24": [
19,
18,
17,
2,
20,
1,
21,
23,
15,
16,
14,
22,
3,
5,
0,
4,
12,
13,
6,
7,
8,
11
],
"primary_archetype": "nft_collector",
"labels": [
"bot",
"nft_whale",
"nft_collector"
],
"label_confidence": [
0.8935902,
0.36235198,
0.95
],
"bot_score": 0.4,
"bot_signals": [
"timing_automation"
],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely N. America (Central–Eastern).
area + brightness = call volume; hover for detail