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 and minting NFTs. It 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 collection. These functions modify the `phases` vector within a `Minter` object, which dictates the sale parameters. The `mint` function allows users to mint NFTs from a `Minter` object, transferring SUI coins as payment. This function mutates the `minted` count of the `Minter`, and updates `user_buys` and `sale_phase_buys` tables to track minting limits. Notable patterns include: 1. **Admin Gating**: The `add_phase`, `remove_phase`, and `update_phase` functions are restricted to the `Minter`'s `owner`. 2. **Time-Gating**: The `mint`
This package manages KEEPSAKE objects, which are NFTs with a name, description, URL, and attributes. The `init` function initializes the collection, creates and shares multiple transfer policies (one enforcing an allowlist, another for P2P listings, and a generic one), and transfers the Publisher, MintCap, and a Display object to the sender. The `create` function adds display and royalty domains to a KEEPSAKE collection and sets up a royalty strategy. The `mint` function creates a new KEEPSAKE NFT, increments the supply, and emits mint events. The `mint_to` and `mint_many` entry functions allow minting multiple KEEPSAKE NFTs, either to a specific address or returned as a vector, respectively. The `mint_launchpad` entry function mints multiple KEEPSAKE NFTs and adds them to a listing. Finally, the `burn` function deletes a KEEPSAKE NFT. The package utilizes a witness pattern for certain operations and integrates with external modules for royalties, listings, and transfer policies, including
This package manages KEEPSAKE NFTs, which have a UID, name, description, URL, and attributes. The `init` function creates and shares a Collection, a Publisher, and several TransferPolicy objects, including one enforcing a transfer allowlist and another for P2P listings. It also creates and transfers a MintCap and a Display object to the deployer. Public functions allow creating new royalty and display information domains for the collection, and minting single or multiple KEEPSAKE NFTs. NFTs can be minted directly to an address, or added to a Listing object. There are also functions to borrow and return KEEPSAKE NFTs or their fields via BorrowRequest objects. The `burn` function allows destroying a KEEPSAKE NFT. The package utilizes transfer policies for royalties, allowlists, and P2P listings, and issues MintCap objects for controlled minting.
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.
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": "0x37f14ce3e9a016b11685a26109b9bffccff37ba2c127b9c7759973184991f908",
"n_tx": 29,
"n_successful_tx": 29,
"n_distinct_epochs": 7,
"n_distinct_sponsors": 0,
"first_seen_cp": 2677386,
"last_seen_cp": 21485028,
"first_seen_ts_ms": 1684282385570,
"last_seen_ts_ms": 1703181656774,
"total_gas_spent_mist": 315379080,
"n_self_sponsored_tx": 29,
"n_sponsored_tx": 0,
"gas_price_p50": 915,
"gas_price_p95": 915,
"active_hours_top24": [
13,
14,
1,
6,
0,
12,
23,
10,
11,
18
],
"primary_archetype": "casual",
"labels": [
"casual"
],
"label_confidence": [
0.7
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).