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. 1. **Primary Object Types**: The package primarily manages `Minter` objects, which represent an NFT collection and its associated minting rules, and `Nft` objects, which are the individual NFTs minted. It also uses `Collection` objects to group NFTs, and `SalePhase` objects to define different stages of a minting event. 2. **Public/Entry Functions**: * `init`: Initializes the package, creating and transferring a `Publisher` and a `Display<Nft>` object to the transaction sender. This sets up the metadata display for NFTs. * `add_phase`: Allows the `Minter` owner to add a new `SalePhase` to a `Minter` object, defining parameters like price, max sales, mints per user, start time, and an optional Merkle root for allowlisting. This function mutates the `phases` vector within the `Minter` object. * `remove_phase`:
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. Public/entry functions allow the Minter's owner to add, remove, and update "SalePhases" within a Minter object, which define different minting conditions (price, max sales, mints per user, start time, and an optional Merkle root for allowlisting). The `mint` function allows users to mint NFTs from a Minter object, provided they meet the current active SalePhase's conditions, including price, supply limits, and an optional Merkle proof for allowlisting. The `mint` function mutates the Minter object by updating the `minted` count, and tracking `user_buys` and `sale_phase_buys` in internal tables. It also creates a new Nft object and transfers it to the minter. Notable patterns include time-gating for sale phases, Merkle tree allowlisting,
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections. The `init` function sets up a `Publisher` and a `Display<Nft>` object, transferring ownership of both to the transaction sender. Public functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` for the NFT collection, defining sale parameters like price, max sales, mints per user, start time, and an optional Merkle root for allowlisting. The `mint` function allows users to mint NFTs from the collection, checking against the current active sale phase, supply limits, user-specific mint limits, and an optional Merkle proof for allowlist verification. It also handles payment for the NFT and updates the `Minter` object's minted count and user/phase buy records.
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` objects within a `Minter`. These functions mutate the `phases` vector of the `Minter` object. The `mint` function allows users to mint NFTs from a `Minter`, transferring SUI coins and creating 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 incorporates time-gating based on `SalePhase` start times and uses a Merkle tree root for allowlist verification (though the verification logic is complex and involves custom `compare_vector`, `hashPair`, `extract_vector`, and `processProof` functions). It also tracks `mints_
Wallets that share a funder, were co-funded by the same personal-scale source, or land in the same behavioral cluster. A heuristic, not proof of common control.
Tinted amber on the bubble map when they appear in the expanded graph.
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": "0xb0f1b7a30db0d6fbb434242d2b8310e9273c986c3618cf5a6faea4bdcc8adc37",
"n_tx": 72,
"n_successful_tx": 59,
"n_distinct_epochs": 11,
"n_distinct_sponsors": 0,
"first_seen_cp": 2475837,
"last_seen_cp": 25095907,
"first_seen_ts_ms": 1684062046011,
"last_seen_ts_ms": 1706791077964,
"total_gas_spent_mist": -275617060,
"n_self_sponsored_tx": 72,
"n_sponsored_tx": 0,
"gas_price_p50": 915,
"gas_price_p95": 931,
"active_hours_top24": [
11,
12,
9,
13,
16,
8,
4,
18,
23,
1,
5,
10,
19
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely W/Central Asia / India.