NFTfi (Testnet Refi)
Bounty Range
$20,000 - $20,000
external program
NFTfi (Testnet Refi)
Bounty Range
$20,000 - $20,000
external program
NFTfi is the leading liquidity protocol for NFTs. NFTfi allows NFT owners to use the assets (NFTs) they own to access the liquidity they need by receiving secured loans from liquidity providers, peer-to-peer, in a completely trustless manner.
For more information about NFTfi, please visit https://www.nftfi.com/
NFTfi (Testnet Refi) provides rewards in USDC on Solana, denominated in USD.
Smart Contract - Critical Flat: $20,000
Reward amount is 10% of the funds directly affected up to a maximum of $20,000
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Reward Calculation for Critical Level Reports
For critical smart contract bugs on testnet assets, the reward is paid as a flat amount of USD 20,000. This is because there are no actual funds at risk on the testnet, hence limits objective calculation.
Repeatable Attack Limitations
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact.
Reward Payment Terms
Payouts are handled by the NFTfi team directly and are denominated in USD. However, payments are done in USDC.
The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.
NFTfi is the leading liquidity protocol for NFTs. NFTfi allows NFT owners to use the assets (NFTs) they own to access the liquidity they need by receiving secured loans from liquidity providers, peer-to-peer, in a completely trustless manner.
Refinancing is a feature that allows the borrower with an existing loan to refinance to a loan with better terms, using the same collateral.
It works by allowing the borrower with an existing loan to accept any other valid offer on the same collateral. The new offer is typically with a new lender, but could also be with the original lender.
Refinancing between different types of loans
The contracts implementing the feature are one layer above the loan contracts and facilitates refinancing of loans between any of the loan contracts. You can refinance:
Refinancing mechanism
Limitations
Refinancing is only possible if the original and new loan have the same loan denomination.
If the currency of the source loan is not supported by DyDx (e.g. wstETH), we do a 2-way swap on uniswap at the beginning and the end of the process by swapping to WETH.
NFTfi adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page.
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
Proof of concept is always required for all severities.
NFTfi's completed audit reports can be found at:
Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
By adhering to Immunefi's best practice recommendations, NFTfi has satisfied the requirements for the Immunefi Standard Badge.
KYC is not required.
Category 3: Approval Required
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.