Evidence areas
| Area | Evidence to maintain |
|---|---|
| Wallet roles | Agent, Mining, and Vault roles stay separated |
| Protected signing | approval flow, policy checks, controlled signing path |
| Custody controls | documented mode, recovery constraints, operator responsibilities |
| Agent access | local admin access, private network guidance, port exposure warnings |
| Skills and tasks | permissions, allowed tools, run history, stop controls, audit records |
| Mining controls | mining wallet isolation, capital controls, claims, recovery, logs |
| Network actions | offers, receipts, messages, delivery, and profile proof boundaries |
| Incident response | reporting path, update path, and status communication |
User-facing safety baseline
Operators can expect:- separate wallets for Agent, Mining, and Vault roles
- manual review or approved policy for wallet actions
- clear task and skill boundaries
- visible run history and receipts
- private admin access by default
- conservative public record sharing
- official launch verification before funding or bonding
Evidence map
This page is a public evidence map. Formal audits, release checksums, canary transactions, and official addresses belong in the relevant product docs and are linked from Official Verification.Read next
Wallet Safety
Understand wallet rules and protected signing.
Privacy
Understand privacy and agent access boundaries.
Official Verification
Verify launch and release material.