Audit status
What exists instead
179 passing tests, including 14 that execute against live Robinhood Chain state and 9 protocol-wide invariants over 4,096 randomised calls each. Details in test results.
That is a substantial suite. It is not an audit.
The difference
A test suite demonstrates that the properties the author thought to check hold under conditions the author thought to create. Both halves of that sentence are limitations.
An audit brings people who did not write the code, are not attached to its design, and are specifically looking for the assumptions the author did not notice they were making. That is a categorically different exercise, and no amount of self-testing substitutes for it.
What the tests do give confidence about
- The accounting reconciles. Nine invariants assert it across randomised sequences.
- The external integrations work against real contracts, not mocks.
- The stated bounds are actually enforced on chain.
- Two real bugs were found and fixed. See build status.
What they cannot tell you
- Whether an economic attack exists that nobody modelled.
- Whether a Solidity or compiler subtlety was missed.
- Whether the Pons integration has an edge case outside the tested phases.
- Whether the design itself is sound, as opposed to correctly implemented.
Language used elsewhere on this site
Deliberately constrained. You will not find:
- "Audited" or "security reviewed".
- "Safe" or "risk-free".
- A green shield, badge or checkmark implying review.
- A test count presented as though it implied safety.
The status page shows health checks, which are liveness checks, not security claims. A verified badge means source matches bytecode — nothing more.
If an audit happens
This page will name the firm, link the report in full including unfixed findings, state the commit hash reviewed, and note anything the audit explicitly did not cover.
Until then it says what it says now.