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 package manages a `BirdVault` object, which holds an optional validator signature, and `AdminCap` for administrative actions. The `init` function creates and shares a `BirdVault` and transfers an `AdminCap` to the deployer. The `updateValidator` function, callable only by the `AdminCap` holder, updates the validator signature within the `BirdVault` after a version check. The `feedWorm` and `preyBird` functions process signed messages from a validator (verified against the `BirdVault`'s validator), perform version checks, and emit events (`FeedWormEvent` or `PreyBirdEvent`) after validating the sender and updating a user's archive nonce. The `feedWorm` function also burns a `BirdNFT`. The `claimPreyReward` function similarly processes a validator-signed message, verifies the sender, and emits a `ClaimPreyRewardEvent` after updating the user's archive nonce. All public/entry functions include version checks and
This package primarily manages `Coin` objects of various types, facilitating swaps between them. Public/entry functions like `swap_a2b` and `swap_b2a` across different modules (afsui, aftermath, bluemove, cetus) allow users to exchange one type of coin for another, often interacting with liquidity pools (`Pool`, `StakedSuiVault`) and mutating their states. These swap functions also typically call a `config::pay_fee` function, indicating a fee mechanism, and emit swap events. A notable pattern is the use of generic type parameters (`Ty0`, `Ty1`, `Ty2`) for coins and pools, allowing for flexible asset handling. The `cetus` module additionally features flash swap functionalities (`flash_swap_a2b`, `flash_swap_b2a`, `repay_flash_swap_a2b`, `repay_flash_swap_b2a`) which involve borrowing and repaying assets within a single transaction, and it interacts with a `Partner` object, suggesting potential
This Sui package manages "BirdArchieve" objects, which represent user accounts and can hold a "BirdGhost" (a quantity of something) and an optional "NFTLite" (a simplified NFT). It also manages "RewardPool" objects, which hold coins of a generic type and have an active status and a reward limit. Users can register to obtain a "BirdArchieve" object. They can then "mineBird" or "mineNft" by providing a signed message, which updates the amount in their "BirdGhost" or the details of their "NFTLite" within their "BirdArchieve" object, respectively. These mining operations are gated by a nonce and a signature verification against a "BirdStore" object. Admin functions, gated by an "AdminCap", allow updating a validator in the "BirdStore" and creating/configuring "RewardPool" objects. A "TreasureCap" allows emergency withdrawals from "RewardPool"s. Users can claim rewards from "RewardPool"s, also gated by signature verification, nonce, and the reward pool'
This package manages `BirdVault` objects, which can optionally hold a single `NFTLite` representing a bird. The `init` function creates an `AdminCap` (transferred to the deployer) and a shared `BirdVault`. The `updateValidator` function, gated by `AdminCap`, allows updating a validator signature for off-chain actions. `feedWorm` and `preyBird` are entry functions that require a signature verification against the `BirdVault`'s validator and interact with a `UserArchieve` object (likely for nonce management). `feedWorm` burns a `BirdNFT` and emits a `FeedWormEvent`. `preyBird` either adds a new `NFTLite` to the `BirdVault` or updates an existing one, setting its `preying` status and `prey_unblock_at` time, and emits a `PreyBirdEvent`. `claimPreyReward` also requires signature verification and updates a nonce in `UserArchieve`, emitting a `ClaimPreyRewardEvent`. Notable
This Sui package manages "BirdArchieve" objects, which represent a user's bird and potentially an associated NFT. It also manages "BirdStore" and "BirdReg" objects, which appear to be shared global registries. The package utilizes an "AdminCap" for administrative functions and a "TreasureCap" for emergency withdrawals from reward pools. Public functions allow users to register a "BirdArchieve", "mine" (deposit) either a bird or an NFT into their "BirdArchieve", and "claim" rewards from a "RewardPool". Administrative functions, gated by the "AdminCap", include updating a validator for signatures and configuring reward pools. A "TreasureCap" is required for emergency withdrawals from reward pools. Notable patterns include signature gating for "mineBird", "mineNft", and "claimReward" functions, using a "BirdStore" object to verify signatures. The package also uses dynamic fields (implicitly through `table::add`) and shared objects for global registries and reward pools. Reward pools are generic over the coin type. The `sponsor_
{
"wallet": "0xc37ce899eb568f490a521590787b167e65300d15819c85c4a12ee8480f2c3554",
"n_tx": 1711,
"n_successful_tx": 1622,
"n_distinct_epochs": 158,
"n_distinct_sponsors": 0,
"first_seen_cp": 14617603,
"last_seen_cp": 269494897,
"first_seen_ts_ms": 1696353714947,
"last_seen_ts_ms": 1777273892960,
"total_gas_spent_mist": 42432218672,
"n_self_sponsored_tx": 1711,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
10,
13,
6,
8,
4,
12,
5,
9,
7,
16,
18,
17,
11,
21,
14,
15,
19,
20,
3,
2,
22
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely E. / SE Asia.