WUYE registry architecture

A verifiable path from wallet to agent identity.

A wallet commits an agent manifest hash to the BOT Chain Agent Registry. The confirmed receipt establishes the onchain identity; persistence and model execution remain explicit offchain services.

Registration service map

Wallet transaction, contract receipt, and separate offchain services

Transaction pathRegistry configured
Authorization
Wallet transaction
Registry
Configured contract
Verification
Confirmed receipt
Execution
Optional hosting

Registry configured

BOT Chain Agent Registry

0x9CE6FE4Cc3bBd809b262A5C762B65fbECE0A35eb
View registry contract

Service ledger

What each registration boundary does.

Contract state proves wallet ownership of a manifest commitment. Hosted storage and AI execution remain separate, optional infrastructure.

Wallet Transaction
Interface ready
Connects an injected wallet, selects BOT Chain, and requests approval for the registry transaction in the wallet.
Manifest Commitment
Interface ready
Canonicalizes the agent profile locally and submits only its deterministic manifest hash to the contract.
BOT Chain Registry
Configured
Routes registration to the configured Agent Registry, which records the owner, manifest hash, and onchain agent identifier.
Receipt Verification
Interface ready
Waits for confirmation and matches the receipt sender, contract target, and AgentRegistered event to the wallet and manifest.
Hosted Agent Runtime
Optional hosting
A separate authenticated service can independently verify the receipt and persist owner-scoped agents and task records.
AI Gateway
Provider required
Offchain inference requires a hosted runtime and model-provider credentials; it is not executed by the registry contract.

Verification boundary

Agent registration is a blockchain transaction.

Wallet sign-in and registry registration are different actions. Sign-in proves account control for an optional hosted service; registration changes contract state, requires gas, and produces a verifiable receipt.

Wallet authorization
Blockchain transaction

Calls the registry from the connected owner wallet and requires network gas.

Registry commitment
Owner + manifest hash

Creates the agent identifier and durable manifest commitment in contract state.

Agent execution
Separate offchain runtime

Keeps instructions, prompts, results, credentials, and model execution offchain.

When hosted persistence is enabled, the server independently checks the transaction sender, registry target, confirmation depth, receipt event, and current contract record before saving an agent.

Register an agent