Decentralized Security, Community-Powered Recon

Bounty Overview Rewards by Severity Assets in Scope In-scope Vulnerabilities Out-of-scope Vulnerabilities Program Rules FAQs

Xode Blockchain

Smart Contract Platform

Infrastructure

Max Payout

1000 XON

Project Overview

Welcome to the official XODE Bug Bounty Program. We are committed to building a secure and transparent decentralized ecosystem. To strengthen the reliability of our protocol, wallet infrastructure, and smart contracts, we invite ethical hackers, security researchers, and the wider developer community to identify vulnerabilities in our systems.

This program is designed to reward responsible disclosures that help us maintain the highest standards of security. Whether you’re an experienced white-hat or a curious developer, your contribution is highly valued and directly supports the long-term success of the XODE ecosystem.

Rewards by Severity

Blockchain

The bounty will be paid out in XON

Assets In-Scope

Target

Severity

Name

https://github.com/Xode-DAO/xode-blockchain

Blockchain

XON native token

In-Scope Vulnerabilities

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

Blockchain

Critical

Unintended permanent chain split requiring hard fork

Major

Unintended chain split (fix not requiring hard fork)

Validator selection set manipulation

Medium

High compute consumption by validator/mining nodes

Vulnerability in RPC API (except via DDoS attack)

Attacks against thin clients

Out-Of-Scope Vulnerabilities

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

Vulnerabilities that have already been exploited
Centralization-related vulnerabilities related to: private keys, privileged addresses, governance, credentials, etc.

Blockchain

Centralization risks

Program Rules

Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue - the issue will not be eligible for a reward., Submit one vulnerability per report - unless you need to chain vulnerabilities to provide impact., When duplicates occur we only award the first report that was received (provided that it can be fully reproduced)., Multiple vulnerabilities caused by one underlying issue will be awarded one bounty., Do not attempt to conduct post-exploitation including modification or destruction of data - and interruption or degradation of services., Do not attempt to perform brute-force attacks or denial-of-service attacks., Do not attempt to target employees or customers including social engineering attacks - phishing attacks or physical attacks.

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. Automated testing of services that generate significant amounts of traffic. Public disclosure of an unpatched vulnerability in an embargoed bounty. Social engineering (e.g. phishing, vishing, smishing) of any kind.

FAQs

How do I search for active bounties?

A: Active bounties can be viewed here [CertiK URL], and by filtering for bounties on the Security Leaderboard. Projects will post bounties along with the assets in the scope of the bounties with a corresponding bounty reward.

How do I submit a bounty?

To submit a bug report, first register an account with us https://www.certik.com/auth/signup. Once your account is created, you can log in and select “Submit Bug” for the specific bounties you're interested in. You will be prompted to fill out a webform; follow the instructions and upon successful submission, you will receive an email confirmation with a reference ID.

Who do I contact if I'm having trouble with my bug report submission?

You can reach out to bugbounty@certik.com for updates and assistance with your bug bounty submission.

I submitted my bug report. What now?

Once your bug report is submitted, CertiK will evaluate the report and contact the respective project. Depending on the criteria stated within a bug bounty, a KYC may be required. With valid bug reports, you will be contacted to begin the process of evaluating the bug with the project.

How is KYC handled?

CertiK has a team of investigative professionals that will handle any needed KYC services for bug bounty submissions requiring KYC.

Why was my bug report submission rejected?

A description of dismissal will be available for any bug bounty that is rejected.

The project is being slow responding to my bug report. What are their required response times / SLAs?

There can be multiple bug bounty submissions therefore there might be some delay in process times.

How do payouts work?

Payments for successful bug bounties will be communicated directly via the project wherein wallet information can be exchanged.

Bounty Highlights

Assets in Scope1

Live SinceAug 18, 2025

Last Updated25d ago

Funds Reserved1000 XON

Max Payout1000 XON

Skynet Score

86.65

KYC

Required

PoC

Not Required

View on Skynet