Tinyman
Tinyman is a decentralised exchange (DEX) on Algorand. More specifically, it is an Automated Market Maker (AMM) exchange employing the Constant Product Market Maker algorithm.
PoC required
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
No PoC is required, but all bug reports must be detailed with either step-by-step exploit instructions or pointers to specific lines of code in order to be considered for a reward. The Tinyman team may ask for further explanations for bug reports to prove validity.
Tinyman will also issue an NFT reward for valid High severity reports, and a single edition Tinyman NFT reward for valid Critical severity reports.
The following impacts are considered to be out of scope of this bug bounty program:
- Issues due to Freeze or Clawback of pooled assets
- Rounding issues when swapping/minting/burning with <1000 microunits of an asset
- Overflow errors when attempting to swap/mint/burn very large amounts
- Attacks against accounts not created from the Pool LogicSig Template
- MEV style attacks
- Pool ratio/price manipulation due to donations to the pool account
All known issues listed here are also considered as out-of-scope of the bug bounty program: https://github.com/tinymanorg/docs/tree/main/known-issues.
Payouts are handled by the Tinyman team directly and are denominated in USD. However, payouts are done in USDC or ALGO, at the discretion of the team.
Program Overview
Tinyman is a decentralised exchange (DEX) on Algorand. More specifically, it is an Automated Market Maker (AMM) exchange employing the Constant Product Market Maker algorithm.
The exchange is fully decentralized and non-custodial. Funds are held in permissionless smart contract accounts. This means the only methods to withdraw funds from the pool accounts are those encoded in the smart contract. At a high level this code only allows withdrawals in exchange for an appropriate amount of another asset or by the liquidity owners in exchange for their Pool Tokens.
Furthermore the contracts are fully permissionless. This means that any account can create a pool by issuing the correct set of transactions. It means that no account has authority over the pool's assets or functionality. This also means there is no mechanism to revert or adjust transactions even if they are made in error.
The contracts are also fully immutable. This means no account has the authority to update or delete the contracts that control the pools. This means that funds cannot be stolen by an update to the contracts.
For more information about Tinyman, please visit https://tinyman.org/.
This bug bounty program is focused on their smart contracts and is focused on preventing:
- Thefts and freezing of liquidity pools
- Unauthorized and fraudulent calls to Tinyman v1.1 smart contracts
KYC not required
No KYC information is required for payout processing.
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
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.