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 a decentralized finance (DeFi) protocol for managing liquidity pools and distributing rewards. It primarily manages an Allocator object, which tracks various liquidity pools, their weights, and accumulated rewards for different token types. Public/entry functions allow for creating an Allocator, adding new liquidity pools, setting weights for specific token types within a pool, and claiming rewards. Notable patterns include the use of dynamic fields (Bag and VecMap) within the Allocator and Pool_info objects to handle different token types and pool data, and an Admin_cap for administrative actions like adding new administrators. The system also incorporates time-gating for reward distribution based on a last_update_time field.
This Sui package defines a reward allocation system for various pools. It manages an `Allocator` object, which stores information about different pools, their weights for various reward types, and accumulated rewards. Public functions allow creating an `Allocator`, adding new pools, setting the weight of a pool for a specific reward type, depositing rewards into the allocator (from a distributor), and claiming rewards for a given pool. The `alpha` module defines the `ALPHA` coin, its `TreasuryCap`, and `Admin_cap` for managing the system, along with a `Burn_start_cap` which is immediately destroyed. The system uses `VecMap` for dynamic storage of pool information and reward weights, and `Bag` for managing various reward balances.
This package manages Pool objects, which are liquidity pools for a specific token type (Ty0). Users can create new Pools and receive an AdminCap for that pool. The `user_deposit` function allows users to deposit coins into a Pool, receiving a Receipt object representing their share (xTokenBalance). The `user_withdraw` function enables users to withdraw coins from a Pool by burning their Receipt. The `take_all` function allows the AdminCap holder to withdraw all funds from a Pool. The package utilizes dynamic fields for rewards and calculates an exchange rate between the deposited token and the xToken.
This package defines a system for managing investor positions across two lending protocols, Navi and Scallop, and a custom staking pool. The primary object type is `Investor<Ty0>`, which holds `AccountCap`s for Navi and Scallop, and tracks the investor's total invested amount. Public entry functions allow investors to create their `Investor` object, deposit and withdraw funds to/from Scallop, and manage their positions in Navi. A notable pattern is the `collect_all_rewards_and_reinvest` function, which claims rewards from both protocols, reinvests Navi rewards into Navi, and then uses a portion of the Navi rewards to borrow more from Navi, which is then deposited into Scallop. The `pool` module defines a `Pool` object with an `AdminCap` for managing staking, including calculating exchange rates and distributing ALPHA rewards.
This package manages a CetusCompensator object, which acts as a vault for CETUS tokens and tracks compensation data. The init function creates and shares a CetusCompensator object. The collect_cetus_compensation function (and its inner variant) redeems CETUS from a CLMM Vester, updates the CetusCompensator's CETUS balance, and calculates an accumulated per-xtoken value, emitting a CollectCetusCompensationEvent. The get_user_compensation_amount (and its sui and base_a variants) functions calculate a user's potential compensation based on their receipt and the pool's accumulated values, without mutating the CetusCompensator. The user_collect_cetus_compensation (and its sui and base_a variants) functions allow users to claim their calculated CETUS compensation, updating their last recorded accumulated value and transferring CETUS from the CetusCompensator. All public/entry functions are gated by a version check.
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": "0xa511088cc13a632a5e8f9937028a77ae271832465e067360dd13f548fe934d1a",
"n_tx": 5008,
"n_successful_tx": 4407,
"n_distinct_epochs": 471,
"n_distinct_sponsors": 1,
"first_seen_cp": 30239336,
"last_seen_cp": 282176957,
"first_seen_ts_ms": 1711910965166,
"last_seen_ts_ms": 1780384004489,
"total_gas_spent_mist": 465255921678,
"n_self_sponsored_tx": 5007,
"n_sponsored_tx": 1,
"gas_price_p50": 750,
"gas_price_p95": 758,
"active_hours_top24": [
20,
21,
12,
13,
11,
22,
19,
9,
14,
10,
18,
15,
17,
23,
16,
8,
7,
0,
6,
1,
3,
2,
4,
5
],
"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).