CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
RWANFTFI logo
RWANFTFI
RWA
Max Payout
$1,000
Project Overview

RWANFTFI is a Web3 protocol on Binance Smart Chain that bridges NFTs, Real World Assets (RWA), DeFi, and CeFi. The protocol uses the Diamond Pattern (EIP-2535) with 7 Facets, a 21M hard-capped USDT-backed Deflationary Asset (DA) token, a 22-level marketing structure, and lending against DA collateral. Smart contracts were independently audited by CertiK (final report: April 28, 2026). This bug bounty program is launched to complement the audit and incentivize the security community to identify any remaining vulnerabilities in our deployed smart contracts. We are particularly interested in findings related to fund safety, access control, accounting integrity (Income Limit, Accumulative Balance, Frozen Balance), DA price formula edge cases, and Diamond Facet upgrade paths. All in-scope contracts are deployed on BSC and verifiable on BscScan. Reports must include a clear PoC and impact assessment. We commit to responding within 72 hours.

Rewards by Severity
Smart Contract
The bounty will be paid out in USD
Assets In-Scope
https://github.com/RWANFTFI/rwa-contracts
Smart Contract
Smart Contracts
In-Scope Vulnerabilities
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in-scope, even if they affect something in the assets in scope table.
Smart Contract
Critical
Direct theft of project funds
other than unclaimed rewards.
Direct theft of user funds
other than unclaimed rewards.
Permanent freezing of funds.
Unauthorized mint/burn/transfer of crypto assets
Governance voting result manipulation.
Protocol insolvency
Major
Issues leading to temporary freezing of funds for a limited amount of time.
Theft or permanent freezing of unclaimed yield and rewards.
Temporary denial of services.
Broken access control leads to high security risks
Medium
Unexpected logic executions (doesn’t lose value)
Smart contract unable to operate due to lack of funds or misconfiguration.
Griefing attacks that can damage users or the protocol without profiting the attacker
Inconsistencies between on-chain state and ViewFacet read functions; rounding errors in fee/split calculations (75/20/5
70/30 redistribution) that drift over time; DAO parameter changes that bypass on-chain min/max range guards; spam vector against tree placement algorithm (weakest-branch
left-to-right); incorrect compression flow when upline Income Limit reaches zero mid-transaction
Low
Important gas optimizations
Smart contract functionality significantly differs from how it is described in its official documentation.
Smart contract fails to deliver promised returns - but doesn’t lose value
Missing events for functions that change critical parameters
Out-Of-Scope Vulnerabilities
The following vulnerabilities are excluded from the rewards for this bug bounty program:
  • Vulnerabilities that have already been exploited
  • Centralization-related vulnerabilities related to: private keys, privileged addresses, governance, credentials, etc.
Smart Contract
Incorrect data supplied by third party oracles (Not to exclude oracle manipulation/flash loan attacks)
Not following best practices
with no security risk.
Sybil attacks
Centralization risks
Issues with no security or financial impact.
Frontend / UI / mobile application bugs (out of audit scope
app-layer concern); issues in TAN code system (off-chain authentication layer); Telegram bot vulnerabilities; cross-chain deposit service bugs (managed by SERVICE_ROLE off-chain infrastructure); BSC network-level issues (BNB gas
RPC reliability
BscScan indexing); third-party wallet vulnerabilities (MetaMask
Trust Wallet); social engineering / phishing; issues only reproducible on testnet; legal / compliance / KYC / AML concerns; intentional protocol parameter values within DAO-adjustable ranges (per-level tree distribution
Sponsor Bonus
fee parameters)
Program Rules
  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue - the issue will not be eligible for a reward., Submit one vulnerability per report - unless you need to chain vulnerabilities to provide impact., When duplicates occur we only award the first report that was received (provided that it can be fully reproduced)., Multiple vulnerabilities caused by one underlying issue will be awarded one bounty., Make a good faith effort to avoid privacy violations - destruction of data - and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder., Do not attempt to conduct post-exploitation including modification or destruction of data - and interruption or degradation of services., Do not attempt to perform brute-force attacks or denial-of-service attacks., Do not attempt to target employees or customers including social engineering attacks - phishing attacks or physical attacks.
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., Automated testing of services that generate significant amounts of traffic., Public disclosure of an unpatched vulnerability in an embargoed bounty., Social engineering (e.g. phishing
  • vishing
  • smishing) of any kind.
FAQs
How do I search for active bounties?
A: Active bounties can be viewed here [CertiK URL], and by filtering for bounties on the Security Leaderboard. Projects will post bounties along with the assets in the scope of the bounties with a corresponding bounty reward.
How do I submit a bounty?
To submit a bug report, first register an account with us https://www.certik.com/auth/signup. Once your account is created, you can log in and select “Submit Bug” for the specific bounties you're interested in. You will be prompted to fill out a webform; follow the instructions and upon successful submission, you will receive an email confirmation with a reference ID.
Who do I contact if I'm having trouble with my bug report submission?
You can reach out to bugbounty@certik.com for updates and assistance with your bug bounty submission.
I submitted my bug report. What now?
Once your bug report is submitted, CertiK will evaluate the report and contact the respective project. Depending on the criteria stated within a bug bounty, a KYC may be required. With valid bug reports, you will be contacted to begin the process of evaluating the bug with the project.
How is KYC handled?
CertiK has a team of investigative professionals that will handle any needed KYC services for bug bounty submissions requiring KYC.
Why was my bug report submission rejected?
A description of dismissal will be available for any bug bounty that is rejected.
The project is being slow responding to my bug report. What are their required response times / SLAs?
There can be multiple bug bounty submissions therefore there might be some delay in process times.
How do payouts work?
Payments for successful bug bounties will be communicated directly via the project wherein wallet information can be exchanged.
Bounty Highlights
Assets in Scope1
Live SinceMay 10, 2026
Last Updated3d ago
Funds Reserved$2,000
Max Payout$1,000
Skynet Score
68.94
BB
KYC
Not Required
PoC
Required
View on Skynet