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 two modules: `StakeManagement` and `deposit`. The `StakeManagement` module manages `Staker` objects, which hold a balance of a generic token type, the lender's address, and a start time. Public functions allow users to `Stake` tokens, creating a `Staker` object and emitting a `StakeAdded` event, and `Withdraw` staked tokens, destroying the `Staker` object and emitting a `StakeWithdrawn` event. Other public functions (`Treasury`, `Account`, `Rate`, `Limit`, `Setting`, `Token`, `Pool`, `Status`, `Payment`, `Reward`) primarily emit events related to various configuration settings, treasury management, reward distribution, and platform commissions, without directly mutating on-chain objects in the provided IR. The `deposit` module manages `RewardDeposit` objects, which hold a balance of a generic token type, the depositor's address, and the recipient's address. The `LendReward` function creates a `RewardDeposit` object, shares it, and emits
This package defines an `AirdropEvent` struct to record airdrop details. The `send` public/entry function distributes a specified `Coin` amount to multiple recipients. It takes a mutable `Coin` object, a vector of recipient addresses, a vector of corresponding amounts, and a mutable `TxContext`. The function iterates through the recipients, splits the input `Coin` into smaller `Coin` objects, and transfers them to each recipient. It also emits an `AirdropEvent` for each successful transfer, containing the recipient's address, the amount, and the coin type. A notable pattern is the use of `event::emit` to log airdrop activities. The function aborts if the number of recipients and amounts do not match.
This Sui package defines a Vault object for managing SUI deposits and rewards. Users can deposit SUI into the Vault, receiving a corresponding VAULT coin and a unique deposit ID. Managers, approved by an AdminCap holder, can also deposit SUI into existing user deposits or commit rewards to them. Users can withdraw their SUI deposits and earned rewards. The Vault tracks total deposited SUI, reward SUI, and individual deposit information including user, manager, strategy, amount, and rewards earned, using dynamic fields (tables) for deposits and approved managers. Events are emitted for various actions like deposits, withdrawals, and manager approvals.
This package defines a space-themed game with various interconnected modules. The primary object types managed are events representing game actions and state changes, such as alliances (Pact, Motion), army deployments (Phalanx), market transactions (Vault, Claimon), building upgrades (Foundation), fleet movements (Formation, Armada), resource declarations (Capita, Flux), planet management (Patarix, Patarian, Phantom, Pateron, Settler), player settings (Settings), production levels (Level), research doctrines (Doctrine), tactical improvements (Model), cross-chain teleportation (Bridge), and war outcomes (Battle, Loss, Loot). All public/entry functions in this package solely emit events, indicating that the actual game state changes and logic are likely handled off-chain or by other contracts that consume these events. A notable pattern is the consistent use of `patarian_id` and `phantom_addr` across many event types, suggesting a hierarchical structure of players and their associated game entities.
This Sui package primarily manages various event-like objects representing actions and states within a game or simulation. The primary object types are Pact, Motion, Phalanx, Vault, Claimon, Foundation, Formation, Flux, Capita, Anchor, Leave, Patarix, Patarian, Phantom, Pateron, Settler, Doctrine, Battle, Loss, and Loot. All public/entry functions in these modules (e.g., Forge, Execute, DeployPhalanx, Supply, Mint, UpgradeFoundation, Cohort, Declaration, Mobilize, Focus, Release, Genesis, EstablishPatarian, EstablishPhantom, EstablishPateron, EstablishSettler, EvolveDoctrine, Clash, Units, Captured) solely emit events by packing their input arguments into the corresponding struct and calling `event::emit`. There are no mutations of on-chain state objects, no signature/allowlist gating, time-gating, dynamic fields, admin caps, or vault/escrow mechanisms present in the provided IR. The package's core functionality appears to be logging game-related actions and state changes as events
{
"wallet": "0xa6e64c357c934e5f169855c7f5390bbf352dceb3e2cbf0b7743e985e0da7ced8",
"n_tx": 46,
"n_successful_tx": 44,
"n_distinct_epochs": 32,
"n_distinct_sponsors": 0,
"first_seen_cp": 183742189,
"last_seen_cp": 266365374,
"first_seen_ts_ms": 1756376063710,
"last_seen_ts_ms": 1776515647769,
"total_gas_spent_mist": 1297191880,
"n_self_sponsored_tx": 46,
"n_sponsored_tx": 0,
"gas_price_p50": 505,
"gas_price_p95": 557,
"active_hours_top24": [
10,
12,
13,
21,
9,
14,
7,
6,
15,
16,
8,
19,
11,
22,
20,
17,
23
],
"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.