Aleph Zero-logo

Aleph Zero

Aleph Zero is an enterprise-ready, high-performance blockchain platform with a novel, Directed Acyclic Graph (DAG)-based consensus protocol that has been peer-reviewed and presented at an ACM conference. To date, Aleph Zero raised $15m for continued development, integrated with the Parity’s Substrate stack, and expanded the team to ~50 people.

Polkadot
Blockchain
Infrastructure
Bridge
L1
Zero-Knowledge Proofs
Rust
Maximum Bounty
$50,000
Live Since
16 August 2023
Last Updated
18 November 2024
  • PoC required

Select the category you'd like to explore

Assets in Scope

Target
Primacy Of Impact
Type
Blockchain/DLT
Added on
5 October 2023
Target
Type
Blockchain/DLT - Aleph Node
Added on
16 August 2023
Target
Type
Blockchain/DLT - AlephBFT
Added on
16 August 2023

Impacts in Scope

Severity
Critical
Title

Network not being able to confirm new transactions (total network shutdown)

Severity
Critical
Title

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

Severity
Critical
Title

Arbitrary signature forging

Severity
Critical
Title

Permanent finalization stall

Severity
High
Title

Prolonged chain splits and/or long, finalization stalls

Severity
High
Title

RPC API crash affecting projects with greater than or equal to 25% of the market capitalization on top of the respective layer

Severity
Medium
Title

High compute consumption by validator nodes

Severity
Low
Title

Underpricing transaction fees relative to computation time

Out of scope

Default Out of Scope and rules

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