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 manages two primary object types: ChopLockerAdmin, which is an administrative capability, and PoolConfig, which holds staking pool configuration and reward balances for a specific token type. It also defines a Lock object, representing a user's staked tokens. The public/entry functions allow an admin to create new PoolConfig objects, fund reward balances within a PoolConfig using a TreasuryCap, and users to lock tokens into a PoolConfig. Locking tokens updates the PoolConfig's total_staked, calculates an APY, and creates a Lock object that is transferred to the staker. Users can also withdraw tokens from a Lock object, which checks if the lock duration has passed, updates the PoolConfig's total_staked, and transfers the original staked tokens and calculated rewards back to the user. Notable patterns include signature gating for admin functions (requiring a ChopLockerAdmin object), time-gating for withdrawing tokens (checking end_time against the current clock timestamp), and the use of generic types (Ty0) to support different token types. The Pool
This package manages staking pools for various token types. The primary object types are ChopLockerAdmin (an admin capability), PoolAdmin (a capability for managing a specific pool), PoolDirectory (a shared object listing available token types), PoolConfig (a shared object holding configuration and state for each staking pool), and Lock (a dynamic field representing a user's locked tokens). Public functions allow an admin to create new staking pools (`new_pool_config`), fund rewards into a pool (`fund_rewards` and `fund_rewards_override`), and users to lock tokens (`lock_tokens`) and withdraw them after a time-gated period (`withdraw_tokens`). The `lock_tokens` function calculates rewards based on APY, total staked, and a depletion factor, and transfers rewards from the pool's balance to the user's lock. The `withdraw_tokens` function transfers both the principal and earned rewards back to the user after the lock period has ended. The package uses shared objects for PoolDirectory and PoolConfig, and admin capabilities for controlling pool creation and reward funding
This package manages 'ChopLockerAdmin' and 'PoolConfig' objects, which configure staking pools, and 'Lock' objects, representing individual user stakes. The 'init' function creates and transfers a 'ChopLockerAdmin' object to the deployer. The 'new_pool_config' function, callable only by the admin, creates a new staking pool with an initial reward balance. The 'fund_rewards' function, also admin-gated, adds more rewards to a specified pool. The 'lock_tokens' function allows users to stake tokens into a pool for a specified duration, calculating and locking in an APY, and creating a 'Lock' object for the user. The 'withdraw_tokens' function enables users to reclaim their staked tokens and earned rewards after the lock-up period has ended. Notable patterns include admin-gating for pool creation and funding, time-gating for withdrawing staked tokens, and the use of 'Balance' objects for managing token amounts within the pools and locks.
This Sui package, "chop_locker", manages staking pools and token locking. The primary object types are `ChopLockerAdmin`, `PoolConfig<Ty0>`, and `Lock<Ty0>`. The `init` function creates and transfers a `ChopLockerAdmin` object to the deployer. The `new_pool_config` function creates a new `PoolConfig` object, initializing it with a provided `Coin` as initial rewards, and shares it. The `fund_rewards` function allows the admin to mint new tokens using a `TreasuryCap` and add them to a `PoolConfig`'s reward balance. The `lock_tokens` entry function allows users to stake tokens into a `PoolConfig`, creating a `Lock` object with a start time, end time, and calculated APY, then transfers the `Lock` object to the sender. The `withdraw_tokens` entry function allows users to withdraw their locked tokens and accrued rewards from a `Lock` object once the `end_time` has passed, deleting the `
This package defines a staking/locking mechanism for tokens. It manages PoolConfig objects, which represent staking pools for a specific token type, and Lock objects, which represent individual user stakes. Public/entry functions allow an admin to create new staking pools (new_pool_config), fund rewards into existing pools (fund_rewards_override, fund_rewards, fund_rewards2, fund_rewards3), and adjust the maximum APY for a pool (change_max_apy, change_max_apy2, change_max_apy3). Users can lock their tokens (lock_tokens) into a PoolConfig and later withdraw them along with earned rewards (withdraw_tokens) after a time-gated period. The system uses multiple admin capabilities (ChopLockerAdmin, PoolAdmin, PoolAdmin2, PoolAdmin3) for different levels of control, and it calculates rewards based on APY, base reward rates, and depletion factors.
flipperRule-based labels, conservative precision.
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": "0x0bb83b54135a88456cef322a8fba5ee496e7e751c5b07ffc119cceed9e309297",
"n_tx": 437,
"n_successful_tx": 412,
"n_distinct_epochs": 53,
"n_distinct_sponsors": 2,
"first_seen_cp": 82074045,
"last_seen_cp": 273525077,
"first_seen_ts_ms": 1732156084315,
"last_seen_ts_ms": 1778266401952,
"total_gas_spent_mist": 3547745008,
"n_self_sponsored_tx": 422,
"n_sponsored_tx": 15,
"gas_price_p50": 740.625,
"gas_price_p95": 750,
"active_hours_top24": [
19,
20,
2,
4,
16,
18,
22,
17,
21,
13,
3,
0,
5,
15,
14,
1,
23
],
"primary_archetype": "flipper",
"labels": [
"flipper"
],
"label_confidence": [
0.5975
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely N. America (Central–Eastern).