Tinyman AMM v2.0 Protocol

Tinyman is a decentralized trading protocol which utilizes the fast and secure framework of the Algorand blockchain, creating an open and safe marketplace for traders, liquidity providers, and developers.

For more information about Tinyman, please visit https://tinyman.org/.

This bounty program will expire on 30.06.2024

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.

All bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

Tinyman requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The basic information needed is full name, residential details, and passport details (DOB, issuing country and passport number). Based on the basic information submitted, Tinyman team may request further information at its sole discretion for compliance with applicable Laws.

Additionally, all bug bounty hunters seeking a reward need to submit certification that (i) they are not acting, directly or indirectly, for or on behalf of any person, group entity, or nation named by any Executive Order or the United States Treasury Department as a terrorist, “Specially Designated National and Blocked Person,” or other banned or blocked person, entity, nation, or transaction pursuant to any law, order, rule or regulation that is enforced or administered by the Office of Foreign Assets Control; and (ii) they are not engaging in, instigating or facilitating this transaction, directly or indirectly, on behalf of any such person, group, entity, or nation. They also need to submit an attestation that all information provided is true, correct, up-to-date and not misleading.

Known issues highlighted in the following audit reports are considered out of scope of the program:

• https://github.com/runtimeverification/publications/blob/main/reports/smart-contracts/Tinyman-amm-v2-audit/tinyman-amm-v2-audit-report.pdf

The Algorand Foundation has agreed to match 100% of any financial reward offered by Tinyman for any validated Critical or High impact vulnerability payout. The matching payout is already included in the reward amounts displayed on the program.

In effect, if a white hat finds a critical vulnerability and it is validated, they will be eligible to receive USD 100,000 from Tinyman as well as USD 100,000 from the Algorand Foundation for a total of USD 200 000. High severity vulnerabilities will be rewarded with USD 25,000 from Tinyman and USD 25,000 from the Algorand Foundation, for a total of USD 50 000.

On top of the matching, Algorand Foundation also pledged a bonus reward for the high and critical findings during the first 30 days. This would bring the total reward for a Critical vulnerability to USD 250 000 if it is found and reported within the first 30 days of this program launch. Due to the time-bound nature of this extra reward, it has been excluded from the reward numbers shown above.

Critical and High severity payouts are handled by the both Tinyman team and the Algorand Foundation. Medium and Low severity payouts are handled by the Tinyman team directly. Payouts are denominated in USD, but are done in USDCa.

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)

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