Rhino.fi

Back to Explore Rhino.fi Rhino.fi is the lightening fast stablecoin liquidity layer powering instant, scalable, cross-chain liquidity all through a single API. We operate our own internal solver and pre-funded liquidity network, enabling guaranteed stablecoin pricing, minimal slippage, and near-instant settlement across 35+ chains, including Ethereum, Solana, Tron, TON, BNB and specialised Appchains. Arbitrum BSC ETH Optimism Polygon Polygon zkEVM zkSync Starknet Tron Base Defi Infrastructure Bridge Crosschain Liquidity Solidity Maximum Bounty $2,000,000 Live Since 30 June 2023 Last Updated 20 July 2026 PoC Required Submit a Bug Information Scope Resources Rewards Rhino.fi provides rewards in USDC or USDT on Ethereum , denominated in USD. Rewards by Threat Level Smart Contract Critical Max: $2,000,000 Min: $20,000 Primacy of Rules High Max: $100,000 Min: $5,000 Primacy of Rules Medium Max: $10,000 Min: $2,000 Primacy of Rules Low Flat: $1,000 Primacy of Rules Critical Reward Calculation Mainnet assets: Reward amount is 10 % of the funds directly affected up to a maximum of: $2,000,000 Minimum reward to discourage security researchers from withholding a bug report: $20,000 Rewards Body Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3. 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 Smart Contract bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required. For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 2,000,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 100,000 is to be rewarded in order to incentivize security researchers against withholding a bug report. All High and Medium rewards for the project bug bounty program are scaled based on an internally established team criteria, taking into account the exploitability of the bug, the impact it causes, and the likelihood of the vulnerability presenting itself, which is especially factored in with bug reports requiring multiple conditions to be met that are currently not in-place. However, there is a minimum reward for each severity level, rewards will be provided at the determined fair value by the team depending on these conditions, assuming that the bug report is in-scope of the bug bounty program. The following vulnerabilities relating to those contracts are not eligible from this specific bounty, but can be submitted instead to https://immunefi.com/bounty/starkex/ : https://github.com/starkware-libs/starkex-contracts/tree/master/audit All vulnerabilities found in any audit documents in https://github.com/rhinofi/contracts_public Payouts are handled by the rhino.fi 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. View impacts in scope Program Overview rhino.fi is a multi-chain DeFi aggregator platform, bringing you the best DeFi opportunities in one place. The company began by pioneering the development of instant, gas-free spot trading on Ethereum layer 2 (powered by StarkEx). Now, they want to unlock the full potential of multi-chain and allow the next million users to enjoy everything DeFi has to offer, through a self-custodial UX that rivals the best centralised exchanges. For more information about rhino.fi, please visit https://rhino.fi/. KYC not required No KYC information is required for payout processing. Proof of Concept Proof of concept is always required for all severities. Prohibited Activities Default 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. Chain Rollbacks Pre-Impact Bug Monitoring Attack Investment Amount Attacks With A Financial Risk To The Attacker When Is An Impactful Attack Downgraded To Griefing? Submit a Bug Total Assets in Scope 9