Axiom

Axiom is the first ZK coprocessor scaling data-rich applications on Ethereum. Axiom provides smart contracts trustless access to all on-chain historic data and arbitrary expressive compute over it. Queries into Axiom are trustlessly fulfilled with ZK-verified results on-chain.

For more information about Axiom, please visit www.axiom.xyz

Axiom provides rewards in USDC. For more details about the payment process, please view the Rewards by Threat Level section further below.

KYC Requirement

The provision of KYC is required to receive a reward for this bug bounty program where the following information will be required to be provided:

• National ID
• Utility Bill

KYC information is only required on confirmation of the validity of a bug report.

Responsible Publication

Axiom adheres to category 3. This Policy determines what information whitehats are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.

Primacy of Impact vs Primacy of Rules

Axiom adheres to the Primacy of Impact for the following severity levels:

• Smart Contract - Critical

If a category’s severity level is covered within the Primacy of Impact, it means that even if the impacted asset is not in-scope but is owned by the project, then it would be considered as in-scope of the bug bounty program as long as it involves an impact under that respective severity level. When submitting a report, just select the Primacy of Impact asset placeholder. If the team behind this project has multiple projects, those other projects are not covered under the Primacy of Impact of this program. Instead, check if those other projects have a bug bounty program on Immunefi.

Testnet and mock files are not covered under the Primacy of Impact.

All other severity levels not listed here are considered under the Primacy of Rules, which means that they are bound by the terms of the bug bounty program.

Known Issue Assurance

Axiom commits to providing Known Issue Assurance to bug submissions through their program. This means that Axiom will either disclose known issues publicly or at the very least privately via a self-reported bug submission in order to allow for a more objective and streamlined mediation process to prove that an issue is known. Otherwise, assuming the bug report itself is valid, it would result in the bug report being considered in-scope and due 100% of the reward with respect to the bug bounty program terms.

Immunefi Standard Badge

Axiom has satisfied the requirements for the Immunefi Standard Badge, which is given to projects that adhere to our best practices.

Invoicing Information

If needed by the security researcher, Axiom is able to provide the necessary information for the proper issuance of an invoice. This includes:

• Legal Entity
• Registered Address
• Email

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below.

Reward Calculation for Critical Level Reports

For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 50 000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 25 000 is to be rewarded in order to incentivize security researchers against withholding a bug report.

Repeatable Attack Limitations

In cases of repeatable attacks for smart contract bugs, only the first attack will be counted, regardless of whether the smart contract is upgradable, pausable, or killable.

Restrictions on Security Researcher Eligibility

Security researchers who fall under any of the following are ineligible for a reward

• Citizens or residents of OFAC-sanctioned countries
• Individuals on an OFAC sanctions list

Proof of Concept (PoC) Requirements

A PoC is required for the following severity levels:

• Smart Contract - Critical
• Smart Contract - High
• Smart Contract - Medium
• Smart Contract - Low

All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

Reward Payment Terms

Payouts are handled by the Axiom team directly and are denominated in USD. However, payments are done in USDC.

All code for Axiom V2 can be found at: https://github.com/axiom-crypto/axiom-v2-contracts/releases/tag/v1.0.0 https://github.com/axiom-crypto/halo2-lib/releases/tag/v0.4.1 https://github.com/axiom-crypto/snark-verifier/releases/tag/v0.1.7 https://github.com/axiom-crypto/axiom-eth/releases/tag/v2.0.14

Documentation for the table assets can be found at https://docs.axiom.xyz/. The deployed assets can be found at: https://docs.axiom.xyz/docs/transparency-and-security/security.

The ZK verifiers AxiomV2CoreVerifier, AxiomV2CoreHistoricalVerifier, and AxiomV2QueryVerifier are generated via the procedure described here: https://docs.axiom.xyz/docs/transparency-and-security/on-chain-zk-verifiers

These impacts are out of scope for this bug bounty program.

All Categories

• Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
• Impacts caused by attacks requiring access to leaked keys/credentials
• Impacts caused by attacks requiring access to privileged addresses (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
• Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
• Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
• Best practice recommendations
• Feature requests
• Impacts on test files and configuration files unless stated otherwise in the bug bounty program

Smart Contracts and Blockchain/DLT

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Impacts requiring basic economic and governance attacks (e.g. 51% attack)
• Lack of liquidity impacts
• Impacts from Sybil attacks
• Impacts involving centralization risks
• Best practice recommendations

The following activities are prohibited by this bug bounty program:

• Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
• Any testing with pricing oracles or third-party smart contracts
• Attempting phishing or other social engineering attacks against our employees and/or customers
• Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
• Any denial of service attacks that are executed against project assets
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty