all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
counterparties · funders · clusters
The 0xda89…c39e wallet is a prolific developer, having published 50 packages on Sui. This project wallet appears to be managing and updating various vault contracts across multiple lending protocols like Navi, Suilend, and Scallop, likely for administrative tasks such as enabling/disabling deposits or withdrawing SUI. With a bot score of 0.00 and no suspicious activity signals, this looks like a legitimate project maintaining its infrastructure.
Move packages this wallet published on-chain — what it shipped, not what it used.
This Sui package defines a system for managing financial vaults and their associated configurations and permissions. The primary object types are `Config`, which stores global parameters like fees and whitelisted extensions, and `Vault<Ty0>`, a generic vault that holds assets of type `Ty0`. Public/entry functions allow for the creation of `Config` objects, management of whitelisted extensions, and updating of various fee parameters. The package heavily utilizes admin caps (`AuthorityCap`) for access control, requiring specific roles (ADMIN, ASSISTANT, PAUSE_GUARDIAN) to perform sensitive operations. It also features a liquidity cache update mechanism (`UpdateLiquidityCacheCap`) to track and manage liquidity across different extensions and coin types within a vault, ensuring all necessary data is queried before an update is finalized.
This Sui package defines a system for managing and executing orders, likely for token swaps or similar transactions. The primary object types are `AdminCap` for administrative control, `Config` for global settings, and `Order<InputCoinType, OutputCoinType>` representing individual orders. Public and entry functions allow for creating a global `Config` object (once per package deployment) and an `AdminCap` (transferred to the deployer). Users can `create_order` by providing input coins, a recipient address, and encrypted fields, which creates an `Order` object and transfers it to a derived multisig address. Orders can be `close_order` to refund the input and gas coins to the original user, or `begin_tx` and `finish_tx` to execute a trade. `begin_tx` extracts the input and gas coins from the `Order` and returns an `OrderCap` containing the original input and gas amounts. `finish_tx` takes the `OrderCap` and the output coin, verifies the trade parameters against the encrypted fields,
This Sui package, `ifixed`, does not manage any primary object types. Instead, it provides a library for fixed-point arithmetic using `u256` integers, representing numbers with a fixed decimal precision. The public and entry functions primarily perform arithmetic operations (addition, subtraction, multiplication, division, negation, absolute value, min, max) and conversions between different integer types (`u64`, `u128`, `u256`) and the fixed-point `u256` representation. These functions do not mutate any on-chain objects; they are pure computations. Notable patterns include extensive use of bitwise XOR operations with a constant `5789...` (likely representing a sign bit or a scaling factor for fixed-point representation) and frequent checks against this constant to handle potential overflows or underflows, aborting execution if conditions are not met. There are no indications of signature/allowlist gating, time-gating, dynamic fields, admin caps, vault/escrow mechanisms, or royalties.
This package defines a new fungible token called LP_COIN. The `init` function is the only public/entry function and it creates the LP_COIN currency, minting a `TreasuryCap<LP_COIN>` and `CoinMetadata<LP_COIN>` object. These objects are then transferred to the sender of the transaction. The `TreasuryCap` allows for future minting and burning of LP_COIN, while the `CoinMetadata` contains information like the coin's name, symbol, and description. There are no notable patterns like dynamic fields, admin caps, or time-gating.
This package defines a `FAKE_COIN` type, which is a dummy struct. The `init` function creates a new `FAKE_COIN` currency, minting a `TreasuryCap<FAKE_COIN>` and `CoinMetadata<FAKE_COIN>` object. It sets the coin's name, symbol, description, and icon URL. Both the `TreasuryCap` and `CoinMetadata` objects are then transferred to the sender of the transaction. This package essentially sets up a new fungible token with basic metadata.
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": "0xda89fdc9957a40614bdcbb0d689022f370b1704e56ee7f338a4841dceaccc39e",
"n_tx": 1032,
"n_successful_tx": 679,
"n_distinct_epochs": 106,
"n_distinct_sponsors": 1,
"first_seen_cp": 12340251,
"last_seen_cp": 267947800,
"first_seen_ts_ms": 1694073431719,
"last_seen_ts_ms": 1776883225440,
"total_gas_spent_mist": 13612309989,
"n_self_sponsored_tx": 1020,
"n_sponsored_tx": 12,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
17,
16,
15,
11,
8,
13,
12,
14,
7,
6,
18,
9,
4,
10,
20,
3,
2,
22,
19,
5,
21,
23
],
"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 C. Europe / Africa / Middle East.
area + brightness = call volume; hover for detail