Obyte

Back to Explore Obyte | Obyte is a distributed ledger based on directed acyclic graph (DAG) and is without middlemen. Unlike centralized ledgers and blockchains, access to the Obyte ledger is decentralized, disintermediated, free (as in freedom), equal, and open. Obyte Blockchain L1 Wallet JavaScript Maximum Bounty $50,000 Live Since 01 December 2020 Last Updated 21 July 2026 PoC Required Submit a Bug Information Scope Resources Rewards Obyte provides rewards in GBYTE, BTC, USDT on BSC , denominated in USD. Rewards by Threat Level Blockchain/DLT Critical Max: $50,000 Min: $2,500 Primacy of Rules High Flat: $1,700 Primacy of Rules Medium Flat: $1,000 Primacy of Rules Critical Reward Calculation Reward amount is 10 % of the funds directly affected, capped at the maximum critical reward of: $50,000 Minimum reward to discourage security researchers from withholding a bug report: $2,500 The reward is dependent on the ratio between the funds at risk, which includes all affected projects on top of the respective blockchain/DLT, and the market cap according to the average between CoinMarketCap.com and CoinGecko.com, calculated at the time the bug report is submitted. Smart Contract Critical Flat: $2,500 Primacy of Rules High Flat: $1,700 Primacy of Rules Medium Flat: $1,000 Primacy of Rules Critical Reward Calculation Mainnet assets: Reward amount is 10 % of the funds directly affected up to a maximum of: $2,500 Websites and Applications Critical Flat: $2,500 Primacy of Rules High Flat: $1,700 Primacy of Rules Medium Flat: $1,000 Primacy of Rules Rewards Body Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below. Repeatable Attack Limitations Given that the reward for High is flat, there is no distinction between a one-time attack and an attack that is repeated and the reward stays the same. Restrictions on Security Researcher Eligibility Security researchers who fall under any of the following are ineligible for a reward: Compensated team members of the Obyte Foundation Employees and team members of third-party suppliers to an Obyte Foundation affiliate that operate in a technical capacity and have assets covered in this bug bounty program Reward Calculation for Critical Level Reports For Blockchain/DLT bug reports, in order to qualify for the reward of USD 50 000, the bug reported must be able to cause unrecoverable total network shutdown of the entire Obyte network or allow the unpermitted execution of transactions from accounts of other users without their private keys . All other critical bug reports are capped at a flat rate of USD 2 500. For Critical Smart Contract and Web/App reports, the reward amount is 10% of the funds directly affected up to a maximum of USD 2 500. Poc Requirements All web and app bug reports must come with a PoC. All bug reports submitted without PoC will be rejected with instructions to provide PoC. Payouts are handled by the Obyte Foundation directly and are denominated in USD. The payout can be completed in GBYTE, BTC, or USDT. View impacts in scope Program Overview Obyte is a distributed ledger based on directed acyclic graph (DAG) and is without middlemen. Unlike centralized ledgers and blockchains, access to the Obyte ledger is decentralized, disintermediated, free (as in freedom), equal, and open. The Obyte Foundation is interested in securing their network, their core library, their GUI wallet, and some of their autonomous agents (smart contracts that operate completely independently). Primary areas of concern are around loss of user funds, DoS(not DDoS), and total network shutdown. Primacy of Impact vs Primacy of Rules Obyte adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms stated in this page. KYC not required No KYC information is required for payout processing. Proof of Concept Proof of concept is always required for all severities. Responsible Publication Category 3: Approval Required Prohibited Activities Default 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. Chain Rollbacks Pre-Impact Bug Monitoring Attack Investment Amount Attacks With A Financial Risk To The Attacker When Is An Impactful Attack Downgraded To Griefing? Submit a Bug Total paid 90.8k from 333 paid reports Med. Resolution Time 14 hours Total Assets in Scope 11