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.
PoC Required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
All Smart Contract impacts are only related to the Autonomous Agent assets.
Unintended permanent chain split requiring hard fork (network partition requiring hard fork)
Direct loss of funds
Permanent freezing of funds (fix requires hardfork)
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
Execute arbitrary system commands
Direct theft of user funds
Network permanently unable to confirm new transactions (total network shutdown)
Retrieve sensitive data/files from a running server, such as: - database passwords usable from the open internet , - wallet private keys (this does not include non-sensitive environment variables, open source code, or usernames)
Taking state-modifying authenticated actions that lead to loss of funds on behalf of other users without any interaction by that user.
Temporary freezing of network transactions by delaying adequate processing for at least 1 day. Requires network coordination to resolve
Out of scope
Out of Scope
- For all impacts directly involving funds being lost or frozen, the minimum impact is USD 1000. Anything below is considered out-of-scope.
-For Blockchain/DLT bug reports, temporary disruptions of network availability, such as node crashes and DoS, are out of scope when they can be resolved by deploying a fix without network coordination. Temporary disruptions that require network coordination to resolve are in scope and are assessed under the 'Temporary freezing of network transactions' impacts in the Impacts in Scope table
-
The web/app impacts of “Stealing User Cookies” and “Bypassing Authentication” are only accepted if they result in a loss of at least USD 1 000. The web/app impact of “Ability to execute system commands” is only accepted if the actions are done as root.
-
Impacts with direct financial damage whereby the total is less than or equal to 200% of the total expense used by the attacker
Blockchain/DLT specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers