Autonolas
Autonolas enables DAOs to create, run and own autonomous services that power next-gen apps in DAO operations, treasury management, AI, and beyond. Autonolas protocol provides means to build, register, co-own, 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.
PoC required
KYC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$50,000Rewards 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 and high 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 6 000 for high smart contract vulnerabilities and 12 000 for critical ones.
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 mentioned in https://github.com/valory-xyz/autonolas-governance/tree/main/audits
- All vulnerabilities mentioned in https://github.com/valory-xyz/autonolas-governance/tree/main/docs
- All vulnerabilities mentioned in https://github.com/valory-xyz/autonolas-governance/tree/main/test
- All vulnerabilities mentioned in the comments on the contracts code https://github.com/valory-xyz/autonolas-governance/tree/main/contracts
- All vulnerabilities mentioned in https://github.com/valory-xyz/autonolas-registries/tree/main/audits
- All vulnerabilities mentioned in https://github.com/valory-xyz/autonolas-registries/tree/main/docs
- All vulnerabilities mentioned in https://github.com/valory-xyz/autonolas-registries/tree/main/test
- All vulnerabilities mentioned in the comments on the contracts code https://github.com/valory-xyz/autonolas-registries/tree/main/contracts
- All vulnerabilities mentioned in https://github.com/valory-xyz/autonolas-tokenomics/tree/main/audits
- All vulnerabilities mentioned in https://github.com/valory-xyz/autonolas-tokenomics/tree/main/docs
- All vulnerabilities mentioned in https://github.com/valory-xyz/autonolas-tokenomics/tree/main/test
- All vulnerabilities mentioned in the comments on the contracts code https://github.com/valory-xyz/autonolas-tokenomics/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 inherited source code for the bridging contracts from Polygon, Gnosis, Arbitrum, Optimism, Base, Wormhole docs.
- All vulnerabilities found in code based on or inspired by Maple Finance (https://github.com/maple-labs) Curve DAO https://github.com/curvefi/curve-dao-contracts Uniswap Labs (https://github.com/Uniswap/v2-core), PaulRBerg (https://github.com/paulrberg/prb-math), Jeiwan (https://github.com/Jeiwan/zuniswapv2), Safe Ecosystem (https://github.com/safe-global/safe-contracts) and that are already reported to one of those projects.
- All vulnerabilities that arise from misconfigured registration from users (e.g. component owners, agent owners, service owners, agents operators) or misuse of the registration logic (e.g. accidental locking of funds, loss of keys to control services, etc.).
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.
Program Overview
Autonolas enables DAOs to create, run and own autonomous services that power next-gen apps in DAO operations, treasury management, AI, and beyond. Autonolas protocol provides means to build, register, co-own, 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://olas.network.
KYC required
The submission of KYC information is a requirement for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Prohibited Activities
- 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
- Any other actions prohibited by the Immunefi Rules