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 system for managing NFT collections and their minting processes. The primary object types are `Collection`, representing an NFT collection, `Minter`, which manages the minting logic for a specific collection, and `Nft`, representing an individual NFT. The `init` function initializes the module by creating a `Publisher` and a `Display<Nft>` object, transferring them to the sender. Public/entry functions include `add_phase`, `remove_phase`, and `update_phase`, which allow the `Minter`'s owner to manage different sale phases (e.g., presale, public sale) by adding, removing, or modifying `SalePhase` objects within the `Minter`'s `phases` vector. These functions mutate the `Minter` object. The `mint` function allows users to mint NFTs, checking against current sale phases, user-specific mint limits, and overall supply. It mutates the `Minter` object by updating `minted` count, `user_buys` and `sale_phase
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections, and `Nft` objects, which are the individual NFTs. The `init` function initializes a `Display` object for `Nft`s and transfers a `Publisher` object and the `Display` object to the transaction sender. Public entry functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` for sales, modifying the `phases` vector within the `Minter` object. The `mint` function allows users to purchase NFTs from the `Minter` object, checking sale phase conditions, updating `user_buys` and `sale_phase_buys` tables, and creating new `Nft` objects. Notably, the package includes Merkle tree verification logic (`compare_vector`, `hashPair`, `extract_vector`, `processProof`, `verify`) for potential allowlist gating, and it uses time-gating for sale phases.
This Sui package defines a module for managing NFT collections and minting processes. It primarily manages 'Collection' objects, which represent an NFT collection, and 'Minter' objects, which control the minting parameters for a specific collection. The 'init' function initializes the package by creating a 'Publisher' and a 'Display<Nft>' object, transferring them to the sender. Public/entry functions allow the 'Minter' owner to add, remove, and update 'SalePhase' objects, which define minting conditions like price, maximum sales, and start time, and are stored in a vector within the 'Minter' object. The 'mint' function allows users to mint NFTs, checking against the current sale phase's conditions, including time-gating and an optional Merkle tree root for allowlist verification (though the Merkle verification logic appears incomplete or incorrect in the provided IR). Minting involves transferring SUI coins to the minter's owner and creating a new 'Nft' object.
This package defines a system for managing NFT collections and minting. The primary object types are `Minter` (representing the minting configuration for a collection), `Collection` (the NFT collection itself), and `Nft` (individual NFTs). The `init` function initializes the package by claiming a `Publisher` object and creating a `Display` object for `Nft`s, then transfers both to the transaction sender. Public/entry functions allow the owner of a `Minter` object to manage sale phases: `add_phase` adds a new sale phase, `remove_phase` removes an existing phase, and `update_phase` modifies an existing phase. These functions mutate the `phases` vector within the `Minter` object. The `mint` function allows users to mint NFTs. It checks the current sale phase based on the `Clock` timestamp, verifies a Merkle proof if a root hash is provided for the phase, and updates the `minted` count in the `Minter` object, as well as `user_buys`
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": "0x5a4ca4cf2889fa012d039553941de873593bf56b10b3b85d5a00263a9935a645",
"n_tx": 98,
"n_successful_tx": 90,
"n_distinct_epochs": 20,
"n_distinct_sponsors": 0,
"first_seen_cp": 1838287,
"last_seen_cp": 69200165,
"first_seen_ts_ms": 1683396391664,
"last_seen_ts_ms": 1728994051766,
"total_gas_spent_mist": 703309012,
"n_self_sponsored_tx": 98,
"n_sponsored_tx": 0,
"gas_price_p50": 895,
"gas_price_p95": 950,
"active_hours_top24": [
7,
12,
17,
14,
15,
6,
18,
5,
8,
13,
3,
16,
4,
10,
11,
9,
20
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely W/Central Asia / India.
area + brightness = call volume; hover for detail