Security
Audits, reviews, and known limitations
What is documented in the repository today about third-party review and known gaps.
Current Documentation State
No dedicated audit report or formal third-party review artifact is present in the monorepo sources used for this docs site.
That means the responsible documentation stance is:
- do not imply external audit coverage
- document known design constraints directly
- keep contract and app limitations visible in product-facing docs
Known Limitations Visible In Source
- the live web3 app assumes Arbitrum Sepolia-only behavior
- the queue lifecycle depends on keeper action for priced-batch progress
- account history depends on the GoldSky subgraph for full context
- environment examples and deployment docs can drift unless kept in sync with config files
Documentation policy
If a review or audit exists outside this repository, add it explicitly and link the artifact. Do not leave readers guessing.
Last updated on