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 primarily manages an Nft object type, which includes fields for ID, name, description, media_url, and attributes (a VecMap of strings). The init, mint_order, mint_nft, mint_edition_nft, and update_nft functions all immediately abort, indicating they are either placeholders or intentionally disabled. The create_nft_with_verification function creates a new Nft object, populating its fields from the arguments, and then associates its ID with a Verification object from the launchpad module. The update_nft_with_verification function allows modification of an Nft's name, description, media_url, and attributes, but only if the provided Nft ID matches the one stored in the Verification object, and it requires a Kiosk and KioskOwnerCap to borrow the Nft. This package uses dynamic fields for Nft attributes and relies on an external launchpad module for verification.
This package manages an `Nft` object, which represents a Seal Adventure NFT with fields for ID, name, description, media URL, and attributes (a `VecMap` of strings). The `init` function initializes a `Display` object for `Nft`, sets up a `TransferPolicy` with a kiosk lock rule and a 2% royalty, and transfers these capabilities to the transaction sender. Public entry functions `mint_order`, `mint_nft`, and `mint_edition_nft` delegate to a `launchpad` module to handle various NFT minting scenarios, including creating new `Nft` objects. The `update_nft` function allows an authorized `Manager` to modify the name, description, media URL, and attributes of an `Nft` stored within a Kiosk. The package utilizes `transfer_policy` for managing NFT transfers, including royalty and kiosk lock rules, and integrates with a `launchpad` module for minting operations.
This package primarily manages `Nft` objects, which are non-fungible tokens with fields for `id`, `name`, `description`, `media_url`, and `attributes` (a `VecMap` of strings to strings). The `init` function and most public/entry functions (`mint_order`, `mint_nft`, `mint_edition_nft`, `update_nft`) immediately abort, indicating they are either placeholders or their implementations were removed. The `create_nft_with_verification` function creates a new `Nft` object, populating its fields from the arguments, and then associates its ID with a `Verification` object from the `launchpad` module. The `update_nft_with_verification` function modifies an existing `Nft`'s `name`, `description`, `media_url`, and `attributes` within a `Kiosk`, but only if the provided `Nft`'s ID matches the one stored in the `Verification` object. This suggests a pattern of using an external `Verification` object for gating updates to specific
This package defines an Nft object type with fields for ID, name, description, media URL, and attributes (a VecMap of strings). The init, mint_order, mint_nft, mint_edition_nft, and update_nft functions are all stubbed out, immediately aborting. The create_nft_with_verification function creates a new Nft object, sets its ID in a Verification object, and returns the Nft. The update_nft_with_verification function allows modification of an Nft's name, description, media URL, and attributes, but only if the provided Nft ID matches the one stored in the Verification object, and it requires a Kiosk and KioskOwnerCap to borrow the Nft mutably. This indicates a pattern of gating NFT creation and updates through a separate Verification object, likely for some form of pre-approval or controlled minting process.
This package defines an `Nft` object type, which includes fields for `id`, `name`, `description`, `media_url`, and `attributes` (a `VecMap` of strings). The `init` function and several public functions (`mint_order`, `mint_nft`, `mint_edition_nft`, `update_nft`) are stubbed out and immediately abort, indicating they are either not yet implemented or are placeholders. The `create_nft_with_verification` entry function creates a new `Nft` object, populates its fields, and then calls an external `launchpad::set_verification_nft_id` function, associating the newly created NFT's ID with a `Verification` object. The `update_nft_with_verification` entry function allows modification of an existing `Nft`'s `name`, `description`, `media_url`, and `attributes` if the provided `ID` matches the one stored in the `Verification` object, and the NFT is held within a `Kiosk`. This package utilizes dynamic fields
area + brightness = call volume; hover for detail
{
"wallet": "0xf34842ea7a553823607dbc43ecc8900af8891949938b3a8cb7941bc3cb2c3942",
"n_tx": 56,
"n_successful_tx": 51,
"n_distinct_epochs": 9,
"n_distinct_sponsors": 0,
"first_seen_cp": 140570123,
"last_seen_cp": 182334054,
"first_seen_ts_ms": 1746206859716,
"last_seen_ts_ms": 1756033414941,
"total_gas_spent_mist": 449352488,
"n_self_sponsored_tx": 56,
"n_sponsored_tx": 0,
"gas_price_p50": 740,
"gas_price_p95": 741,
"active_hours_top24": [
17,
11,
20,
5,
9,
10,
18,
1,
0,
13
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).