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 `GithubNFT` objects, which represent NFTs with an ID, name, image URL, creator, and recipient. It also uses a `MintRecord` object, which is a shared object containing a table mapping addresses to `u64` values (likely representing mint counts or NFT IDs). The `init` function initializes a `MintRecord` as a shared object and creates a `Display` object for `GithubNFT`s, transferring both to the transaction sender. The `mint` entry function allows users to mint a `GithubNFT` by paying 10,000,000 SUI to a specific address, provided the recipient address has not previously minted an NFT and the total number of minted NFTs does not exceed 5000. The `burn` entry function allows the owner of a `GithubNFT` to burn it, removing the associated record from the `MintRecord` table.
This package defines a system for managing NFT collections and minting. It primarily manages Minter objects, which represent an NFT collection and its associated minting logic, and Nft objects, which are the individual NFTs. Public/entry functions allow the Minter's owner to add, remove, and update SalePhase objects within a Minter. SalePhase objects define parameters for different minting stages, including price, maximum sales, mints per user, start time, and an optional Merkle root for allowlist gating. The `mint` function allows users to mint NFTs, checking against the current active sale phase, user-specific mint limits, and an optional Merkle proof for allowlist verification. Notable patterns include: - **Admin Gating:** Many functions are restricted to the Minter's owner. - **Time-Gating:** Sale phases are activated based on their `start_time`. - **Allowlist Gating:** Sale phases can optionally include a Merkle root for allowlist verification during minting. - **Dynamic Fields:** The `M
This package manages GithubNFT objects, which represent NFTs with a name, image URL, creator, and recipient. The `init` function creates and shares a `MintRecord` object, which tracks minted NFTs, and a `Display` object for `GithubNFT` metadata, transferring both to the transaction sender. The `mint` entry function allows users to mint a `GithubNFT` for a specified recipient by paying 0.01 SUI, which is transferred to a hardcoded address, and records the mint in the shared `MintRecord` (up to 5000 total NFTs). The `burn` entry function removes a `GithubNFT` from existence and deletes its corresponding entry in the `MintRecord`. The `MintRecord` uses a dynamic field `Table` to store a mapping from recipient addresses to a `u64` (likely the NFT ID).
This package manages `Nft` objects, which represent non-fungible tokens with fields for ID, name, description, media URL, and attributes (a VecMap of strings). The `init` function initializes a `Display` object for `Nft`s, setting up display properties, and creates a `TransferPolicy` for `Nft`s with a kiosk lock rule and a 5% royalty rule, then transfers these objects to the sender and shares the `TransferPolicy`. The `mint_order`, `mint_nft`, and `mint_edition_nft` functions are entry points that delegate to a `launchpad` module to create new `Nft`s, with `mint_edition_nft` also handling kiosk interactions. The `update_nft` function allows a manager to modify the name, description, media URL, and attributes of an existing `Nft` held within a Kiosk. Notably, the package utilizes a `launchpad` module for minting operations, implements royalty and kiosk lock rules via a `TransferPolicy`, and uses dynamic fields for NFT attributes.
This package manages `GithubNFT` objects, which represent NFTs with a name, image URL, creator, and recipient. It also manages a `MintRecord` object, which tracks the number of NFTs minted to each address using a dynamic field `Table<address, u64>`. The `init` function initializes a `MintRecord` and a `Display` object for `GithubNFT`s, sharing both objects publicly. The `mint` entry function allows users to mint a `GithubNFT` by paying 10,000,000 SUI to a hardcoded address, provided the recipient has not already minted an NFT and the total minted NFTs do not exceed 5000. The `burn` entry function allows the recipient of a `GithubNFT` to destroy it, removing their entry from the `MintRecord`.
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": "0x29ae162b4245983529221213663f6157c2fce260333c5312c6d95828ad352499",
"n_tx": 488,
"n_successful_tx": 425,
"n_distinct_epochs": 35,
"n_distinct_sponsors": 0,
"first_seen_cp": 126126960,
"last_seen_cp": 157582293,
"first_seen_ts_ms": 1742809168879,
"last_seen_ts_ms": 1750139984950,
"total_gas_spent_mist": -17487727512,
"n_self_sponsored_tx": 488,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
9,
2,
7,
12,
3,
10,
19,
8,
16,
22,
17,
13,
1,
20,
23,
18,
11,
0,
15,
21,
4,
14,
6,
5
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely E. / SE Asia.
area + brightness = call volume; hover for detail