Intuition

The following are out of scope for this program.

Accepted protocol design & privileged roles

• Actions taken by trusted roles within their documented powers: contract upgrades and parameter changes executed through the Upgrades / Parameters TimelockControllers and the governing multisig — pausing, upgrading, changing fees within configured caps, registering bonding curves, and setting the AtomWarden.
• Protocol fees accruing to the configured FeeProxy recipient by design.
• Bonding-curve rounding that favors the protocol and yields only dust-level differences with no profitable, repeatable extraction.
• First-depositor or share-inflation scenarios that do not overcome the protocol's initial-share-price and minimum-deposit mitigations.
• Reports premised on non-standard behavior of the TRUST token itself (fee-on-transfer, rebasing); TRUST is a standard ERC-20.

Execution environment — single-sequencer networks

• Both Base Mainnet and the Intuition Network are operated by a single centralized sequencer with no public mempool: pending transactions are not publicly gossiped and reach the sequencer only via RPC, and are ordered first-come-first-served without exposure to third-party reordering. Any finding whose exploitation depends on public-mempool access, transaction reordering, or MEV extraction — front-running, back-running, or sandwiching by other users or searchers — is out of scope on both networks, because that adversarial environment does not exist under the current sequencing model. User-configurable slippage bounds (min-shares / min-assets) remain the supported protection, and only defeating those bounds qualifies.

Cross-chain & infrastructure

• Cross-chain message latency, sequencer downtime, and reorg behavior inherent to the Intuition Network, the Caldera MetaLayer / Hyperlane bridge, and the Base settlement layer; only Intuition's own dispatcher and controller accounting logic is in scope.
• ERC-4337 EntryPoint, bundler, and paymaster behavior; only the AtomWallet / AtomWalletFactory / AtomWarden validation logic is in scope.
• Behavior of external systems the periphery integrates with — Aerodrome / Uniswap v3 routers, MetaLayer / Hyperlane, and Chainlink Automation — except where Intuition's own integration logic is at fault.
• Governance, admin, and proxy infrastructure: the TimelockControllers, all ProxyAdmin contracts, and the multisig signers.
• Shared third-party infrastructure deployed alongside the protocol: Multicall3, the ERC-4337 EntryPoint, and the SafeSingletonFactory.

Excluded assets

• Contracts not deployed to mainnet or not listed as in-scope assets.
• All testnet deployments (Base Sepolia, Intuition Sepolia).

Known issues & prior audits

• Any vulnerability already reported, publicly known, or already fixed in an unreleased branch.
• Findings from the protocol's public security audits, including the September 2025 audits by Consensys Diligence and the Code4rena April 2026 competitive audit.

Standard exclusions

• Attacks requiring leaked/compromised privileged keys, or control of a trusted role or governance majority.
• Generic economic or governance attacks (e.g. 51% attacks).
• Best-practice, informational, gas-optimization, missing-event, and NatSpec findings without a demonstrated impact.
• Automated scanner output without a working proof of concept.
• Sybil attacks, spam, and volumetric / DDoS attacks.
• Issues requiring social engineering, phishing, or physical attacks, or targeting Intuition employees, infrastructure, or off-chain services.
• Testing against public mainnet or testnet (use a local fork).
• Frontend, website, or UX issues with no contract-level fund or accounting impact.

The assessment of the extent of any potential indirect economic damage, defined as damage other than that evidenced by a PoC that showcases the direct exploitation of the vulnerability leading to impact, is at the full discretion of the project.