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. It also defines `Collection` and `Nft` objects, but the core logic revolves around the `Minter`. The public/entry functions allow for the management of sale phases within a `Minter` object. `add_phase`, `remove_phase`, and `update_phase` are gated by the `Minter`'s owner, allowing them to modify the sale phases (price, max sales, mints per user, start time, name, and an optional Merkle root for allowlisting). The `mint` function allows users to mint NFTs. This function checks for time-gating based on the current sale phase's start time and potentially allowlist-gating using a Merkle proof (`processProof` and `verify` functions). It also tracks user-specific and phase-specific mint counts using dynamic fields (Tables) within the `Minter` object. The `mint` function mutates the `Minter`'s `
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections. It also defines `Nft` objects, representing individual NFTs, and `SalePhase` objects, which define parameters for different minting stages. The public/entry functions allow for the creation and management of these `Minter` objects and their associated sale phases. `add_phase`, `remove_phase`, and `update_phase` are restricted to the `Minter`'s owner and modify the `phases` vector within a `Minter` object, which contains `SalePhase` structs. The `mint` function allows users to mint NFTs from a `Minter` object, transferring SUI coins as payment and creating new `Nft` objects. It updates the `minted` count of the `Minter` and tracks user and phase-specific purchases using `Table` dynamic fields (`user_buys` and `sale_phase_buys`). Notable patterns include owner-gating for administrative functions (`add_phase`, `remove_
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 rules, and 'Nft' objects, which are the individual NFTs. The 'init' function initializes the package by claiming a 'Publisher' object and creating a 'Display' object for 'Nft's, transferring both to the transaction sender. Public/entry functions allow the 'Minter' owner to 'add_phase', 'remove_phase', and 'update_phase' for the minting process, which modifies the 'phases' vector within a 'Minter' object. The 'mint' function allows users to mint NFTs, which involves checking the current sale phase, verifying a Merkle proof if a root hash is present, and transferring SUI coins. Notable patterns include: owner-gating for 'add_phase', 'remove_phase', and 'update_phase' functions; time-gating for minting based on 'start_time' in 'SalePhase' objects; and
This Sui package defines a minter for NFTs. It manages `Minter` objects, which control the minting process, and `Nft` objects, which are the minted tokens. Public/entry functions allow the `Minter` owner to add, remove, and update `SalePhase` configurations, which dictate pricing, maximum sales, and per-user mint limits. The `mint` function allows users to mint NFTs by paying SUI, subject to the current `SalePhase` rules, including an optional Merkle tree root for allowlist gating. Minting updates the `Minter`'s minted count and user/phase-specific buy counts. Notable patterns include: - Admin gating: `add_phase`, `remove_phase`, and `update_phase` can only be called by the `Minter`'s owner. - Time-gating: The `mint` function checks the current timestamp against the `start_time` of the active `SalePhase`. - Allowlist gating: `SalePhase` objects can contain a Merkle
This Sui package, `my_minter`, primarily manages `Minter` and `Nft` objects. A `Minter` object represents a collection and contains details like its name, description, owner, total supply, minted count, and a vector of `SalePhase` objects. Each `SalePhase` defines a specific sale period with a price, maximum sales, mints per user, start time, name, and an optional Merkle root for allowlisting. The public/entry functions allow the `Minter`'s owner to manage sale phases: `add_phase` inserts a new `SalePhase`, `remove_phase` deletes an existing one by name, and `update_phase` modifies an existing phase's parameters. The `mint` function allows users to mint NFTs from the collection. This function checks the current time against the active `SalePhase`'s `start_time` for time-gating, verifies Merkle proofs for allowlist gating (if a root is present), and updates the `minted` count for the collection,
True specific-lot profit from 2 closed buy→sell round-trips of the same NFT (realized_roundtrip), wash-adjusted, valued at each leg's trade-hour USD. Excludes still-held inventory (that's unrealized).
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
flipperRule-based labels, conservative precision.
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": "0x3139dd6b0cdb1d06fe964d94658545716481742927e2172118cfb10a2aeaaa62",
"n_tx": 346,
"n_successful_tx": 332,
"n_distinct_epochs": 21,
"n_distinct_sponsors": 0,
"first_seen_cp": 1841664,
"last_seen_cp": 28815864,
"first_seen_ts_ms": 1683399954989,
"last_seen_ts_ms": 1710494067515,
"total_gas_spent_mist": 2900803652,
"n_self_sponsored_tx": 346,
"n_sponsored_tx": 0,
"gas_price_p50": 950,
"gas_price_p95": 990,
"active_hours_top24": [
16,
13,
21,
6,
11,
10,
19,
20,
17,
14,
18,
15,
22,
5,
12,
9,
8,
7,
4
],
"primary_archetype": "flipper",
"labels": [
"flipper"
],
"label_confidence": [
0.68
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).