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 `NSClaimNFT` objects, which are non-fungible tokens with a name, description, and image URL. It also uses a `ClaimCap` object to track which addresses have already claimed an NFT. The `init` function creates a `Publisher` object, a `Display` object for `NSClaimNFT`, and a `ClaimCap` object, transferring all three to the transaction sender. The `mint_single` function allows a user to claim a single `NSClaimNFT` if they haven't already, adding their address to the `claimed` set within the `ClaimCap`. The `mint_batch` entry function iterates through a list of addresses and calls `mint_single` for each, effectively allowing batch claiming. The package includes getter functions for the `NSClaimNFT`'s name, description, image URL, and ID.
This package manages two primary object types: `NSClaimNFT`, which represents a non-fungible token with a name, description, and image URL, and `ClaimCap`, which tracks which addresses have already claimed an NFT. The `init` function initializes the module, creating a `Publisher` object, a `Display` object for `NSClaimNFT`, and a `ClaimCap` object, all transferred to the transaction sender. The `mint_single` public function allows an address to claim a single `NSClaimNFT` if they haven't already, updating the `ClaimCap` and transferring the new NFT to the claimant. The `mint_batch` entry function iterates through a list of addresses and calls `mint_single` for each, effectively allowing multiple NFTs to be claimed in a single transaction. A notable pattern is the use of a `ClaimCap` with a `VecSet<address>` to prevent duplicate claims, acting as an allowlist or signature gating mechanism.
This package manages `NSClaimNFT` objects, which are non-fungible tokens with a name, description, and image URL. It also uses a `ClaimCap` object to track which addresses have already claimed an NFT. The `init` function initializes the package, creating a `Publisher` object, a `Display` object for `NSClaimNFT`, and a `ClaimCap` object, transferring them to the sender. The `mint_single` public function allows a user to mint a single `NSClaimNFT` if they haven't claimed one before, transferring it to a specified address and updating the `ClaimCap`. The `mint_batch` entry function iterates through a list of addresses and calls `mint_single` for each, effectively allowing batch minting. The package employs an allowlist-like pattern using the `ClaimCap` to prevent multiple claims per address.
This package manages two primary object types: `NSClaimNFT` (the actual NFT) and `ClaimCap` (a capability object that tracks claimed addresses). The `init` function creates a `Publisher` object, a `Display` object for `NSClaimNFT` metadata, and a `ClaimCap` object, transferring all three to the transaction sender. The `mint_single` public function allows the holder of a `ClaimCap` to mint a single `NSClaimNFT` to a specified address, but only if that address has not already claimed an NFT (checked via a `VecSet<address>` within `ClaimCap`). The `mint_batch` entry function iterates through a list of addresses and calls `mint_single` for each, effectively allowing batch minting. The package includes getter functions for `NSClaimNFT`'s name, description, image URL, and ID. A notable pattern is the use of a `ClaimCap` to gate minting and a `VecSet` within `ClaimCap` to prevent duplicate claims per address.
This package manages `NSClaimNFT` objects, which are simple NFTs with a name, description, and image URL. It also uses a `ClaimCap` object to track which addresses have already claimed an NFT. The `init` function initializes the package, creates a `Publisher` object and a `Display` object for `NSClaimNFT`, and transfers them to the sender. It also creates and transfers a `ClaimCap` object to the sender. The `mint_single` and `mint_batch` functions allow a user to mint `NSClaimNFT`s, but only if the recipient address has not already claimed one, as tracked by the `ClaimCap`'s `claimed` VecSet. The `mint_batch` function iterates through a list of addresses and calls `mint_single` for each. There are also public getter functions for the `NSClaimNFT` fields. This package implements an allowlist/one-time claim pattern using the `ClaimCap` object.
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.
botRule-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": "0xdd8d4022617f5f3d8b677821f3b0bd2d7ae0ad575896d62a568e9833d3a46ab5",
"n_tx": 3843,
"n_successful_tx": 3843,
"n_distinct_epochs": 3,
"n_distinct_sponsors": 0,
"first_seen_cp": 80286420,
"last_seen_cp": 81258430,
"first_seen_ts_ms": 1731722082220,
"last_seen_ts_ms": 1731958166560,
"total_gas_spent_mist": 1194419865964,
"n_self_sponsored_tx": 3843,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
3,
4,
5,
10,
9,
19,
8,
11,
2,
1
],
"primary_archetype": "bot",
"labels": [
"bot"
],
"label_confidence": [
0.9406559
],
"bot_score": 0.4,
"bot_signals": [
"timing_automation"
],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely E. / SE Asia.
area + brightness = call volume; hover for detail