Protected floor
Your existing reward balance becomes a floor. Compounding only uses eligible tokens above it, within the allowance you approve.
Defense in depth: on-chain limits you sign, guarded execution, and an engineering record that says exactly what has and has not been verified.
Every release is checked against the recorded scopes below before anything can execute. These are our own engineering checks, not an independent audit, and the page says so on purpose.
| Scope | Coverage | Method | Date | Record |
|---|---|---|---|---|
| Permission & accounting | Protected floor, bounded allowance, expiry, owner rate, actual output, replay protection, revocation | Local SBF tests | Sep 2026 | View record |
| Price protection | Immature and stale history, substituted sources, spot deviation, minimum-output bypass, atomic rollback | Local guard tests | Sep 2026 | View record |
| Lending protocol | 364 native protocol tests, 67 SVM tests, all 58 instructions with a compute baseline | Local + SVM | Sep 2026 | View record |
| Hosted operations | Journal durability, ambiguous submissions, request limits, read-only readiness monitoring | Local + hosted checks | Sep 2026 | View record |
Rewards will be assessed by severity and potential impact on user funds. Send reproducible reports; critical findings are handled through coordinated disclosure.
The permission model is the product. Every limit below is enforced by the program and changed only with your signature.
Your existing reward balance becomes a floor. Compounding only uses eligible tokens above it, within the allowance you approve.
Connecting approves no spending. The executor's reward-token permission is limited to buying the selected coin and delivering it to your wallet.
The executor checks the reward floor, price bounds and net output. If a required check fails, the swap and accounting revert together.
Stop compounding in your position or revoke the delegation from your wallet. After confirmation, ANVIL cannot spend through that permission.
Good-faith researchers who report responsibly will not face legal action.
Initial response within 24 hours and updates until the report is closed.
We agree a disclosure timeline that protects users before details are published.
If you discovered a potential vulnerability, we want to hear from you.
Disclosure channelAt launch