Ceres
Ceres is one of the first projects on SORA (XOR) blockchain. Ceres is developing DeFi services and utilities for new projects and tokens on Polkaswap (Cross-chain exchange on SORA/Polkadot).
PoC required
Rewards
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate classifications for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
All bug reports must come with a Proof of Concept (PoC) with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.
Payouts are handled by the SORA team directly and are denominated in USD. However, payouts are done in TBCD, at the discretion of the team.
Program Overview
Ceres is one of the first projects on SORA (XOR) blockchain. Ceres is developing DeFi services and utilities for new projects and tokens on Polkaswap (Cross-chain exchange on SORA/Polkadot).
Ceres ecosystem consists of four concepts:
- Burning - Ceres tokens will be burned over time and supply will be constantly reducing.
- Governance - Ceres token holders can influence decisions concerning the project such as proposing or deciding on new feature proposals.
- Airdrops - Every Ceres holder can get each of three Ceres Airdrop tokens which will have its own platforms with different purposes.
- Treasury - Community will be making proposals for the use and Ceres holders will have the right to vote for them.
There are also 3 Airdrop tokens for Ceres holders: Demeter, Hermes and Apollo. Each of the tokens will have its own platform with different purposes. Fees from those platforms will be used for burning and other ecosystem uses.
These are the current products so far:
- Ceres Tools (like Dextools but for Polkaswap) - https://tools.cerestoken.io
- Liquidity Locker - https://dapps.cerestoken.io/liquidity_locker
- Token Locker - https://dapps.cerestoken.io/token_locker
- Ceres Governance - https://dapps.cerestoken.io/governance
- Demeter Farming Platform - https://farming.deotoken.io
- DEO Arena - https://deoarena.io (first Play-to-Earn game on SORA)
- Ceres Launchpad - https://dapps.cerestoken.io/launchpad
For more information about Ceres, please visit https://cerestoken.io
KYC not required
No KYC information is required 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.