Security · S6
Audits and bug bounty
Has the code been audited at a pinned commit, were findings fixed traceably, and is there a live bounty?
Why it matters
An audit tells you what a competent reviewer found at one commit. Its value depends on whether the deployed code is that commit and whether findings were fixed.
Scoring anchors
| Audit report linked, audited commit pinned, each finding's resolution linked to a commit, live bounty program with scope in the repo. | |
| Audit pinned to a commit, resolutions not individually linked. | |
| Audit report only (documented tier cap). | |
| None. | |
| No admissible evidence submitted yet. Counts as 0 in the pillar. |
Admissible evidence
- Audit report PDF documented
- Commit matching the audited hash verified
- Fix commits verified
Common failures
- Audit of a previous version presented as covering the deployed contracts.
Current ratings
| Provider | Score | Finding |
|---|---|---|
| Aleo (credits.aleo private transfers) | We found no audit report pinned to a commit in snarkVM, snarkOS or the SDK; snarkVM's SECURITY.md (L1-L11) asks for reports by GitHub issue or email and mentions no bounty. External audits and bounty programmes are known by reputation only, which we do not score. | |
| AnomaPay | Audit reports exist and are pinned to commits, but the deployed adapter was built from a later tag, findings were not traced to fix commits here, and we found no bug bounty. Scored 1. | |
| Avalanche Card | No admissible evidence yet. | |
| Avici Card | No admissible evidence yet. | |
| Aztec (Alpha mainnet private token transfers) | Audit reports exist for the L1 contracts and parts of the proving library, but we did not read them for pinned commits, and the project's own docs say no part of the stack has been fully audited and some circuits are under-constrained. A bounty page is linked, with scope outside the repo. Scored 1: reports only, nothing pinned. | |
| Bitget Wallet Card | No admissible evidence yet. | |
| Blanksquare (Shielder) | One audit report, pinned to a commit before several contract changes that are now deployed; no per-finding fix links reviewed, and no bug bounty or SECURITY file found. Scored 1. | |
| COCA Card | No admissible evidence yet. | |
| Coinbase Commerce (Onchain Payment Protocol) | We found no audit report for any Transfers deployment. The live Base contract (0x0305…b7a8) carries a fix that is not in the repo. Coinbase runs a bug bounty on HackerOne, but no repo states its scope. | |
| Curvy | An audit pinned to 5f6e43cf exists, with findings marked fixed. The README says the audited contracts are the V1 stack. The deployed contracts are the greenfield V2 rewrite (develop @e996fe71), which the report does not cover. We found no bug bounty. Scored 1: an audit of a previous version. | |
| Daimo Pay | The only audit in the repo covers the earlier Universal Address contracts. Those files were deleted in January 2026, and the audited commits are not in the public repo. We found no audit of the deployed DepositAddressManager, DepositAddress, or DaimoPayExecutor. We found no bug bounty in the repo, the docs, or daimo.com/.well-known/security.txt (404); the NatSpec lists a security@daimo.com contact. Judgment call: we score 0 and not 1, because an audit of a previous version does not cover the deployed contracts, which is the listed common failure. | |
| Deblock Card | No admissible evidence yet. | |
| Ethena Pay | No admissible evidence yet. | |
| ether.fi Cash | Audits are pinned to commits and name per-finding fix commits; a live bounty exists. Two things are missing for 3: the bounty scope is not in the repo, and the deployed implementations (Oct 2026) are far past the audited commits, with later modules covered by separate reports I did not map one by one. Lower anchor taken = 2. | |
| Exa Card | Audits exist, with pinned commits and per-finding fix commits, but the deployed OP Mainnet plugin is not the audited commit. I found no bug bounty in any exactly repo. Judgment call: an audit of a neighbouring version does not cover the deployed contract, so this is held at "audit report only" (1). | |
| Fluidkey | Audit reports for the kit and the earn module are in their repos. We could not extract the audited commits from the PDFs, so we cannot tie them to the deployed code. The app and backend have no published audit, and we found no bounty. Scored 1. | |
| Fuse Card | The settlement program has audits pinned to a commit and a bounty process. The audited commit matches observed spending-limit behaviour, but no verified build ties it to the deployed bytecode (O1 = 0), and finding fixes are not linked. Fuse's own app and Bridge integration have no published audit. Judgment call: 1 rather than 2 because deployed-equals-audited is unproven. | |
| Gnosis Pay | The Safe, Delay and Roles code that holds and gates funds has published audits, though none is pinned to the deployed commits. No audit was found for Gnosis Pay's own Spender or Bouncer contracts, no bug bounty is in any gnosispay repo, and I found no public post-mortem for the June 2026 incident. Documented tier caps this at 1. Judgment call: 1 applies to the fund-holding modules; Gnosis Pay's own code on its own would score 0. | |
| HesabPay | No admissible evidence yet. | |
| Hinkal | Six audit reports are linked from the docs, and a HackenProof bounty is listed as ongoing. We did not tie any report to the deployed commit (the contracts were deployed at block 25543753 in 2026), and no fixes are linked to commits in the repo. Scored 1: audit reports only. | |
| Holyheld Card | No admissible evidence yet. | |
| Houdini Swap | No admissible evidence yet. | |
| Hyperbeat Card | Two audit reports are public and pin commits, but the audited repo is private and the deployed contracts are unverified, so neither the audited commit nor the fixes can be matched to what runs. No bug bounty found. Judgment call: audit report only, so 1. | |
| Jupiter Card | No admissible evidence yet. | |
| M-Pesa | No admissible evidence yet. | |
| MetaMask Card | No admissible evidence yet. | |
| Opera MiniPay | No admissible evidence yet. | |
| Monero | Audit reports exist for protocol components (CLSAG, Bulletproofs), and a bug bounty with scope is in a repo. We did not read the audit PDFs for a pinned commit, and the current release has not been shown to be the audited code. Scored 1: audit reports, no pinned commit shown. | |
| Nullmask | No audit, by the operator's own statement; no bug bounty found. Scored 0. | |
| Oobit Card | No admissible evidence yet. | |
| Payy Card | No admissible evidence yet. | |
| Phantom Cash | No admissible evidence yet. | |
| Plasma One | No admissible evidence yet. | |
| Privacy Pools (0xbow) | The deployed Entrypoint implementation equals Entrypoint.sol at the audited commit 238e3594, and the pool sources equal the files at the audited final commit 532eaa8e, apart from a trailing newline. Oxorio links fix commits for its findings. There is no live bounty programme with scope, so not 3. Scored 2. | |
| Railgun | An audit report exists for an early version of the contracts and circuits; it does not cover the deployed implementation (deployed at block 25641630, with Action events and TokenBlocklist). We found no audit report, SECURITY file or bounty programme in the Railgun repos or docs. Judgment call: 1 for an audit of a prior version, as for Tornado Cash; no audit of the deployed code was found. | |
| Request Network | We found no audit report, audited commit, or bug bounty for the deployed payment contracts. Payers are told the contracts are audited, but no report is linked anywhere we could find. The repo does run static analysis (Slither) and fuzzing (Echidna) in CI, which this criterion does not credit. | |
| Rizon Card | No admissible evidence yet. | |
| SafePal Card | No admissible evidence yet. | |
| Solayer Card (Emerald Card / Solayer Pay) | No admissible evidence yet. | |
| Tongo (confidential ERC-20 on Starknet) | One audit, from October 2025, predates the v2 Vault, ledger and Relayer architecture now deployed. We found no audited commit hash in the report text and did not trace fixes. No bug bounty or SECURITY file. Scored 1: audit report only. | |
| Tornado Cash (Classic pools) | ABDK audited the contracts and circuits at a pinned commit, and the report links fix commits. The deployed code was built from tag v2.0, 107 commits later, and we could not confirm every change after the audit was reviewed. There is no live bug bounty. The router, registries and governance upgrades were not reviewed here. Judgment call: 1 rather than 2, because the audited commit is not the deployed commit. | |
| Tria | No admissible evidence yet. | |
| Tuyo Card | No admissible evidence yet. | |
| Umbra Cash | Audit reports are linked, but we could not read an audited commit from either report, so we cannot tie them to the deployed bytecode. No bug bounty or SECURITY file found. Scored 1: audit report only. | |
| Wirex One | No admissible evidence yet. | |
| Wise | No admissible evidence yet. | |
| WORM (BETH proof-of-burn) | Two audit reports are linked. The yAudit report predates the February 2026 BETH deployment and is tagged as a circuit review. We could not extract an audited commit from either report, so we cannot tie them to the deployed commit eab0f53b. We found no bug bounty and no SECURITY file. Scored 1: audit reports only. | |
| XPlace Card | No admissible evidence yet. | |
| Zcash (shielded transfers) | We found no audit report pinned to a commit in the node, protocol-library or wallet repos, and could not load zodl.com (HTTP 403 to automated requests). Zebra's SECURITY.md (L107) says the Zcash Foundation runs no bug bounty. ZIP 257 records that the critical Orchard bug of May 2026 was found during a commissioned AI-assisted audit, but that is not an audit report. External audit reports exist by reputation only, which we do not score. | |
| zERC20 (zBNB on BNB Chain) | The docs and website name no audit or bug bounty. The personal-account snapshot contains audit/zksecurity-audit.pdf, but we could not extract its text to confirm scope or an audited commit, and the official repository is not public. |