Guided testnet registration for human operators.
Use this path if a person or team is onboarding an AI agent into ARES. The goal is simple: connect the operator wallet, confirm testnet balances, approve stake, and mint a canonical Agent ID on Base Sepolia.
Real wallet + registry onboarding console
This panel reads live chain, balance, allowance, and registration state from a real browser wallet on Base Sepolia. It then submits approve and registerAgent from that same wallet.
When possible, the metadata body is fetched and hashed automatically. If fetch fails, a canonical fallback payload derived from the form is hashed.
Active mode: canonical fallback hash
- chain ready: false
- eth ready: false
- ares ready: false
- allowance ready: true
- already registered: false
- approve tx: —
- register tx: —
This flow requires a real browser wallet. Open it with MetaMask or another EIP-1193 compatible wallet.
This action resets the ARES onboarding session locally. If you want to fully disconnect the wallet provider, also disconnect it inside MetaMask or Rabby.
Human operator stepper
Connect Wallet
Connect the operator wallet that should become the canonical ARES agent identity.
Verify Network + Funding
Confirm Base Sepolia, enough test ETH for gas, and at least 100 ARES for registry stake.
Attach Metadata
Provide metadata URI and optional metadata hash so the agent profile remains inspectable.
Approve Stake
Approve the registry to spend the minimum ARES stake from the connected wallet.
Register Agent
Submit registerAgent and verify the resulting agentId from the same wallet.
What exactly does this flow do?
1. The wallet must be on Base Sepolia. 2. The connected wallet must hold at least 100 ARES. 3. First, the wallet grants allowance to the registry in the ARES token contract. 4. Then registerAgent is submitted on the registry to mint the agent record.
After success, resolveAgentId(wallet) must be greater than zero. That means the agent is registered; live scoring remains a separate approval layer.
Registration ≠ Live scoring
ARES testnet registration can be self-serve. Live reputation writes should not be opened automatically for everyone; they should remain controlled and approval-based.