11%· poor fit · The Venture23 Aleo team's expertise in ZK, privacy, and Aleo-specific infrastructure is entirely mismatched with Celestia's Go/Rust modular blockchain protocol and general security bounty structure.
Trust
57%· model self-report 90% · first seen 2026-11-17 · v1
Verified
2026-11-17 · by extraction
Celestia Foundation runs a bug bounty program on HackenProof for vulnerabilities in its modular blockchain protocol. Security researchers can submit proof-of-concept exploits for critical, high, and medium severity issues in core repositories like celestia-core, celestia-app, and celestia-node. Rewards are paid in TIA tokens with a 25% immediate unlock and 75% locked for 12 months. Applicants must complete KYC, provide a PoC, and follow responsible disclosure rules.
Eligibility: Open to security researchers who are first reporters, provide a valid proof-of-concept on private/test networks, complete KYC and compliance screening, and are not employees or family of Celestia Labs/Foundation. Submissions must be made via HackenProof within 24 hours of discovery.
Pipeline
Funder track record · does Celestia Foundation actually pay grants?
🟡 Some payout evidence · 1 grantee found · last payout 2025-01-01 · checked 2026-11-01 · 0 forum reports, 8 web pages read, 3 unverifiable claims dropped
Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.
Grantee
Amount
Date
Evidence
Libp2p Software and Network Maintenance
—
2025-01-01
“Grant Name Libp2p Software and Network Maintenance (2 mos in 2025)”source
Trust breakdown (3/4 checkable facts verified)
Signal
Weight
Result
Note
deadline
0.35
0%
rolling claimed but not stated
amount
0.25
100%
figure appears in source
apply link
0.075
100%
link in source
funder
0.075
100%
named in source
source quality
0.15
50%
social or search hit
model confidence
0.1
90%
model self-report
Fit breakdown (against the ORG_* profile)
Signal
Weight
Result
Note
model fit
0.5
10%
model rated 10%
ecosystem overlap
0.25
0%
celestia vs aleo
category overlap
0.15
17%
security vs zk, privacy, infra, dev_tooling, security, interoperability
Celestia: Program Info | HackenProof
'%3e%3cpath%20d='M12.4997%201.33325C10.39%201.33325%208.32772%201.95884%206.5736%203.13091C4.81947%204.30298%203.4523%205.96888%202.64496%207.91796C1.83763%209.86704%201.62639%2012.0118%202.03797%2014.0809C2.44955%2016.15%203.46545%2018.0506%204.95721%2019.5424C6.44897%2021.0342%208.34959%2022.0501%2010.4187%2022.4616C12.4878%2022.8732%2014.6326%2022.662%2016.5816%2021.8546C18.5307%2021.0473%2020.1966%2019.6801%2021.3687%2017.926C22.5408%2016.1719%2023.1663%2014.1096%2023.1663%2011.9999C23.1663%209.17094%2022.0425%206.45783%2020.0422%204.45745C18.0418%202.45706%2015.3287%201.33325%2012.4997%201.33325ZM12.4997%2021.3333C10.6537%2021.3333%208.84922%2020.7859%207.31436%2019.7603C5.7795%2018.7347%204.58322%2017.2771%203.8768%2015.5716C3.17039%2013.8662%202.98555%2011.9896%203.34568%2010.1791C3.70581%208.36859%204.59473%206.70554%205.90002%205.40025C7.20531%204.09496%208.86835%203.20605%2010.6788%202.84592C12.4893%202.48579%2014.3659%202.67063%2016.0714%203.37704C17.7768%204.08346%2019.2345%205.27974%2020.2601%206.8146C21.2856%208.34945%2021.833%2010.154%2021.833%2011.9999C21.833%2014.4753%2020.8497%2016.8492%2019.0993%2018.5996C17.349%2020.3499%2014.975%2021.3333%2012.4997%2021.3333Z'%20fill='white'/%3e%3cpath%20d='M19.167%208.06667C19.042%207.9425%2018.8731%207.8728%2018.697%207.8728C18.5208%207.8728%2018.3519%207.9425%2018.227%208.06667L10.8269%2015.4333L6.82695%2011.4333C6.70495%2011.3016%206.53562%2011.2237%206.35621%2011.2169C6.1768%2011.21%206.00201%2011.2747%205.87028%2011.3967C5.73856%2011.5187%205.66069%2011.688%205.65382%2011.8674C5.64694%2012.0468%205.71162%2012.2216%205.83362%2012.3533L10.8269%2017.3333L19.167%209.01333C19.2294%208.95136%2019.279%208.87762%2019.3129%208.79638C19.3467%208.71514%2019.3642%208.62801%2019.3642%208.54C19.3642%208.45199%2019.3467%208.36485%2019.3129%208.28361C19.279%208.20237%2019.2294%208.12864%2019.167%208.06667Z'%20fill='white'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_2790_31187'%3e%3crect%20width='24'%20height='24'%20fill='white'%20transform='translate\(0.5\)'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)

Bug bounty  Triaged by HackenProof
# Celestia: Program info
## Celestia
Company: [Celestia](/companies/celestia)
Scope Review:
359926
Submissions:
283
Total rewards:
Private
Reputation
150 points required
KYC
Required
PoC
Required
Submission fee
$5
Program is: active now
Live
[Submit report](https://dashboard.hackenproof.com/user/programs/celestia/reports/new)
Program infoHackers114Reports0
Celestia is a blockchain network that introduces a modular approach to the design and functionality of blockchains. Unlike traditional blockchains that bundle consensus, data availability, and execution into a single layer, Celestia separates these functions to offer a more scalable and flexible infrastructure.
AllScopeFocus AreaProgram RulesReporting / DisclosuresEligibilityPayment of Bug Bounties
## Scope
Search targets
In scope
Target
Type
Severity
https://github.com/celestiaorg/celestia-core
Copy
Protocol
Critical
https://github.com/celestiaorg/celestia-app
Copy
Protocol
Critical
https://github.com/celestiaorg/celestia-node
Copy
Protocol
Critical
https://github.com/celestiaorg/go-header
Copy
Protocol
Critical
https://github.com/celestiaorg/rsmt2d
Copy
Protocol
Critical
https://github.com/celestiaorg/nmt
Copy
Protocol
Critical
Show all targets
### Out of scope
Out of scope
Target
Type
Severity
https://github.com/celestiaorg/celestia-node
Copy
* light node
* nodebuilder/fraud - share/ipld - share/eds/byzantine - share/eds/retriever.go - share/eds/retriever\_quadrant.go
Web
None
## Focus Area
⚠️**Only the code that directly impacts the celestia protocol in the versions referenced in the go.mod of celestia-app and celestia-node are within scope. Whether or not an issue in this repo is within scope will be determined by the Celestia Foundation in its sole discretion**.⚠️
## Vulnerability Categories
### Critical: Up to $10,000 in TIA tokens
Loss of User Funds
* Theft of funds without user signature
* Loss of staking rewards (including, but not limited, to slashing or tombstoning) without validator signature
* Excludes censoring of validator signatures by a dishonest ≥1/3 of voting power
* Excludes network attacks on the validator’s node(s)
* Excludes consensus liveness violations (i.e. chain halts)
Consensus Violations
* Consensus safety violation (i.e. chain fork) with < 1/3 dishonest voting power, within the unbonding period
* Inclusion of valid transaction(s) with the [out-of-spec](https://dashboard.hackenproof.com/redirect?url=https://celestiaorg.github.io/celestia-app/specs/state_machine_modules.html) side effect that allows minting of TIA or transferring locked, delegated, or staked TIA
* Acceptance by full nodes of a badly-encoded block
### High: Up to $1,000 in TIA tokens
Liveness
* Consensus liveness violation (i.e. chain halt) with < 1/3 dishonest voting power
Network DoS Attacks (Crash)
* Crashing an arbitrary node with a single bounded-size message each (no more than maximum block size)
* i.e. Remote resource exhaustion via non-RPC protocols such as exploiting a nil pointer dereference that can immediately halt a node without any automatic recovery
Network Partition
* Eclipse attack on an arbitrary node
* Excludes network partitions that require control of the p2p network (including, but not limited to, control over a large number of p2p nodes) or underlying networking infrastructure (including, but not limited to, control of bootstrapper nodes)
Supply Chain Attacks
* Attacks that identify gaps in the implementation of Github security policies for managing releases of source code, pre-built binaries, or docker images, that allow downloading malicious code
* Excludes social attacks and phishing attacks
### Medium: Up to $100 in TIA tokens
DoS Attacks (Resource Exhaustion)
* Remote resource exhaustion via non-RPC protocols.
State Corruption
* Inclusion of a valid transaction or blob that results in an EDS or data root that is not reconstructable
DA network
* Issues that affect the celestia-node bridge node.
## Out of Scope:
The following components are out of scope for the bounty program:
* Any DDoS attack
* Any metrics, logging, or tracing, such as Grafana, Prometheus, etc.
* Any infrastructure for running nodes
* Any encrypted credentials, auth tokens, etc. checked into version control
* Bugs in dependencies other than those explicitly listed. Please take them upstream!
* Attacks that require social engineering
* Attacks that require network partitions (but not network partitions themselves, see above)
* Attacks that require physical access
* Any asset whose source code does not exist in the in-scope repositories
* Any bugs caused by user, intentionally or by error
* celestia-node light node
## Program Rules
* When testing for possible bugs please adhere to the following:
* Stay within the defined scope of the program and only perform testing within the program scope.
* Do not damage or restrict the availability of products, services, or infrastructure
* Do not compromise any personal data
* Do not cause interruption or degradation of any service
* Don’t access or modify other user data, instead localize all tests to your accounts
* Do not test against mainnet, instead use testnets and local devnets
* Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
* Don’t spam forms or account creation flows using automated scanners
* Do not use web application scanners for automatic vulnerability searching which generates massive traffic, as web properties are out of scope for this program.
* In that case where you find a vulnerability that qualifies for multiple categories/severities, please only submit it once for the highest category/severity, as we will only pay for the highest category/severity.
* Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized representative of the Celestia Foundation without appropriate permission
* In case that your findings is valid you will be asked for KYC verification to proceed with payments
* For more information, check: https://docs.celestia.org/
## Reporting / Disclosures
**DO NOT CREATE A GITHUB ISSUE** to report a security problem.
Instead please use the HackenProof bug bounty program. Provide a helpful title, detailed description of the vulnerability and an exploit proof-of-concept. Speculative submissions without proof-of-concept will be closed with no further consideration.
Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
Expect a response as fast as possible in the advisory, typically within 72 hours.
If you do not receive a response from HackenProof, send an email to [\[email protected\]](/cdn-cgi/l/email-protection) with the full URL of the advisory you have created. DO NOT include attachments or provide detail sufficient for exploitation regarding the security issue in this email. **Only provide such details in the advisory**.
## Eligibility
* Only those that meet the following eligibility requirements may receive a monetary reward:
* You must be the first reporter of a vulnerability
* The vulnerability must be a qualifying vulnerability
* Submissions MUST include an exploit proof-of-concept to be considered eligible:
* Valid exploits MUST NOT be executed on any public cluster, public testnet, or in any public manner
* Proof-of-concepts should be demonstrated using localized or private networks
* The participant submitting the bug report must follow the process outlined within this document
* Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through [hackenproof.com](https://dashboard.hackenproof.com/redirect?url=https://hackenproof.com/programs)
* You must send a clear textual description of the report along with steps to reproduce the issue, including attachments such as screenshots or proof of concept code as necessary
* ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded)
* Participants must complete a compliance screen and sign the participation agreement with Hacken. Security exploits will still be assessed and open for submission at all times. This needs only be done prior to distribution of tokens.
* Provide detailed but to-the point reproduction steps
* Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
* Employees, spouses, partners, or families of employees, or of former employees, of Celestia Labs, the Celestia Foundation, and any subsidiaries, are not eligible to participate in the Bug Bounty program
## Payment of Bug Bounties
**Prize Details and Eligibility Requirements**
* Before you are eligible to receive a reward for a successful bug bounty submission, you must complete a compliance screen
* For eligible hackers, bounties will be paid in TIA, subject to the following unlock schedule:
* 25% unlocked at the time of payment
* 75% locked until 12 months after the time of payment
* The amount of TIA to be paid for each bounty will be calculated using a trailing, three-day, time weighted average price of TIA from the date a vulnerability report is submitted by a hacker, but excluding such date, based on the “Open” USD price of TIA provided by Coingecko.