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, cetus_integration, primarily manages AutoRebalanceStrategy<Position> objects. The public function new_strategy creates a new AutoRebalanceStrategy object, initialized with a byte vector, a Position object, an I32 value, and a Clock object, then shares this new strategy object publicly. The get_new_tick_range function takes a mutable AutoRebalanceStrategy, a Pool, and a Clock, and calculates new tick ranges (I32 * I32) along with a Position and an AutoRebalanceReceipt, based on the current pool state and the strategy's parameters. This function involves complex calculations using square root prices and tick math, and includes checks that can abort execution if certain conditions related to tick ranges or price boundaries are not met. There are no explicit signature/allowlist gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties patterns visible in the provided IR.
This package, `cetus_integration`, primarily manages `AutoRebalanceStrategy<Position>` objects. The `new_strategy` public function creates a new `AutoRebalanceStrategy` object, initialized with a name, a `Position` object, an `I32` value, and the current `Clock` and `TxContext`, then shares this new strategy object publicly. The `get_new_tick_range` public function calculates new tick ranges for a given `AutoRebalanceStrategy` and `Pool` based on the current tick and sqrt price, returning two `I32` values representing the new tick range, the updated `Position` object, and an `AutoRebalanceReceipt`. This function involves several calculations and assertions related to tick values and sqrt prices, and it mutates the `AutoRebalanceStrategy` object by calling `auto_rebalance::prepare_rebalance`. The package uses the `auto_rebalance` module to manage rebalancing strategies and the `pool` and `position` modules for liquidity pool and position data.
This Sui package defines an "enclave" module for managing trusted execution environments and a "test_cetus" module for testing. The primary object types in "enclave" are EnclaveConfig (shared configuration for enclaves) and Enclave (a registered enclave instance). Public functions allow creating and sharing EnclaveConfig, registering Enclaves by verifying NitroAttestationDocuments, and verifying signatures against an Enclave's public key. Updates to EnclaveConfig (PCRs, name) are gated by a Cap object, which acts as an admin capability. The "test_cetus" module manages a shared Counter object, which uses a dynamic field Bag to store arbitrary key-value pairs.
This package manages `EnclaveConfig` and `Enclave` objects, which represent configurations and registered enclaves, respectively. Public functions allow users to create an `EnclaveConfig` (which is then shared), register an `Enclave` based on an `EnclaveConfig` and a NitroAttestationDocument (also shared), and verify signatures against an `Enclave`'s public key. An `EnclaveConfig` can be updated by its creator (identified by a `Cap` object) to modify PCRs or the name, which increments its version. Old `Enclave` objects can be destroyed if their `config_version` is outdated or by their owner. A notable pattern is the use of a `Cap` object for authorization to modify `EnclaveConfig` fields, and the `Enclave` object itself stores the public key and the owner's address.
This Sui package manages automated strategies for interacting with financial positions, primarily through `AutoCompoundStrategy` and `AutoExitStrategy` objects. Public functions allow users to create new strategies, which are owned by the creator and linked to a `PositionRegistry` ID. These strategies define conditions for auto-compounding rewards or auto-exiting positions based on specified intervals, thresholds, or values. The `prepare_compound_bot` and `prepare_exit_bot` functions enable external bots to trigger these strategies, requiring a valid signature from an `Enclave` object, while `prepare_compound_owner` and `prepare_exit_owner` allow the strategy owner to trigger them directly. The package utilizes dynamic fields implicitly through `UID`s for object identification and employs signature-based gating for bot interactions.
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.
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": "0x1f763ff6cd47aa848142373c2595102e73da7d53d175a478ed0c57a5ab0d887f",
"n_tx": 223,
"n_successful_tx": 128,
"n_distinct_epochs": 15,
"n_distinct_sponsors": 0,
"first_seen_cp": 176199332,
"last_seen_cp": 182648734,
"first_seen_ts_ms": 1754553341233,
"last_seen_ts_ms": 1756110346638,
"total_gas_spent_mist": 2431446832,
"n_self_sponsored_tx": 223,
"n_sponsored_tx": 0,
"gas_price_p50": 500,
"gas_price_p95": 503,
"active_hours_top24": [
4,
9,
8,
2,
3,
5,
13,
12,
14,
10,
15,
6,
7,
11,
1,
0,
16,
17,
18,
19
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Tinted amber on the bubble map when they appear in the expanded graph.
Top active hours by UTC. Circadian peak → likely E. / SE Asia.
area + brightness = call volume; hover for detail