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 implements a perpetual futures exchange. It primarily manages `TradeChecks` objects, which define trading parameters for a specific perpetual market, and `Perpetual` objects, representing individual perpetual contracts. Public/entry functions allow for initializing and updating these trading parameters (e.g., `set_min_price`, `set_max_qty_limit`), managing perpetual contracts (listing, delisting, pausing trading), and handling user positions and orders. The package utilizes admin capabilities (`AdminCap`) for privileged operations, emits events for significant state changes, and incorporates extensive error handling for various trading and system constraints, including price and quantity checks, margin requirements, and liquidation conditions.
This Sui package defines a perpetual futures exchange. It primarily manages `TradeChecks` objects, which encapsulate various trading parameters like min/max prices, tick sizes, quantity limits, and market-take bounds. Public/entry functions allow for the initialization of `TradeChecks` and the modification of its individual parameters (e.g., `set_min_price`, `set_max_qty_limit`), emitting corresponding events upon successful updates. The package enforces strict validation rules for all parameter updates and trade operations, including checks for price and quantity ranges, tick/step size adherence, and market-take bounds. Notably, the `error` module provides a comprehensive set of error codes for various validation failures, and the `library` module likely contains common utility functions.
This Sui package defines a perpetual futures exchange. It manages `Perpetual` objects, which represent trading pairs, and `TradeChecks` objects, which store trading rules for each perpetual. Public and entry functions allow for the creation and configuration of perpetuals, including setting price and quantity limits, tick sizes, and market-take bounds. They also enable users to open, close, and modify positions, deposit and withdraw margin, and interact with an order book. The package employs signature gating for order validation, time-gating for order expiration, and admin caps for privileged operations like delisting perpetuals or updating oracle operators. It also uses dynamic fields to store user positions and margin accounts, and implements vault/escrow mechanisms for managing collateral.
This Sui package implements a perpetual futures exchange. It primarily manages `TradeChecks` objects, which define trading parameters for a perpetual market, including min/max prices, tick/step sizes, quantity limits, and market-take bounds. Public and entry functions allow for the initialization of `TradeChecks` and the modification of its various parameters (e.g., `set_min_price`, `set_max_qty_limit`). These functions mutate the `TradeChecks` object and emit corresponding update events. Notable patterns include extensive error handling for parameter validation and the use of events to signal parameter changes.
This Sui package defines a perpetual futures exchange. It primarily manages `TradeChecks` objects, which encapsulate various trading parameters like min/max prices, tick sizes, and quantity limits for different perpetual markets. Public/entry functions allow for the initialization of `TradeChecks` and the modification of its individual parameters (e.g., `set_min_price`, `set_max_qty_limit`), emitting corresponding update events and performing extensive validation checks against predefined error conditions. The package also includes functions to verify trade parameters against these `TradeChecks` before execution. A notable pattern is the use of an `ID` for events, suggesting dynamic fields or a registry for multiple perpetual markets, and the extensive use of error codes for detailed validation failures.
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": "0xfddf022ecb6ec6667131e560ba3c24de3464181792312fcc468521ee0a49c7c5",
"n_tx": 5406,
"n_successful_tx": 5349,
"n_distinct_epochs": 788,
"n_distinct_sponsors": 2,
"first_seen_cp": 10284725,
"last_seen_cp": 282727730,
"first_seen_ts_ms": 1691976482029,
"last_seen_ts_ms": 1780506865200,
"total_gas_spent_mist": 13440900532,
"n_self_sponsored_tx": 5403,
"n_sponsored_tx": 3,
"gas_price_p50": 741.1229,
"gas_price_p95": 759,
"active_hours_top24": [
1,
14,
2,
12,
17,
10,
13,
11,
21,
16,
7,
15,
8,
18,
20,
4,
19,
9,
6,
23,
22,
3,
0,
5
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely W/Central Asia / India.
area + brightness = call volume; hover for detail