all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
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 manages a primary object type called `Demo`, which represents an NFT with a name, description, URL, and attributes. The `init` function initializes the collection, sets up display information, defines creators, establishes royalty policies (using a basis points strategy), and creates fixed-price and limited fixed-price venues for listings. The `mint_nft` and `mint_nft_to_wallet` functions allow minting new `Demo` NFTs, either depositing them into a listing's inventory or directly transferring them to a specified wallet. The package also includes a `MetadataStore` object, which can store NFT metadata. The `create_metadata_store` function creates this store, and `insert_nft_metadata` adds metadata entries. The `reveal_nft` function updates an existing `Demo` NFT's metadata by retrieving it from the `MetadataStore`, using dynamic fields to track revealed NFTs. The package uses several patterns including royalty enforcement, dynamic fields, and admin capabilities through `MintCap` and `Publisher` objects.
This package manages "Demo" objects, which are NFTs with a name, description, URL, and attributes. The `init` function initializes the collection, sets up display information, defines creators and royalties, and creates various venues (fixed price, limited fixed price) for listing. Public functions allow users to `mint_nft` into a listing's inventory or directly `mint_nft_to_wallet`. An `add_venue` function allows adding new fixed-price venues to an existing listing. The package also includes functionality to create a `MetadataStore` (admin-gated by `Publisher`) and `insert_nft_metadata` into it, which can then be used by `reveal_nft` to update the metadata of a `Demo` object. Notable patterns include admin-gating via `Publisher` for metadata operations, royalty strategies, and the use of dynamic fields to track revealed NFTs.
This Sui package defines a `Test` object, which represents an NFT with a name, description, URL, and attributes. The `init` function initializes the collection, sets up display information, defines creators, and establishes royalty policies (including a royalty strategy based on basis points) and transfer policies. It also creates a listing and an orderbook for the `Test` NFTs. The `mint_nft` entry function allows minting a new `Test` NFT and depositing it into a specified listing's inventory, while `mint_nft_to_wallet` mints an NFT and directly transfers it to a recipient's wallet. The `create_metadata_store` function creates a shared `MetadataStore` object, which acts as a vault to store unrevealed NFT metadata. The `insert_nft_metadata` function adds new metadata (name, description, URL, attributes) to this `MetadataStore`. Finally, the `reveal_nft` function allows updating an existing `Test` NFT's metadata by popping values from the `MetadataStore`, effectively revealing the NFT
This Sui package manages a primary object type called `Test1`, which represents an NFT with fields for `id`, `name`, `description`, `url`, and `attributes`. It also uses `MetadataStore` to manage metadata for these NFTs. The `init` function initializes the collection, sets up display information, defines creators, establishes royalty policies (with a 10% royalty split to a specific address), and creates various policies for transfer, withdrawal, and borrowing of `Test1` NFTs. It also initializes a listing object with a warehouse and a fixed-price venue for SUI, and creates an orderbook. All these capabilities and policies are then shared or transferred to the transaction sender. The `mint_nft` entry function allows minting a new `Test1` NFT with provided name, description, URL, and attributes, and deposits it into a specified listing's inventory. The `mint_nft_to_wallet` entry function similarly mints a `Test1` NFT but directly transfers it to a specified address. Both minting functions emit a
This Sui package manages "Demo" NFTs, which have a name, description, URL, and attributes. The `init` function sets up the collection, creates display information, defines creator addresses, establishes royalty percentages, and initializes various venues for fixed-price and limited fixed-price sales, and an orderbook. Public functions allow for minting new "Demo" NFTs either directly to a wallet or into a listing's inventory. There are also functions to create a `MetadataStore` (a shared object to hold NFT metadata) and to insert metadata into it, and a `reveal_nft` function that updates an existing "Demo" NFT's metadata from the `MetadataStore` using dynamic fields. The package utilizes royalty strategies and transfer policies.
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).
3 self-dealing round-trips excluded from the headline (gross incl. wash: $0).
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
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": "0x0468a7fec4d3ef80a274c66e7f75981cac1423f463fcbe4644f97ad87702ceb5",
"n_tx": 413,
"n_successful_tx": 377,
"n_distinct_epochs": 48,
"n_distinct_sponsors": 0,
"first_seen_cp": 2296651,
"last_seen_cp": 21509320,
"first_seen_ts_ms": 1683871875946,
"last_seen_ts_ms": 1703206378505,
"total_gas_spent_mist": 13611035388,
"n_self_sponsored_tx": 413,
"n_sponsored_tx": 0,
"gas_price_p50": 820,
"gas_price_p95": 830,
"active_hours_top24": [
8,
7,
9,
12,
14,
16,
10,
13,
11,
15,
17,
4,
5,
0,
18,
6,
3,
20
],
"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.
area + brightness = call volume; hover for detail