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 `Config` and `DomainKiosk` objects. The `Config` object stores global settings like a version, a boolean `allow_mint` flag, and a `ve_sca_amount_threshold`. The `DomainKiosk` object holds an optional `SuinsRegistration` (representing a primary domain), a nested table of `MintRecord`s (mapping addresses to a table of `ID`s to `MintRecord`s), and a `total_minted` counter. Public/entry functions allow an `AdminCap` holder to set the `ve_sca_amount_threshold`, add/take a primary domain, and enable/disable global minting. The `add_to_mint_records` and `remove_from_mint_records` functions (and their batch variants) allow an admin to manage which users are eligible to mint. The `mint_subdomain` function is the core logic, allowing users to mint a `SubDomainRegistration` if global minting is allowed, they are in the mint records, and
This package manages two primary object types: a globally shared Config object and an AdminCap object. The Config object stores a single u64 value representing a threshold. The AdminCap object is a capability object used for administrative control. The init function creates and shares a Config object with an initial threshold of 0, and creates an AdminCap object which is then transferred to the transaction sender. The set_threshold function updates the threshold field of a mutable Config object. The check_if_profit function takes a shared Config object and a Coin object, and aborts if the Coin's value is less than the Config's threshold. The package uses an admin capability pattern for initial setup and a shared object pattern for the Config.
This package defines a `TradeInfoHotPotato` object, which stores a `threshold_in_usd` and `profit_in_usd`. The `start_evaluation` entry function creates a `TradeInfoHotPotato` object with an initial `threshold_in_usd` and `profit_in_usd` set to zero, requiring the initial threshold to be greater than zero. The `is_trade_profitable` entry function calculates the USD value of a given coin using Pyth price feeds and adds it to the `profit_in_usd` field of a mutable `TradeInfoHotPotato` object. The `end_evaluation` entry function checks if the `profit_in_usd` in a `TradeInfoHotPotato` object is greater than or equal to its `threshold_in_usd`, aborting if not. The package uses Pyth price feeds to convert token values to USD.
This package manages a name service for "Obligation" objects, allowing them to be associated with human-readable names. The primary object types are `ObligationNameService` (a singleton object holding the registry) and `Registry` (which stores the name-to-ID mappings). Public/entry functions allow for registering, updating, and removing names for `Obligation` objects, and resolving names to IDs or IDs to names. The `init` function creates an `ObligationNameService` and an `AdminCap`, sharing the former and transferring the latter to the deployer. The `new_registry` and `destroy_registry` functions are gated by the `AdminCap`, enabling administrative control over the `Registry` object within the `ObligationNameService`. The `Registry` uses two dynamic tables for bidirectional lookups between names (String) and `Obligation` IDs.
This package, arbitrage_check, manages a single primary object type: TradeInfoHotPotato. This object stores two u64 values: threshold_in_usd and profit_in_usd. The public/entry functions are start_evaluation, end_evaluation, and is_trade_profitable. start_evaluation creates a TradeInfoHotPotato object, initializing profit_in_usd to 0 and threshold_in_usd with a provided value (which must be greater than 0). end_evaluation takes a TradeInfoHotPotato and asserts that profit_in_usd is greater than or equal to threshold_in_usd, aborting otherwise. is_trade_profitable calculates the USD value of a given Coin using Pyth price feeds, adds this value to the profit_in_usd field of a mutable TradeInfoHotPotato, and then either destroys the coin if its value is zero or transfers it to the transaction sender. A notable pattern is the use of Pyth price feeds for real-time price data and the "Hot Potato" pattern where the TradeInfoHotPotato
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": "0x61819c99588108d9f7710047e6ad8f2da598de8e98a26ea62bd7ad9847f5329c",
"n_tx": 28278,
"n_successful_tx": 27734,
"n_distinct_epochs": 934,
"n_distinct_sponsors": 4,
"first_seen_cp": 8270499,
"last_seen_cp": 283170982,
"first_seen_ts_ms": 1689962510286,
"last_seen_ts_ms": 1780605173460,
"total_gas_spent_mist": 161111517446,
"n_self_sponsored_tx": 28207,
"n_sponsored_tx": 71,
"gas_price_p50": 750,
"gas_price_p95": 755,
"active_hours_top24": [
5,
18,
17,
6,
8,
16,
7,
4,
11,
9,
19,
20,
21,
15,
10,
12,
3,
13,
22,
14,
2,
1,
23,
0
],
"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).
area + brightness = call volume; hover for detail