all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
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 an XSWAP cross-chain bridge. The primary object is the XSwap shared object, which stores configuration like paused status, supported wallet keys and chains, minimum confirmations, solvers, managers, and collected fees. The package also manages Request objects, representing individual cross-chain transfer requests. Public/entry functions allow for initializing the XSwap object, minting presignatures (likely for off-chain processing), creating new cross-chain requests, settling requests, and withdrawing funds from requests. These functions mutate the XSwap object (e.g., updating collected fees, pausing/unpausing) and create/update Request objects. Notable patterns include an AdminCap for administrative control, dynamic fields (tables) for managing various configurations (chains, solvers, managers, digests, min_confirmations), and the use of an EnclaveCap, suggesting interaction with a trusted execution environment. The package also emits numerous events to log state changes.
This package manages cross-chain address linkages, primarily for Solana and EVM addresses to Sui addresses, and also supports alias addresses within Sui. The primary object is `StateV1`, which stores mappings between Solana/EVM addresses and Sui addresses, and manages a user's linked external addresses and Sui aliases. Public functions allow users to link and unlink Solana, EVM, and Sui alias addresses to their primary Sui address, requiring cryptographic signatures for external chain linkages. The package uses `Table` and `VecSet` dynamic fields to store these mappings and enforce limits on the number of linked addresses. Events are emitted for all linking and unlinking operations.
This package defines an `Enclave` object, which stores PCRs (Platform Configuration Registers) and a public key from a NitroAttestationDocument. The `new_cap` function creates an `EnclaveCap` object, which acts as an administrative capability for a specific type. The `register` function creates and shares a new `Enclave` object, using the `EnclaveCap` for authorization and extracting PCRs and a public key from a provided `NitroAttestationDocument`. The `update` function allows modification of an existing `Enclave`'s PCRs and public key, but only if the provided `EnclaveCap` matches the `cap_id` stored within the `Enclave` object. The `verify_signature` function checks an Ed25519 signature against a public key stored in an `Enclave` object, using a serialized `IntentMessage` as the signed data.
This package defines an XBridgeConfig object that manages cross-chain bridge operations, including fees, validators, and watchtowers. It allows administrators (holding an AdminCap) to configure bridge parameters like fees (mint, burn, lock, unlock, presign), add/remove validators and watchtowers, and pause/unpause the bridge. The package also handles minting presignatures for cross-chain transactions, collecting fees, and managing wallet keys. Notably, it uses an AdminCap for administrative gating, dynamic fields (VecMap, VecSet, Table) for storing configuration data, and collects fees into a SUI balance.
This Sui package defines an Interest Stable Swap protocol, primarily managing `InterestStableSwapACL` (Access Control List), `InterestStableSwapSuperAdmin`, and `InterestStableSwapAdmin` objects for administrative control, and `InterestStableSwapAV` for managing allowed protocol versions. Public functions allow for adding/removing administrators, transferring super admin roles with a time-gated deadline, and signing in as an admin to obtain an `AuthWitness` for gated functions. The package also includes modules for calculating curve invariants, handling coin decimals, and emitting events, suggesting a stable swap AMM with administrative control and versioning.
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": "0xbbf31f4075625942aa967daebcafe0b1c90e6fa9305c9064983b5052ec442ef7",
"n_tx": 27381,
"n_successful_tx": 27201,
"n_distinct_epochs": 220,
"n_distinct_sponsors": 0,
"first_seen_cp": 46645071,
"last_seen_cp": 283114955,
"first_seen_ts_ms": 1723504616351,
"last_seen_ts_ms": 1780592726020,
"total_gas_spent_mist": 200056348970,
"n_self_sponsored_tx": 27381,
"n_sponsored_tx": 0,
"gas_price_p50": 711,
"gas_price_p95": 757,
"active_hours_top24": [
1,
0,
23,
2,
14,
13,
15,
16,
9,
21,
22,
18,
17,
19,
20,
3,
11,
8,
12,
6,
4,
10,
5,
7
],
"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