All smart contracts of Kadena can be found at https://github.com/kadena-io. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Kadena’s API specification can be found at [https://api.chainweb.com/openapi/](https://api.chainweb.com/openapi/) However attacking a node via its Service API is out-of-scope of the bug bounty program

Kadena was founded on the idea that blockchain could revolutionize how the world interacts and transacts. But to get to mass adoption, chain technology and the ecosystem connecting it to the business world needed to be reimagined from the ground up.

Remotely manipulating the content of the chain database (rocksdb) of a node

Remotely manipulating the content of the Pact (sqlite) database of a node such that it is not consistent with block validation results

Transaction consuming very little gas compared to node resources

Permanently disabling all or most nodes in the network, requiring node software update

Stopping block production across the network for a prolonged period, requiring node software update

Transaction censorship for a prolonged period, without block stuffing, requiring node software update

Theft, permanent freezing, or counterfeiting of unclaimed yield

Theft, freezing, or counterfeiting of any amount of funds

Temporary freezing of funds

Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.

Taking down the application

Subdomain takeover without already-connected wallet interaction

Leak of Kadena-held keys and/or credentials that allow access to private systems

Transient consensus failures

Denial of service for individual nodes via resource leak or improperly bounded query parameter

Transaction consuming little gas compared to node resources

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Unbounded gas consumption

Changing non-sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as changing the name of user, or enabling/disabling notifications

Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site data

Redirecting users to malicious websites (open redirect)

Unintended permanent chain split requiring hard fork (network partition requiring hard fork)

Permanent and total network shutdown or corruption, requiring significant rollback of history Arbitrary remote code execution

Arbitrary signature forging

Arbitrary remote code execution

Permanent loss, freezing, or counterfeiting of a considerable amount of funds

Theft, permanent freezing, or counterfeiting of any considerable amount of funds, whether at-rest or in-motion, other than unclaimed yield

Insolvency

Execute arbitrary system commands

Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys(this does not include non-sensitive environment variables, open source code, or usernames)

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, commenting, voting, making trades, withdrawals, etc.

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions

Redirected funds by address modification

Leak of unencrypted Kadena-held private keys controlling mainnet funds

Kadena Smart Contract

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2). This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All web/app bug reports must come with a PoC (Proof of Concept document) with an end result that impacts an asset-in-scope in order to be considered for a reward. All Medium, High and Critical Smart Contract bug reports require a PoC to be eligible for a reward. A valid PoC is demonstrated privately, for example using a private devnet, and must clearly communicate the nature of the flaw, how it was discovered, and how to exercise the flaw within that private environment. It must be sufficiently well documented to allow reproduction of the findings by a third party. Explanations and statements alone are not accepted as PoC: code is required. Any bug report that has already been run on a public facing network such as mainnet or testnet will not be eligible for payout.

The following vulnerabilities are not eligible for a reward:

  - Congestion and scalability vulnerabilities
  - Vulnerabilities requiring the use of the private service API of the node being attacked
  - Distributed denial of service (DDoS) attacks

Payouts are handled by the __Kadena team__ directly and are denominated in USD. However, payouts are done in __KDA and stablecoins__, with the choice of the ratio at the discretion of the team. In addition, as part of claiming a bug bounty, whitehats must complete a KYC process from SumSub and submit relevant tax documents requested by the Kadena team.

Kadena

Codebase