Autonolas

Autonolas enables DAOs to create, run and own autonomous services that power next-gen apps in DAO operations, treasury management and beyond. Autonolas protocol provides means to build, register, manage and secure autonomous services: off-chain services which run as a multi-agent-system (MAS) and are replicated on a temporary consensus gadget (blockchain) while being crypto-economically secured on a public blockchain, hence offering robustness, transparency and decentralization off-chain.

For more information about Autonolas, please visit https://www.autonolas.network/.

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 25 000.

All Critical, High, and Medium Smart Contract bug reports must come with a PoC, have an end-effect impact, and an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

The following vulnerabilities are not eligible for a reward:

• All vulnerabilities found in https://github.com/valory-xyz/autonolas-governance/tree/main/audits
• All vulnerabilities found in https://github.com/valory-xyz/autonolas-governance/tree/main/docs
• All vulnerabilities found in https://github.com/valory-xyz/autonolas-governance/tree/main/test
• All vulnerabilities found in the comments on the contracts code https://github.com/valory-xyz/autonolas-governance/tree/main/contracts
• All vulnerabilities found in the inherited source code from OpenZeppelin (https://github.com/OpenZeppelin/openzeppelin-contracts) and Solmate (https://github.com/transmissions11/solmate)
• All vulnerabilities found in the contracts that are found in code based on or inspired by Maple Finance (https://github.com/maple-labs) and Curve DAO (https://github.com/curvefi/curve-dao-contracts) and are already reported to one of those projects.

Autonolas requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is an invoice with Name, Address, and Country of the hacker or a legal entity used for transactions. If the hacker is based in Switzerland they need to account for VAT in the invoice. The collection of this information will be done by the Autonolas team.

Payouts are handled by the Autonolas team directly and are denominated in USD. However, payouts are done in USDT and USDC, with the choice of the ratio at the discretion of the team.

Smart Contract

All smart contracts of Autonolas can be found at https://github.com/valory-xyz/autonolas-governance/tree/v1.0.0. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist, community multisig)
• Attacks building on already identified attacks

Smart Contracts and Blockchain

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks
• Centralization risks

The following activities are prohibited by this bug bounty program:

• Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
• 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
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty