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 no primary object types. It provides two entry functions: `prove_game` verifies a BLS signature against a message and an object ID, emitting a `ProveBLSEvent` with the verification result. `fun_get_roll` hashes a byte vector using blake2b256 and then calculates a "roll" value (u64) from the hash, emitting a `ProveRollEvent` with this roll. The `roll` function iterates through the first 32 bytes of the input, combining them into a u256, then takes this modulo 38 to produce the final u64 roll.
This package, `prover`, does not manage any primary object types. It provides two public entry functions: `prove_game` and `fun_get_roll`. The `prove_game` function verifies a BLS12-381 signature using provided byte vectors for the message, signature, and an object ID, returning a boolean indicating success. The `fun_get_roll` function takes a byte vector, hashes it using Blake2b-256, and then calculates a `u64` "roll" value based on the first 32 bytes of the hash. There are no notable patterns like signature/allowlist gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties.
This package implements a Drand-based roulette game. It manages two primary object types: HouseData, which holds the house's balance and risk parameters for a specific coin type, and RouletteGame, which represents an individual game instance, storing its status, bets, and the random result. Public/entry functions allow an authorized HouseCap holder to initialize and configure the HouseData (setting max risk per game), and to manage the house's funds (top-up and withdraw). Players can place bets on an active RouletteGame, which updates the game's risk profile and the house's overall risk. The game can be closed and completed, using Drand randomness to determine the winning number and distributing payouts to winning bets from the HouseData's balance. Notable patterns include the use of a HouseCap for administrative control over HouseData, and the reliance on Drand for verifiable randomness in game completion.
This package implements a single-dice betting game. The primary object type is `House`, which manages a pool of funds (`Balance<Ty0>`) and game parameters like min/max stake and payout rate. `Game` objects represent individual bets, storing player, stake, guess, and a seed. Public/entry functions allow an `AdminCap` holder to create a `House`, deposit/withdraw funds from its pool, and update game parameters. Players can `start_game` by providing a guess, a seed, and a stake, which creates a `Game` object and deducts from the House's pool. The `settle` function resolves a game using a provided signature and seed, determining if the player won and transferring funds accordingly, or returning funds to the house. `batch_settle` allows multiple games to be settled simultaneously. The `challenge` function allows a player to reclaim their stake if a game is not settled within a certain epoch window. Notable patterns include: - AdminCap gating: Several functions require an `AdminCap` to
{
"wallet": "0x5207862b3823e88f8fb1fcdea9e7da9e813f746d9f9a3de71b734b74b31e71ff",
"n_tx": 102088,
"n_successful_tx": 102082,
"n_distinct_epochs": 161,
"n_distinct_sponsors": 0,
"first_seen_cp": 12275649,
"last_seen_cp": 32593410,
"first_seen_ts_ms": 1694006005526,
"last_seen_ts_ms": 1714259437946,
"total_gas_spent_mist": -763068638044,
"n_self_sponsored_tx": 102088,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 754,
"active_hours_top24": [
20,
18,
19,
17,
9,
12,
14,
6,
15,
16,
10,
3,
5,
11,
4,
21,
7,
8,
13,
2,
22,
23,
0,
1
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely UK / W. Europe / W. Africa.