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 collections, and 'Nft' objects, which are the individual NFTs. Public entry functions allow the Minter's owner to add, remove, and update 'SalePhase' configurations within a 'Minter' object, controlling minting parameters like price, maximum sales, and start times. The 'mint' function enables users to mint NFTs, checking against the active 'SalePhase' for price, supply limits, and user-specific mint limits, and also verifies a Merkle proof if a root hash is provided for the phase. Minting mutates the 'Minter' object by updating minted counts and user/phase buy records, and transfers SUI from the user to the Minter's owner. Notable patterns include time-gating for sale phases, Merkle tree allowlist gating, and dynamic fields for tracking user and phase-specific mint counts.
This package defines a system for managing and minting NFTs, primarily centered around the `Minter` object. The `Minter` object holds details about an NFT collection, including its supply, name, description, and a vector of `SalePhase` objects. Each `SalePhase` dictates pricing, maximum sales, mints per user, start time, and an optional Merkle root for allowlist gating. Public/entry functions allow the `Minter`'s owner to add, remove, and update `SalePhase` objects, modifying the `phases` vector within the `Minter`. The `mint` function allows users to mint NFTs. This function checks the current `SalePhase` based on the current timestamp, verifies Merkle proofs if an allowlist is active, manages per-user and per-phase mint limits, and handles payment. Notable patterns include: 1. **Admin Gating**: The `add_phase`, `remove_phase`, and `update_phase` functions are restricted to the `Minter`'s owner. 2
This package defines a minter for NFTs, centered around the 'Minter' object. The 'Minter' object manages a collection of NFTs, tracks minting progress, and defines sale phases. Public functions allow the minter's owner to add, remove, and update sale phases, which include price, max sales, mints per user, start time, and an optional Merkle root for allowlist gating. The 'mint' function allows users to purchase NFTs, checking against the current sale phase's rules, including time-gating, price, 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 specific buy counts are updated.
This package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections, and `Nft` objects, which are the individual NFTs. The `init` function initializes the package by creating a `Publisher` and a `Display<Nft>` object, transferring both to the transaction sender. Public/entry functions allow the `Minter`'s 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 mint NFTs from a `Minter` object, requiring payment in SUI and checking against sale phase rules like start time, maximum sales, and mints per user, and potentially a Merkle root for allowlist gating. Successful mints create a new `Nft` object and update the `minted` count in the `Minter`, as well as tracking user and phase-specific buys in dynamic tables.
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 the `Minter`'s owner to `add_phase`, `remove_phase`, and `update_phase` for the NFT sale. These functions modify the `phases` vector within the `Minter` object, which defines different sale stages with varying prices, maximum sales, mints per user, start times, and optional Merkle roots for allowlisting. The `mint` function allows users to purchase NFTs, transferring SUI coins to the minter, creating a new `Nft` object, and updating the `minted` count and user/phase-specific buy counts within the `Minter`. Notable patterns include owner-gating for phase management functions, time-gating for sale phases, and optional Merkle root verification for allowlist-gated sales within the `mint` function. The `Minter` object uses `Table`s to track
casualRule-based labels, conservative precision.
area + brightness = call volume; hover for detail
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": "0xde747ac256499aecd23774b8ee7ce7c6e7ec0202aa04ea4fc2d8e4d0d8f7e877",
"n_tx": 11,
"n_successful_tx": 11,
"n_distinct_epochs": 2,
"n_distinct_sponsors": 0,
"first_seen_cp": 1571261,
"last_seen_cp": 1659382,
"first_seen_ts_ms": 1683119920924,
"last_seen_ts_ms": 1683210693907,
"total_gas_spent_mist": 105380264,
"n_self_sponsored_tx": 11,
"n_sponsored_tx": 0,
"gas_price_p50": 1000,
"gas_price_p95": 1000,
"active_hours_top24": [
14,
13,
15,
16
],
"primary_archetype": "casual",
"labels": [
"casual"
],
"label_confidence": [
0.7
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely C. Europe / Africa / Middle East.