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 `DEEPClaimNFT` objects, which represent 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 creates and transfers a `Publisher` object, a `Display` object for `DEEPClaimNFT`, and a `ClaimCap` to the transaction sender. The `mint_single` public function allows a `ClaimCap` holder to mint a `DEEPClaimNFT` to a specified address, but only if that address has not already claimed one, and adds the 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 minting to multiple addresses, again preventing duplicate claims. The package employs an allowlist pattern via the `ClaimCap`'s `claimed` field to prevent multiple claims per address.
This package manages two primary objects: `DEEPClaimNFT`, representing an NFT with a name, description, and image URL, and `ClaimCap`, which tracks addresses that have already claimed an NFT. The `init` function creates and transfers a `Publisher` object, a `Display` object for `DEEPClaimNFT`, and a `ClaimCap` to the transaction sender. The `mint_single` public function allows an address to claim a `DEEPClaimNFT` if they haven't already, transferring the NFT to them and updating the `ClaimCap`. 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 one transaction. The package uses a `VecSet` within `ClaimCap` to prevent duplicate claims, acting as an allowlist or signature-gating mechanism based on prior claims.
This package manages two primary objects: `DEEPClaimNFT` (the NFT itself) and `ClaimCap` (a capability object tracking claimed addresses). The `init` function creates and transfers a `Publisher` object, a `Display` object for `DEEPClaimNFT`, and a `ClaimCap` to the transaction sender. The `mint_single` public function allows a `ClaimCap` holder to mint a `DEEPClaimNFT` to a specified address, but only if that address has not already claimed an NFT, and then adds the address to the `ClaimCap`'s `claimed` set. The `mint_batch` entry function iterates through a list of addresses and calls `mint_single` for each, effectively minting NFTs in bulk while respecting the single-claim restriction. The package utilizes a `ClaimCap` to gate the minting process, ensuring each address can only claim one NFT.
This package manages two primary object types: DEEPClaimNFT, which represents an NFT with a name, description, and image URL, and ClaimCap, which tracks addresses that have already claimed an NFT. The `init` function creates a Publisher object, a Display object for DEEPClaimNFTs, and a ClaimCap, transferring all three to the transaction sender. The `mint_single` function allows a user to mint a DEEPClaimNFT if their address is not already in the ClaimCap's `claimed` set, then adds their address to this set and transfers the NFT to them. 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 the DEEPClaimNFT's name, description, image URL, and ID. The ClaimCap acts as an allowlist/signature gating mechanism, preventing duplicate claims.
This package manages two primary object types: DEEPClaimNFT, which represents a non-fungible token, and ClaimCap, which tracks claimed addresses. The `init` function initializes a `ClaimCap` object and transfers it to the sender, along with a `Publisher` and `Display` object. The `mint_single` function allows a `ClaimCap` holder to mint a `DEEPClaimNFT` to a specified address, provided that address has not already claimed an NFT. The `mint_batch` entry function iterates through a list of addresses and calls `mint_single` for each, effectively batch minting NFTs to multiple recipients. This package implements an allowlist-like pattern using the `ClaimCap` to prevent duplicate claims.
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": "0xea7d56603cfb76bed04e1a39380064a7ae93a44cf862e33067078fb3a3240447",
"n_tx": 525,
"n_successful_tx": 525,
"n_distinct_epochs": 1,
"n_distinct_sponsors": 0,
"first_seen_cp": 81259999,
"last_seen_cp": 81271115,
"first_seen_ts_ms": 1731958549031,
"last_seen_ts_ms": 1731961257339,
"total_gas_spent_mist": 174408070500,
"n_self_sponsored_tx": 525,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
19,
20
],
"primary_archetype": "bot",
"labels": [
"bot"
],
"label_confidence": [
0.9942748
],
"bot_score": 0.4,
"bot_signals": [
"timing_automation"
],
"cex_label": null
}Top active hours by UTC.
area + brightness = call volume; hover for detail