The core value-bearing contracts on Chain 2800 were analyzed with Slither 0.11.5, the open-source static analyzer from Trail of Bits, against the Solidity 0.8.23 compiler. This report is published in full, findings and caveats included.
Read this first, honestly. This is an automated static-analysis pass, not a manual line-by-line audit and not an economic or formal-verification review by a named third-party firm. A named human audit (for example Code4rena, Cantina, Sherlock, or a Trail of Bits engagement) remains on the roadmap. Until then, the live adversarial mechanism is the AERE bug bounty, and this report is one honest layer of assurance rather than a substitute for a full third-party engagement.
hardhat.config.js), OpenZeppelin 4.9.6.| Contract | Area | Analyzed |
|---|---|---|
| AereToken | Native token (2.8B fixed) | yes |
| AereSink | Immutable 3-bucket fee router | yes |
| AereFeeBurnVault | Sealed 37.5% base-fee burn | yes |
| AereCoinbaseSplitter / V2 | Coinbase split | yes |
| sAERE | ERC-4626 staking receipt | yes |
| AereLockedStaking | Fixed-term staking | yes |
| AereZKScreen (v3) | zk-KYC screening | yes |
| AereCompliancePool | Compliant privacy pool | yes |
| AereSanctionsRegistry | OFAC registry | yes |
| AereLendingMarket / Oracle | Isolated lending | yes |
| AereInsuranceFund | Bad-debt cover | yes |
| AerePQCVerifier | Post-quantum WOTS+ verifier | yes |
Zero genuine high-severity vulnerabilities.
Slither raised 4 "high" flags. Each resolves to a known false positive inside the audited OpenZeppelin 4.9.6 library, or to an explicitly by-design action that cannot harm users:
| Flag | Where | Verdict |
|---|---|---|
incorrect-exp | OpenZeppelin Math.mulDiv (via sAERE) | False positive. Intentional bit trick in the OZ library, not AERE code. |
reentrancy-eth | sAERE._deposit | False positive. Standard ERC-4626 pattern, no ETH in contract; balance re-cached after transfer. |
reentrancy-eth | sAERE._withdraw | False positive. Same pattern, state re-cached post-transfer. |
unchecked-transfer | AereCompliancePool.dismissAssociationRootChallenge | By design. Best-effort burn of an already-collected griefer bond to a burn address; failure cannot harm users or the protocol (documented in source). |
62 raw medium flags reduce to a handful of distinct patterns. None is assessed as practically exploitable by an external attacker against user funds:
mulDiv, which are false positives). Rounding is conservative and favors protocol solvency.== 0 uninitialized-slot and sentinel checks, not balance-equality traps. Mostly false positives.ReentrancyGuard with standard ERC-20s; would only bite with a malicious hooked token (ERC-777) that the protocol does not list. Disclosed with the token-allowlist assumption noted.approve(): approvals are to the protocol's own trusted immutable addresses and reset to zero after use. Best-practice nit; SafeERC20 planned for the next non-immutable revision.Low (57): block.timestamp comparisons (33), benign reentrancy (17), reentrancy-in-events (6), missing zero-check (1).
Informational (117): naming convention (43, immutable UPPER_CASE style), dead code (24), low-level calls (17), solc-version advisory (15), pragma (11), and minor items. Pinning the three floating-pragma files to an exact 0.8.23 is a trivial hardening note.
Many of these contracts are already deployed and immutable on Chain 2800 (sAERE, AereCompliancePool, AereZKScreen v3, AerePQCVerifier, the lending market and oracle, AereCoinbaseSplitter, AereFeeBurnVault, AereLockedStaking). Findings on those contracts are disclosed here transparently rather than silently patched, because they cannot be patched. All are low-risk or false positives.
AERE Network's core value-bearing contracts were analyzed with Slither 0.11.5 (Trail of Bits) against the Solidity 0.8.23 compiler. All 14 audited contracts, covering the token, staking, fee and burn economics, the compliance and zk-screening layer, the lending market and oracle, the insurance fund, and the post-quantum verifier, compiled and analyzed cleanly. Static analysis surfaced no genuine high-severity vulnerabilities: every high flag resolved to either a known false positive inside the audited OpenZeppelin 4.9.6 library or an explicitly by-design best-effort token burn that cannot harm users. The medium-severity findings are dominated by conservative fixed-point rounding, strict-equality sentinel checks, and unchecked approve() return values on calls to the protocol's own trusted immutable contracts, none assessed as externally exploitable against user funds. Remaining items are informational hardening notes. Findings on already-deployed immutable contracts are disclosed transparently. This is an automated static-analysis pass, not a manual line-by-line audit or economic and formal-verification review, and should be read as one honest layer of assurance rather than a substitute for a full third-party engagement.
Report generated with Slither 0.11.5. Raw per-contract JSON and markdown outputs are retained by the Foundation. Re-run the analysis yourself: the contract sources are in the public repository, and Slither is open source. Report an issue or claim a bounty at the bug bounty.