0x07f8993e716f6d64d2fb12ae46b2e45682f495e614aa192bd3a0d3a88694dff3
published packages · 5 of 6
Move packages this wallet published on-chain — what it shipped, not what it used.
- 0x03eaab99…600b8c26
This Sui package, ScallopGift, primarily manages a non-fungible token (NFT) called SCALLOPGIFT_TICKET. The `init` function initializes the package by creating a Publisher object and a Display object for the SCALLOPGIFT_TICKET, transferring both to the transaction sender. The `GiftFromScallop` entry function allows for the minting of new SCALLOPGIFT_TICKET NFTs, distributing them to a list of provided addresses, and emits a `MintEvent` for each. The `burn_nft` entry function enables users to destroy their SCALLOPGIFT_TICKET NFTs, emitting a `BurnEvent` upon successful burning. The package utilizes standard object and event mechanisms, and the `init` function sets up display metadata for the NFT.
- 0x12fe596b…c8726c09
This Sui package, ScallopGift, primarily manages SCALLOPGIFT_TICKET objects, which are NFTs representing vouchers with a name, image URL, description, and a reward string. The `init` function is called once upon package deployment to create and transfer a `Publisher` object and a `Display` object for `SCALLOPGIFT_TICKET` to the deployer. The `MintNFT` entry function allows for the creation of new `SCALLOPGIFT_TICKET` NFTs and transfers them to specified recipient addresses, emitting a `MintEvent`. The `burn_nft` entry function allows an owner to burn a `SCALLOPGIFT_TICKET` NFT, emitting a `BurnEvent` with the NFT's details. A notable pattern is the use of a loop in `MintNFT` to mint multiple NFTs to different addresses provided in a vector, and the hardcoded metadata for the NFTs.
- 0x2c1779e7…4b1f8355
This package manages SCALLOPGIFT_TICKET objects, which are NFTs representing vouchers for 10,000 SCA. The `init` function initializes the package by creating a Publisher object and a Display object for SCALLOPGIFT_TICKET, then transfers them to the transaction sender. The `GiftFromScallop` entry function mints SCALLOPGIFT_TICKET NFTs and transfers them to a list of specified addresses, emitting a MintEvent for each. The `burn_nft` entry function allows users to burn their SCALLOPGIFT_TICKET NFTs, emitting a BurnEvent. The package utilizes the `display` module to set up metadata for the NFT and emits events for minting and burning.
- 0x8aceb4ae…91fa4361
This package manages a primary object type called SCALLOPGIFT_TICKET, which represents a gift voucher with an ID, name, image, description, and reward. The `init` function initializes the package by claiming a `Publisher` object and creating a `Display` object for `SCALLOPGIFT_TICKET`s, then transfers both to the transaction sender. The `GiftFromScallop` entry function mints new `SCALLOPGIFT_TICKET`s, each containing a 10,000 SCA voucher, and transfers them to a list of specified recipient addresses, emitting a `MintEvent` for each. The `burn_nft` entry function allows users to burn their `SCALLOPGIFT_TICKET`s, emitting a `BurnEvent` upon successful burning. The package utilizes dynamic fields implicitly through the `Display` object and emits events for both minting and burning of tickets.
- 0xb8fc4524…ff83699d
This package manages a primary object type called SCALLOPGIFT_TICKET, which represents a gift voucher. The init function initializes the package by creating a Publisher object and a Display object for SCALLOPGIFT_TICKET, then transfers them to the transaction sender. The public entry function GiftFromScallop mints new SCALLOPGIFT_TICKET objects and transfers them to a list of specified addresses, emitting a MintEvent for each. The public entry function burn_nft allows a user to burn their SCALLOPGIFT_TICKET, emitting a BurnEvent. Notably, the GiftFromScallop function uses a loop to mint multiple tickets and transfers them one by one, and both minting and burning actions emit events.
related wallets · likely same operator
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.
- 0x0137d102…4c6ae16acofunded
- 0x0a8c39cb…effa547afunder
- 0x0ee36e9a…c893a699cofunded
- 0x232872a1…0d0c1e4fcofunded
- 0x30f2e0ae…b2d86eb0cofunded
- 0x61eb2e1b…db05a760cofunded
- 0x72246cff…94bea80fcofunded
- 0xab04c8a9…68f05f0acofunded
- 0xb509db3d…647d1a34cofunded
- 0xe10fa1b5…a24f90d0cofunded
Tinted amber on the bubble map when they appear in the expanded graph.
relationship bubble map
behavioral classification
casual70%
Rule-based labels, conservative precision.
activity window
- first seen
- cp 39,315,940 · 2024-07-14 14:50:06 UTC
- last seen
- cp 39,359,394 · 2024-07-15 02:50:33 UTC
- distinct epochs
- 2
- distinct sponsors
- 0
- gas price p50 / p95
- 759 / 759 mist
active hours (UTC) — circadian rhythm
Top active hours by UTC.
transaction timing
packages interacted with(5 distinct)
area + brightness = call volume; hover for detail
- ScallopGift9 calls1 fns
- ScallopGift8 calls1 fns
- ScallopGift8 calls1 fns
- ScallopGift8 calls1 fns
- ScallopGift1 calls1 fns
top counterparties
funding lineage
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.
gas sponsor lineage
raw profile JSON
{
"wallet": "0x07f8993e716f6d64d2fb12ae46b2e45682f495e614aa192bd3a0d3a88694dff3",
"n_tx": 41,
"n_successful_tx": 41,
"n_distinct_epochs": 2,
"n_distinct_sponsors": 0,
"first_seen_cp": 39315940,
"last_seen_cp": 39359394,
"first_seen_ts_ms": 1720968606791,
"last_seen_ts_ms": 1721011833200,
"total_gas_spent_mist": 28051488680,
"n_self_sponsored_tx": 41,
"n_sponsored_tx": 0,
"gas_price_p50": 759,
"gas_price_p95": 759,
"active_hours_top24": [
15,
14,
2
],
"primary_archetype": "casual",
"labels": [
"casual"
],
"label_confidence": [
0.7
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}