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. It primarily manages `Minter` objects, which represent an NFT collection's minting configuration, and `Nft` objects, which are the actual NFTs. The `init` function initializes the package by creating a `Publisher` object for the `Nft` type and a `CreatorCapability` object, transferring both to the transaction sender. Public/entry functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` for the NFT collection, which modify the `phases` vector within the `Minter` object. These functions are gated by checking if the transaction sender is the `Minter`'s owner. The `mint` function allows users to mint NFTs. It checks the current time against sale phases, verifies a Merkle proof if a root is present in the active phase, and updates the `minted` count, `user_buys` table, and `sale_phase_buys` table within the `Minter` object
This package defines a system for managing and minting NFTs. The primary object types are `Minter`, which represents an NFT collection and its minting configuration, `SalePhase`, which defines different stages of a mint with specific pricing and limits, and `Nft`, which is the actual NFT object. Public functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` to manage the minting schedule and parameters. The `mint` function allows users to purchase NFTs, checking against sale phase rules, user-specific limits, and an optional Merkle tree root for allowlist gating. The `mint` function mutates the `Minter` object by updating mint counts and transfers the newly created `Nft` to the minter. Notable patterns include time-gating for sale phases, an optional Merkle tree root for allowlist gating, and dynamic fields (`user_buys` and `sale_phase_buys` tables) within the `Minter` object to track minting statistics. An `init`
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections and their associated sale phases. It also defines `Nft` objects, which are the individual NFTs minted. The `init` function initializes the package by creating a `Publisher` object, a `Display<Nft>` object for NFT metadata, and a `CreatorCapability` object, transferring all three to the transaction sender. The `add_phase`, `remove_phase`, and `update_phase` entry functions allow the `Minter`'s owner to manage the sale phases of an NFT collection, including price, max sales, mints per user, start time, and an optional Merkle root for allowlist gating. The `mint` entry function allows users to mint NFTs from a `Minter` object, checking against the current sale phase's rules (time, supply, user limits, and Merkle proof if applicable) and transferring the SUI payment to the `Minter`'s owner. Notable patterns include: - **Admin Gating
{
"wallet": "0x3707bdadcb2e515c4d1fd7aacaa8461b1e0dc2252482101545d1f271bdda76d2",
"n_tx": 54,
"n_successful_tx": 54,
"n_distinct_epochs": 14,
"n_distinct_sponsors": 0,
"first_seen_cp": 98976994,
"last_seen_cp": 115917609,
"first_seen_ts_ms": 1736262980414,
"last_seen_ts_ms": 1740356387311,
"total_gas_spent_mist": 576849100,
"n_self_sponsored_tx": 54,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
1,
3,
0,
15,
2,
22,
19,
16,
17
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely N. America (Central–Eastern).