Tropykus-logo

Tropykus

Tropykus is a decentralized lending protocol on top of Bitcoin (i.e. second layer compatible with the Ethereum Virtual Machine EVM: RSK) inspired by Compound and Aave protocols. These lending protocols provide a decentralized marketplace for suppliers and borrowers holding crypto assets.

RSK
Defi
Lending
JavaScript
Solidity
Maximum Bounty
$50,000
Live Since
16 February 2022
Last Updated
28 March 2023
  • PoC required

Submit a Bug

Rewards by Threat Level

Smart Contract
Critical
USD $50,000
High
USD $3,000
Medium
USD $2,000
Low
USD $1,000

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 and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All Critical/High/Medium smart contract 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. All bug reports must also come with a suggestion for a fix to be considered for a reward.

Payouts are handled by the Tropykus team directly and are denominated in USD. However, payouts are done in USD, USDC, XUSD, BTC, RBTC or DOC, at the discretion of the team.

Program Overview

Tropykus is a decentralized lending protocol on top of Bitcoin (i.e. second layer compatible with the Ethereum Virtual Machine EVM: RSK) inspired by Compound and Aave protocols. These lending protocols provide a decentralized marketplace for suppliers and borrowers holding crypto assets.

Tropykus provides alternative deposit and lending smart contracts for users with different interests in terms of return expectations and investment horizons, with similar risk management features of other lending protocols (e.g. collateralization, liquidation incentives). It also provides markets and accepts as collateral alternative crypto assets such as rBTC, RIF, rUSDT, DOC.

The main objective of Tropykus is to provide better financial services to everyday people in developing countries by creating a bridge between the needs of these users and the advantages of DeFi.

For more information about Tropykus, please visit https://tropykus.com/.

This bug bounty program is focused on their smart contracts and is focused on preventing:

  • Loss of user funds staked (principal) by freezing or theft
  • Theft of unclaimed yield
  • Freezing of unclaimed yield
  • Temporary freezing of funds
  • Smart contract gas drainage
  • Block stuffing without fund transfers blocked
  • Smart contract fails to deliver promised returns, but doesn’t lose value
  • Informational issues

KYC not required

No KYC information is required for payout processing.

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.