Security properties
The protocol's security rests on three design decisions:
- Immutability: the contracts have no upgrade function. The audited code is the code in execution, permanently.
- No administrative key: there is no multisig, owner or privileged function with access to the backing. The only operation that transfers wBTC out of the vault is redemption by burning EVA.
- Minimal surface: few functions, one formula, no external price oracle and no composability integrations. The attack surface is reduced by design.
These properties describe the Burn Vault (Core), the vault that sustains the base floor. The Burn Vault Boost is a separate contract: the balance, the covered quota and the burn quote are public on Arbiscan, and the contract was audited by CertiK.
Audits
| Auditor | Result | Report |
|---|---|---|
| Hacken | 10/10 | View report ↗ |
| CertiK | Auditado | View report ↗ |
Hacken and CertiK are security firms specialized in smart contract auditing and vulnerability analysis.
Audit scope
The scope covered the two points that sustain the protocol's guarantee:
- The Burn Vault mechanism, in particular the absence of any path to withdraw wBTC without burning the proportional amount of EVA.
- The tokenomics logic: fixed supply, no mint, permanent burn and the Burn Price calculation.
Limits and external dependencies
Auditing reduces risk without eliminating it. The protocol depends on external components with risks of their own: the wBTC wrapper and its custody, the Arbitrum infrastructure and the physical mining operation. The details are in Risks.