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, `my_minter`, primarily manages `Minter` objects, which represent NFT minting campaigns, and `Nft` objects, which are the NFTs themselves. The public/entry functions allow for the management of `SalePhase` objects within a `Minter`. `add_phase` adds a new sale phase to a minter, `remove_phase` removes a phase by name, and `update_phase` modifies an existing phase's parameters. These functions are gated by checking if the transaction sender is the `Minter`'s owner. The `mint` function allows users to mint NFTs from a `Minter` object, checking against active sale phases, user-specific mint limits, and overall sale limits. It also handles payment for the NFT. Notable patterns include: owner-gating for administrative functions (`add_phase`, `remove_phase`, `update_phase`), time-gating for sale phases (`start_time` in `SalePhase`), and the use of `Table` for dynamic fields to track `user
This package, my_minter, primarily manages Minter objects, which represent NFT collections and their associated sale phases. Public/entry functions allow the Minter's owner to add, remove, and update SalePhase configurations within a Minter object, which mutates the Minter's phases vector. The mint function allows users to mint NFTs from a Minter, decrementing the Minter's supply and incrementing minted count, user-specific buy counts, and sale phase buy counts. It also creates and transfers an Nft object to the minter. Notable patterns include owner-gating for phase management, time-gating for sale phases, and optional Merkle tree root verification for minting.
This package defines a system for managing and minting NFTs within a collection. The primary object types are `
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 individual NFTs. Public/entry functions allow the 'Minter' object's owner to add, remove, and update 'SalePhase' objects within a 'Minter'. 'SalePhase' objects define different minting stages with specific prices, maximum sales, mints per user, and start times. The 'mint' function allows users to mint NFTs, checking against the active sale phase, user-specific mint limits, and overall supply. It also handles payment and updates the minted count for the collection and the user. Notable patterns include time-gating for sale phases, dynamic fields (Table for user buys and sale phase buys), and a Merkle tree-like verification process for some sale phases (indicated by the 'root' field in 'SalePhase' and the 'verify' function). The 'init' function sets up a 'Publisher' and
This package manages Minter objects, which represent NFT collections and their associated sale phases. Public functions allow the Minter's owner to add, remove, and update sale phases, which are time-gated and can have specific pricing, maximum sales, and mints per user. The mint function allows users to mint NFTs from a Minter object, checking against the active sale phase's price, maximum sales, and per-user mint limits, and verifying a Merkle proof if required by the sale phase. It mutates the Minter's minted count, user_buys, and sale_phase_buys tables, and transfers SUI from the user to the Minter's owner. The package also defines an Nft object type and includes utility functions for Merkle tree verification (compare_vector, hashPair, extract_vector, processProof, verify) and number-to-string conversion (zero_padded, to_string).
{
"wallet": "0xe5eeca5943f1363215447188c27008a98194829348de4ce9dbfd46a9b23ff592",
"n_tx": 78,
"n_successful_tx": 75,
"n_distinct_epochs": 10,
"n_distinct_sponsors": 0,
"first_seen_cp": 1744682,
"last_seen_cp": 11236868,
"first_seen_ts_ms": 1683298611325,
"last_seen_ts_ms": 1692939790621,
"total_gas_spent_mist": 1511406472,
"n_self_sponsored_tx": 78,
"n_sponsored_tx": 0,
"gas_price_p50": 995,
"gas_price_p95": 1000,
"active_hours_top24": [
15,
19,
16,
10,
21,
12,
14,
4,
5,
7,
22,
11
],
"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.