09 August 2022
Live since
KYC required
Maximum bounty
08 April 2024
Last updated

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:

For more information about Ceres, please visit https://cerestoken.io

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.


USD $30,000
PoC Required

Assets in scope

All smart contracts of Ceres can be found at https://github.com/sora-xor/sora2-network. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If an impact can be caused to any other asset managed by Ceres that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.

Impacts in scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.


  • Direct loss of funds
  • Permanent freezing of funds (fix requires hardfork)

Out of Scope & Rules

The following vulnerabilities are excluded from the rewards for this bug bounty program:

  • Attacks that the reporter has already exploited themselves, leading to damage
  • Attacks requiring access to leaked keys/credentials
  • Attacks requiring access to privileged addresses (governance, strategist)

Smart Contracts and Blockchain

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Basic economic governance attacks (e.g. 51% attack)
  • Lack of liquidity
  • Best practice critiques
  • Sybil attacks
  • Centralization risks

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
  • 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
  • Automated testing of services that generate significant amounts of traffic
  • Public disclosure of an unpatched vulnerability in an embargoed bounty