![BankX-logo](/_next/image/?url=https%3A%2F%2Fimages.ctfassets.net%2Ft3wqy70tc3bv%2F1AVW8dU4G3wnbqcGMuaLP3%2Fe04b779c5701717a28f468f5eea4270d%2FBankX_logo.png&w=128&q=75)
BankX
BankX Is A Dual-Token System Stablecoin: Stablecoin - BankX Silver Dollar (XSD). The BankX token – Utility token used as partial collateral to mint the stablecoin and stake in the Certificate of Deposit.
BSC
ETH
Defi
Stablecoin
Staking
Solidity
Maximum Bounty
$10,000Live Since
02 January 2024Last Updated
08 April 2024PoC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
The scope is focused solely on any exploit that results in loss in either of the liquidity pools or the collateral pool. Contracts are on the BSC chain only.
Critical
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Critical
Permanent freezing of funds
Critical
Any exploit that results in loss of in either of the liquidity pools or the collateral pool.
Critical
Protocol insolvency
Critical
Any exploit that results in system or user loss of funds or unauthorized control of the system can be found.
Out of scope
Program's Out of Scope information
These impacts are out of scope for this bug bounty program.
All Categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
- Impacts caused by attacks on the NFT
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
Smart Contracts
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
- Best practice recommendations
The following activities are prohibited by this bug bounty program:
- 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