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, `sentinel`, enables the creation and management of AI agents. The primary object types are `Agent` (representing an AI agent with its configuration, balance, and accumulated fees), `AgentRegistry` (a shared object mapping agent IDs to their object IDs), and `ProtocolConfig` (a shared object holding global parameters like fees, whitelisted tokens, and the protocol wallet). Public and entry functions allow users to: `register_agent` by providing an agent ID, cost, prompt, and initial funding, which creates an `Agent` object, an `AgentCap` for the creator, and registers the agent in the `AgentRegistry`; `fund_agent` to add funds to an existing agent's balance using its `AgentCap`; `claim_fees` to withdraw accumulated fees from an agent's balance by the agent's owner; and `request_attack` and `consume_prompt` which are part of an attack/defense mechanism where users can challenge agents and the outcome is verified by an external enclave. Notable patterns include: `
This Sui package, `sentinel`, primarily manages `Agent` objects, which represent AI agents with associated costs, system prompts, and balances in a specific token type. The package also includes `AgentRegistry` to track all registered agents, `ProtocolConfig` for global settings like fees and whitelisted tokens, and `AgentCap` for managing ownership of `Agent` objects. Public functions allow users to `register_agent` by providing agent details and a signed response from an enclave, `fund_agent` to deposit tokens into an agent's balance, and `claim_fees` to withdraw accumulated fees by the agent owner. The `request_attack` function initiates an attack on an agent, deducting a fee from the attacker and distributing it to the agent's balance and protocol fees. The `consume_prompt` function processes the results of an attack, verifying an enclave signature for the outcome, updating agent balances, and potentially marking an agent as defeated. Notable patterns include: signature gating for agent registration and prompt consumption (requiring enclave signatures), an allowlist for token
This package manages two primary object types: EnclaveConfig and Enclave. EnclaveConfig stores configuration details for an enclave, including its name, PCRs (Platform Configuration Registers), and a version number. Enclave objects represent registered enclaves, holding their public key, configuration version, and owner. Public functions allow creating new EnclaveConfig objects, registering new Enclave objects based on an EnclaveConfig and a NitroAttestationDocument, and verifying signatures against an Enclave's public key with time-gating. EnclaveConfig objects can be updated by an authorized Cap holder to change their PCRs or name, which also increments the config version. Old Enclave objects can be destroyed by their owner if their configuration version is outdated compared to the current EnclaveConfig. Notable patterns include: - An "admin cap" (Cap<Ty0>) is used for authorization to modify EnclaveConfig objects. - Time-gating is implemented in verify_signature, ensuring that the message timestamp is within a valid range relative to the current clock timestamp. - The system
This package manages `EnclaveConfig` and `Enclave` objects, which represent configurations and registered enclaves, respectively. Public functions allow creating a new `Cap` (capability) object, creating and sharing an `EnclaveConfig` object, and registering an `Enclave` object. It also provides functions to update the PCRs (Platform Configuration Registers) and name within an `EnclaveConfig`, and to verify signatures against an `Enclave`'s public key, incorporating time-gating. A `destroy_old_enclave` function allows an enclave's owner to remove it if its configuration version is outdated. The `Cap` object acts as an admin capability, gating modifications to `EnclaveConfig` objects.
{
"wallet": "0xc647dfdb8d8b575809902c9b86a26b6ace9f9271dfe5385468f503833a237177",
"n_tx": 1817,
"n_successful_tx": 1804,
"n_distinct_epochs": 71,
"n_distinct_sponsors": 1,
"first_seen_cp": 194479340,
"last_seen_cp": 280626197,
"first_seen_ts_ms": 1758970695621,
"last_seen_ts_ms": 1779961481616,
"total_gas_spent_mist": 4009095456,
"n_self_sponsored_tx": 1816,
"n_sponsored_tx": 1,
"gas_price_p50": 552.07306,
"gas_price_p95": 556,
"active_hours_top24": [
15,
2,
11,
12,
8,
7,
13,
3,
9,
4,
6,
14,
22,
16,
10,
1,
17,
18,
21,
5,
20,
19,
23,
0
],
"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.
area + brightness = call volume; hover for detail