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. It primarily manages 'Minter' objects, which represent an NFT collection and its associated minting configuration, and 'Nft' objects, which are the actual NFTs. The 'init' function initializes a 'Publisher' and a 'Display' object for 'Nft's, transferring them to the transaction sender. Public/entry functions allow the 'Minter' owner to 'add_phase', 'remove_phase', and 'update_phase' for the minting process, modifying the 'phases' vector within the 'Minter' object. The 'mint' function allows users to mint NFTs, checking against the current active sale phase, user-specific mint limits, and total sales limits, and requires payment in SUI. Notable patterns include time-gating for sale phases, dynamic fields for user and sale phase buy counts (using 'Table' objects), and an admin cap for the 'Minter' owner to manage sale phases. The 'verify' function suggests a Merkle tree-based allow
This package defines a system for managing and minting NFTs within a collection. The primary object types are `Collection` (representing an NFT collection), `Minter` (managing the minting process for a collection), and `Nft` (the individual NFT object). Public/entry functions allow the `Minter` owner to manage sale phases: `add_phase` adds a new sale phase, `remove_phase` removes an existing phase by name, and `update_phase` modifies an existing phase's parameters. The `mint` function allows users to mint NFTs, which involves checking sale phase conditions (time-gating, user-specific mint limits, overall sale limits, and an optional Merkle tree root for allowlist gating). Notable patterns include: owner-gating for `add_phase`, `remove_phase`, and `update_phase` functions, time-gating for minting based on `SalePhase` start times, optional allowlist gating using a Merkle tree root in `SalePhase`, and dynamic fields for tracking user and sale phase
This Sui package defines a minter for NFTs. The primary object types it manages are `Collection`, `Minter`, and `Nft`. The `init` function initializes the package by claiming a `Publisher` capability and creating a `Display<Nft>` object, transferring both to the transaction sender. The `add_phase`, `remove_phase`, and `update_phase` entry functions allow the `Minter` owner to manage sale phases, which include price, max sales, mints per user, start time, name, and an optional Merkle root for allowlisting. These functions mutate the `phases` vector within the `Minter` object. The `mint` entry function allows users to mint NFTs. It checks the current time against sale phase start times, verifies Merkle proofs if a root is present for the phase, and updates user and phase-specific mint counts in dynamic tables (`user_buys` and `sale_phase_buys`) within the `Minter` object. It also creates a new `Nft` object and transfers it to
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections. It also defines `Nft` objects for the individual NFTs. The `init
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections, and `Nft` objects, which are the individual NFTs. Public/entry functions allow for the creation and management of "sale phases" within a `Minter` object. `add_phase`, `remove_phase`, and `update_phase` are gated by the `Minter`'s owner and modify the `phases` vector within the `Minter` object. The `mint` function allows users to mint NFTs from a `Minter` object, checking against sale phase conditions (time, price, max sales, mints per user, and an optional Merkle root for allowlisting). Minting mutates the `minted` count, `user_buys` table, and `sale_phase_buys` table within the `Minter`, and transfers a newly created `Nft` object to the minter. Notable patterns include: owner-gating for administrative functions, time-gating for sale phases, allowlist-
{
"wallet": "0xc61e8952bb859c21cb472eecf14e7d8300e0729e935b02ad369329e963d99840",
"n_tx": 126,
"n_successful_tx": 123,
"n_distinct_epochs": 15,
"n_distinct_sponsors": 0,
"first_seen_cp": 1726969,
"last_seen_cp": 6961578,
"first_seen_ts_ms": 1683280312560,
"last_seen_ts_ms": 1688639016124,
"total_gas_spent_mist": 2180868020,
"n_self_sponsored_tx": 126,
"n_sponsored_tx": 0,
"gas_price_p50": 915,
"gas_price_p95": 1000,
"active_hours_top24": [
15,
12,
23,
16,
22,
10,
18,
14,
17,
20,
19,
9,
8,
21,
13
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely UK / W. Europe / W. Africa.