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 Sui package defines a fungible token called XOADIDAS and manages a `Store` object. The `init` function creates the XOADIDAS currency with a fixed supply and stores its `TreasuryCap` in the `Store` object using a dynamic object field. The `Store` object, which holds an admin address and a version, is then shared. Public/entry functions allow an authorized admin to register bridges with the `tradeport_bridge` module, either directly or with a signature, by minting XOADIDAS tokens from the `TreasuryCap` and passing them to the bridge. The admin can also update the `Store`'s version and change the admin address. All administrative actions are gated by `verify_version` and `verify_admin` checks, ensuring only the current admin can perform these operations.
This Sui package defines an ASTRO token and a Store object. The Store object holds the package's version, an admin address, and dynamically stores the ASTRO token's TreasuryCap and DenyCapV2. Public functions allow the admin to register a bridge (minting ASTRO tokens in the process), set the package version, and change the admin address. All administrative functions are gated by checking the Store's version and verifying the transaction sender against the stored admin address.
This package defines a `BOBA` coin and a `Store` object to manage its properties. The `init` function creates the `BOBA` coin's `TreasuryCap`, `DenyCapV2`, and `CoinMetadata`, storing the caps as dynamic object fields within a shared `Store` object. Public functions `register_bridge` and `register_bridge_with_signature` mint `BOBA` coins and then call functions on a `tradeport_bridge::Manager` object, likely for cross-chain bridging. These functions are gated by `verify_version` and `verify_admin` checks, ensuring only the designated admin can perform these actions and that the `Store` object is at version 1. The `set_version` and `set_admin` entry functions allow the current admin to update the `Store`'s version and the admin address, respectively, also protected by the `verify_version` and `verify_admin` checks. The package utilizes dynamic object fields to store the `TreasuryCap` and `Den
This Sui package, `commission`, primarily manages a `Manager` object, which acts as an administrative hub. The `Manager` object stores a version number and an admin address, and uses dynamic fields to manage various `Balance` objects (for different coin types) and `RewardManager` objects. Public/entry functions allow the admin to set the manager's version and admin address. Users can `verify_swap` and `verify_slippage` for token exchanges, which potentially collects a commission into the manager's balance if certain conditions are met. The admin can add or update `RewardManager` objects, which define reward rates and manage NFT registries for rewards. Users can `pay` into the commission system, with a portion potentially allocated to a specific reward manager, and `pay_reward` or `withdraw_reward` for NFTs registered in a reward manager. The admin can also `withdraw` funds from the manager's collected balances. Notable patterns include: - Admin gating: `set_version`, `set_admin`, `add_reward_manager
This package defines a `PAPER` coin and a `Store` object to manage its associated capabilities. The `init` function creates the `PAPER` coin, its `TreasuryCap`, `DenyCapV2`, and `CoinMetadata`, then shares a `Store` object that holds these capabilities as dynamic object fields. Public/entry functions `register_bridge` and `register_bridge_with_signature` mint `PAPER` coins and register them with a `tradeport_bridge` module, with the latter allowing for an additional signature. The `set_version` and `set_admin` entry functions allow the current admin to update the `Store`'s version or transfer admin privileges. All public/entry functions are gated by an admin check and a version check on the `Store` object.
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": "0x356a4c521daab807958cdf04355c571af0c1a1f8b3cf83b694edb4c7124affe0",
"n_tx": 157,
"n_successful_tx": 154,
"n_distinct_epochs": 20,
"n_distinct_sponsors": 0,
"first_seen_cp": 114647137,
"last_seen_cp": 256020094,
"first_seen_ts_ms": 1740048230514,
"last_seen_ts_ms": 1773928252647,
"total_gas_spent_mist": 117430219968,
"n_self_sponsored_tx": 157,
"n_sponsored_tx": 0,
"gas_price_p50": 500,
"gas_price_p95": 553,
"active_hours_top24": [
13,
18,
16,
17,
10,
15,
11,
12,
7,
9,
20,
8,
19
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely C. Europe / Africa / Middle East.