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 defines a "Vault" system for managing assets with optional yield strategies. The primary object types are `Registry` and `Vault`. The `Registry` object tracks all `Vault` IDs by their owner and heir addresses using dynamic tables. The `Vault` object stores details like owner, heir, period, last confirmed heartbeat, yield strategy, asset kind, principal amount, and settlement status. Public/entry functions allow users to create new vaults, deposit assets (with or without yield), confirm heartbeats to extend the vault's active period, and settle vaults (claim assets) if the heartbeat period has elapsed. These functions mutate the `Registry` by adding/removing vault IDs and mutate the `Vault` object by updating its state (e.g., `last_confirmed_at`, `is_active`, `settled_at`). Notable patterns include: a shared `Registry` object, dynamic tables within the `Registry` to store lists of vault IDs, `VaultOwnerCap` for access control, time-gating for vault settlement (based on `period
This package defines a registry for managing "Vault" objects and their associated "VaultOwnerCap" objects. The Registry object tracks vaults by owner and heir addresses using dynamic fields (tables) and maintains a total vault count. Public functions allow creating vaults, depositing/withdrawing coins, confirming owner activity (heartbeat), claiming funds by the heir after a period of inactivity, and updating vault heir/period settings. Vaults can be closed by the owner, which transfers remaining funds to them and deactivates the vault. All vault operations are gated by the VaultOwnerCap and the vault's active status.
This Sui package defines a "Registry" for "Vault" objects, which are used for managing asset deposits with or without yield. The Registry tracks Vaults by owner and heir using dynamic tables. Public functions allow creating new Vaults, depositing assets into them (with different strategies for yield), confirming "heartbeats" to prevent settlement, and settling Vaults to transfer assets to the heir after a period of inactivity. Vaults are deactivated upon settlement, and events are emitted for key actions like creation, deposit, heartbeat, settlement, and deactivation. The package uses an owner cap pattern for controlling access to Vaults and includes time-gating logic for settlement.
This package defines a system for managing "Vault" objects, which are essentially escrow accounts for assets. The `registry` module maintains a shared `Registry` object that tracks all active vaults, indexed by both owner and heir addresses. The `vault` module defines the `Vault` object itself, along with functions for its creation, deposit, heartbeat, and settlement. The primary object type is `Vault`, which holds an owner, an heir, a heartbeat period, a yield strategy, and an asset kind. Public/entry functions allow users to `create_vault` (registering it in the `Registry` and transferring a `VaultOwnerCap` to the creator), `deposit` assets into a vault (with or without a yield strategy), `heartbeat` to confirm the owner's activity, and `settle` a vault (claiming its contents) if the heartbeat period has elapsed. The `Registry` object is mutated by `register_vault` and `reassign_heir` to update vault ownership and heir information. Notable patterns include the use of a shared
casualRule-based labels, conservative precision.
area + brightness = call volume; hover for detail
{
"wallet": "0xdc9ea8d573f239b013caac386ef0a610718c38349415643e5a6b490bc2fa2efa",
"n_tx": 16,
"n_successful_tx": 8,
"n_distinct_epochs": 4,
"n_distinct_sponsors": 0,
"first_seen_cp": 249168535,
"last_seen_cp": 251531476,
"first_seen_ts_ms": 1772158375156,
"last_seen_ts_ms": 1772771018724,
"total_gas_spent_mist": 311167950,
"n_self_sponsored_tx": 16,
"n_sponsored_tx": 0,
"gas_price_p50": 548,
"gas_price_p95": 551,
"active_hours_top24": [
17,
6,
4,
15,
2,
16,
10,
3
],
"primary_archetype": "casual",
"labels": [
"casual"
],
"label_confidence": [
0.7
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).