Money on Chain
Money On Chain brings Bitcoin to mass adoption. To that end, it offers solutions to meet the needs of different types of users: a fully Bitcoin-collateralized stablecoin (DoC), a Bitcoin on steroids conceived for the long term bitcoin holder (BPro), and a dizzying bitcoiner option for lovers of leveraged trading (BTCx). All this, without requiring the delivery of private keys.
PoC required
KYC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$10,000Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. 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.
The final payout amount may be affected by the exploitability of the vulnerability. Payouts are handled by Money on Chain directly and are denominated in USD. However, payouts are done in DOC (Bitcoin-collateralized stablecoin).
Program Overview
Money On Chain brings Bitcoin to mass adoption. To that end, it offers solutions to meet the needs of different types of users: a fully Bitcoin-collateralized stablecoin (DoC), a Bitcoin on steroids conceived for the long term bitcoin holder (BPro), and a dizzying bitcoiner option for lovers of leveraged trading (BTCx). All this, without requiring the delivery of private keys. To make this possible, we developed a unique mathematical-financial model with proven robustness, even in extreme market situations. Money On Chain - Bringing Bitcoin into the mainstream.
Money on Chain is interested in securing its smart contracts, oracle, and price feeder app and is primarily interested in preventing the loss of user funds.
KYC required
The submission of KYC information is a requirement for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Prohibited Activities
-
- Disassembly or reverse engineering of binaries for which source code is not published, not including smart contract bytecode
- 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.