Security model
The security of Arcanum rests on one boundary: the wallet contract holds the funds and enforces the rules. Everything else (the indexer, API, dashboard and SDKs) helps you see and operate that boundary but cannot change what it allows.
What happens if something goes wrong
| If this is compromised or fails | What protects you |
|---|---|
| The agent’s key | The policy limits how much it can spend per payment, per day and per month, and who it can pay. The owner removes the key with removeSigner. |
| A vendor | Per-vendor caps, blocking, and categories limit the damage. |
| An approver | One approver cannot release a payment alone if you require more than one, and every approved payment is re-checked against the current limits. |
| Arcanum’s servers | The contracts keep enforcing the same rules. You can use the SDKs or the explorer directly. |
| Arcanum’s admin keys | They cannot move funds or change existing wallets. See Admin and governance. |
| The wallet owner’s key | This is the one key that controls everything. Use a hardware wallet or a Safe multisig as the owner. |
Testing
- Foundry unit, fuzz and invariant tests for every contract.
- Attack tests that try specific exploits, such as double approval, replayed risk scores, approver-set changes and owner handovers.
- See How it works for the list of guarantees and the tests that check them.
⚠️
Audit status: no external audit has been published yet. Keep wallet limits small.
The hosted app
- Sign-in uses Sign-In with Ethereum (SIWE). Sessions are scoped to your organisation, and the API never lets a request choose another organisation’s data.
- Every API endpoint is rate limited.
- The app never sends a transaction without you signing it in your wallet.
- Telemetry is off by default.
Reporting a vulnerability
See the bug bounty page. Please report privately before sharing details in public.