Circuit is a DeFi protocol built on the Chia blockchain.
Specifically, Circuit is a collateralized debt position (CDP) protocol that allows users to borrow Bytecash (BYC), a USD stablecoin issued by the protocol, against XCH, the native token of Chia.
For more information about CircuiDAo, please visit https://docs.circuitdao.com/.
Circuit rewards are denominated in USD and distributed in USDC on Ethereum
Status
This Audit Competition Is Over
Invite-Only-Program cards for security researchers with paid reports are available here. The amounts show $2K in guaranteed rewards per SR and a $6K reward pool distributed according to the Standardized Competition Reward Terms.
All paid bug reports are available in original format here.
Immunefi vault program
Rewards
Rewards by Threat Level
Rewards are distributed among SRs according to Immunefi’s Standardized Competition Reward Terms.
Total budget: $10,000 broken down as follows:
Reward pool:
If bugs are found → USD $6k (see Immunefi’s Standardized Competition Reward Terms)
If only Insights are found → USD $900 (9% of the Reward pool)
Guaranteed rewards: $2k per SR → $4k total (for 2 SRs)
Duplicate submissions of bugs are valid. Duplicate submissions of Insights are invalid.
Proof of Concept (PoC) Requirements
For this program, runnable PoC code is not required. Whitehats are instead required to write a step-by-step explanation of the PoC and impact. Read our New Audit Competition Proof-of-Concept Rules
Insight reports can be submitted. Read our Insight validity rules
Program Overview
Circuit is a DeFi protocol built on the Chia blockchain.
Specifically, Circuit is a collateralized debt position (CDP) protocol that allows users to borrow Bytecash (BYC), a USD stablecoin issued by the protocol, against XCH, the native token of Chia.
For more information about CircuiDAo, please visit https://docs.circuitdao.com/.
Circuit rewards are denominated in USD and distributed in USDC on Ethereum
Audits
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
- 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.