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 minting. It primarily manages Minter objects, which represent an NFT collection and its associated minting logic, and Nft objects, which are the NFTs themselves. The `init` function initializes a `Display<Nft>` object, which is likely used for displaying NFT metadata. The `add_phase`, `remove_phase`, and `update_phase` entry functions allow the Minter's owner to manage different sale phases for the NFT collection, each with its own price, maximum sales, mints per user, start time, and an optional Merkle root for allowlist gating. The `mint` function allows users to mint NFTs, checking against the current sale phase's rules, including time-gating, price, and Merkle proof verification for allowlists. It also tracks the number of NFTs minted per user and per sale phase.
This package defines a minter for NFTs. The primary object types are `Minter`, which manages the minting process, `Collection`, representing an NFT collection, and `Nft`, representing an individual NFT. The `init` function initializes the package by claiming a `Publisher` capability and creating a `Display` object for `Nft`s, then transferring both to the transaction sender. Public entry functions include `add_phase`, `remove_phase`, and `update_phase`, which allow the `Minter`'s owner to manage sale phases by adding, removing, or modifying `SalePhase` objects within the `Minter`'s `phases` vector. These functions mutate the `Minter` object. The `mint` function allows users to mint NFTs, checking against sale phase rules (time, price, max sales, mints per user, and an optional Merkle root for allowlisting). Notable patterns include owner-gating for phase management functions, time-gating for minting based on `SalePhase` start times, and an optional Mer
This package defines a system for managing and minting NFTs. The primary object types are Collection, Minter, and Nft. The Minter object manages the minting process, including sale phases and user-specific purchase limits. The public/entry functions allow the Minter's owner to add, remove, and update sale phases, and for users to mint NFTs. The mint function checks for time-gating and optional Merkle tree root verification for allowlist access, and updates the number of NFTs minted per user and per sale phase. The package also includes helper functions for string conversion, vector manipulation, and Merkle proof verification.
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 sale phases, and `Nft` objects, which are the individual NFTs. Public functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` for the NFT sale, modifying the `phases` vector within the `Minter` object. The `mint` function allows users to mint NFTs by paying a specified price, which updates the `minted` count in the `Minter` and the `user_buys` and `sale_phase_buys` tables. Notable patterns include: 1. Admin Gating: `add_phase`, `remove_phase`, and `update_phase` functions are restricted to the `Minter`'s owner. 2. Time-Gating: The `mint` function checks the current timestamp against the `start_time` of the active sale phase. 3. Merkle Tree
This package defines a system for managing NFT collections and minting NFTs. The primary object types are Collection, Minter, and Nft. The Collection object represents an NFT collection, while the Minter object manages the minting process for a specific collection, including sale phases and user-specific mint counts. The Nft object represents an individual NFT with its metadata. Public/entry functions allow the minter's owner to add, remove, and update sale phases within a Minter object, which mutates the Minter's phases vector. The `mint` function allows users to mint NFTs from a Minter object, which mutates the Minter's minted count, user_buys, and sale_phase_buys tables, and transfers SUI coins. It also creates and transfers a new Nft object to the minter. Notable patterns include: owner-gating for `add_phase`, `remove_phase`, and `update_phase` functions, ensuring only the minter's owner can modify sale phases. Time-gating is present
botflipperRule-based labels, conservative precision.
{
"wallet": "0x4e860342f9f1bcd5754f011d562c59ef1bdddd5666ce0a9a22d09281cc54ec27",
"n_tx": 2965,
"n_successful_tx": 2932,
"n_distinct_epochs": 79,
"n_distinct_sponsors": 3,
"first_seen_cp": 1640190,
"last_seen_cp": 148124125,
"first_seen_ts_ms": 1683190966237,
"last_seen_ts_ms": 1747911924906,
"total_gas_spent_mist": 4751081532,
"n_self_sponsored_tx": 2910,
"n_sponsored_tx": 55,
"gas_price_p50": 820,
"gas_price_p95": 930,
"active_hours_top24": [
16,
20,
15,
19,
14,
17,
21,
18,
10,
23,
13,
22,
9,
11,
12,
8,
2,
1,
0,
7
],
"primary_archetype": "bot",
"labels": [
"bot",
"flipper"
],
"label_confidence": [
0.8265896,
0.5925
],
"bot_score": 0.4,
"bot_signals": [
"timing_automation"
],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely Atlantic / E. South America.
area + brightness = call volume; hover for detail