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 and minting NFTs, centered around the Minter object. The Minter object tracks collection details, total minted NFTs, and a vector of SalePhase objects, each defining a specific sale period with its own price, maximum sales, mints per user, start time, and an optional Merkle root for allowlisting. Public functions allow the Minter's owner to add, remove, and update these SalePhase configurations, ensuring only authorized changes. The core 'mint' function allows users to purchase NFTs, checking against the active sale phase's rules, including price, supply limits, per-user limits, and Merkle proof verification if an allowlist is active. Upon successful minting, an Nft object is created and transferred to the buyer, and the Minter's minted count and user/phase buy counts are updated.
This package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections. It also defines `Nft` objects for the NFTs themselves and `SalePhase` objects to configure minting stages. Public/entry functions allow the `Minter`'s owner to add, remove, and update `SalePhase` configurations, which dictate pricing, maximum sales, mints per user, and start times. The `mint` function allows users to mint NFTs from a `Minter` object, transferring SUI coins in exchange. This function mutates the `Minter` object by updating mint counts for the collection and individual users, and creates new `Nft` objects. Notable patterns include owner-gating for `add_phase`, `remove_phase`, and `update_phase` functions, ensuring only the `Minter`'s owner can modify sale phases. The `mint` function implements time-gating based on `SalePhase` start times and utilizes a Merkle tree verification (`verify`, `processProof`, `hashPair`)
This package defines a minter for NFTs, centered around the Minter and Nft object types. The Minter object manages the minting process, including sale phases, total supply, and tracking user and phase-specific mint counts. The Nft object represents the actual NFT with details like name, description, image URL, and attributes. Public functions allow the Minter's owner to add, remove, and update sale phases, which dictate pricing, maximum sales, mints per user, and start times, and can include a Merkle root for allowlist gating. The 'mint' entry function allows users to mint NFTs by paying SUI, verifying against the active sale phase's rules (including an optional Merkle proof for allowlisting), and updating mint counts. Notable patterns include time-gating for sale phases, optional allowlist gating via Merkle proofs, and the use of dynamic fields (Tables) to track user and sale phase specific mints. The 'init' function sets up a Display object for Nft metadata.
{
"wallet": "0x8c92242c62d16fc4d3cdb82ff5d55049d735d33f1e0ade0ac5a2e04472478b5d",
"n_tx": 356,
"n_successful_tx": 353,
"n_distinct_epochs": 14,
"n_distinct_sponsors": 0,
"first_seen_cp": 1738697,
"last_seen_cp": 15840269,
"first_seen_ts_ms": 1683292422471,
"last_seen_ts_ms": 1697571795016,
"total_gas_spent_mist": 475766620,
"n_self_sponsored_tx": 356,
"n_sponsored_tx": 0,
"gas_price_p50": 820,
"gas_price_p95": 990,
"active_hours_top24": [
10,
9,
11,
14,
7,
13,
17,
19,
5,
18,
6,
20,
15
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0.4,
"bot_signals": [
"timing_automation"
],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely W/Central Asia / India.
area + brightness = call volume; hover for detail