← Opportunities

Stellar Bug Bounty Program

Funder
Stellar Development Foundation · Bug Bounty Program ✅ Proven payer
Type / status
bounty · open
Amount
—
Deadline
rolling
“The Stellar Bug Bounty Program provides bounties for vulnerabilities and exploits discovered in the Stellar protocol or any of the code in our repos.”
Ecosystems
stellar
Categories
security
Tech stack
Apply
https://hackerone.com/stellar
Source
http://www.blockchain-asia.com/bug-bounty.html
Fit
8% · poor fit · The Venture23 Aleo team works in the Aleo ecosystem with ZK and Rust tooling, which is entirely unrelated to Stellar's protocol, core repositories, or web properties.
Trust
52% · model self-report 90% · first seen 2026-10-01 · v27
Verified
2026-11-17 · page still up, no closing language

The Stellar Development Foundation runs a bug bounty program for vulnerabilities in the Stellar protocol, core repositories, SDF-maintained services, and stellar.org web properties. Security researchers and eligible individuals can submit findings via HackerOne for rewards paid in XLM based on severity and impact. Payouts vary by severity with no fixed maximum; the program uses CF Benchmarks XLMUSD_RR for USD-to-XLM conversion at distribution time.

Eligibility: Open to individuals aged 18+ or minimum legal age for crypto use in jurisdiction, not located in sanctioned countries (Cuba, Iran, North Korea, Syria, Russian-controlled Ukraine regions), not on OFAC SDN list, and not residing where crypto holding is illegal without license. Teams and organizations of eligible individuals also eligible. Submissions must not violate laws, promote unlawful activities, gambling, offensive/harmful content, sexually obscene material, discrimination, or contain malware/phishing.

Pipeline

Override status:

Funder track record · does Stellar Development Foundation actually pay grants?

✅ Proven payer · 7 grantees found · last payout 2026-10-29 · checked 2026-10-30 · 0 forum reports, 6 web pages read, 4 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.

GranteeAmountDateEvidence
Marketnode—2026-10-29
page date
“Stellar Development Foundation Makes Strategic Investment in Marketnode to Expand Institutional Tokenized Real-World Asset Adoption in Asia-Pacific” source
University Of Flordia Foundation$280Kundated“Recent Stellar Foundation grant recipients include University Of Flordia Foundation ($280K)” source
Uf Foundation$195Kundated“Recent Stellar Foundation grant recipients include University Of Flordia Foundation ($280K); Uf Foundation ($195K)” source
Unf Foundation$68Kundated“Recent Stellar Foundation grant recipients include University Of Flordia Foundation ($280K); Uf Foundation ($195K); Unf Foundation ($68K)” source
Uf Health Jacksonville$60Kundated“Recent Stellar Foundation grant recipients include University Of Flordia Foundation ($280K); Uf Foundation ($195K); Unf Foundation ($68K); Uf Health Jacksonville ($60K)” source
Deerwood Rotary Charities INC$40Kundated“Recent Stellar Foundation grant recipients include University Of Flordia Foundation ($280K); Uf Foundation ($195K); Unf Foundation ($68K); Uf Health Jacksonville ($60K); Deerwood Rotary Charities INC ($40K)” source
Ymca Of Florida'S First Coast INC$40Kundated“Recent Stellar Foundation grant recipients include University Of Flordia Foundation ($280K); Uf Foundation ($195K); Unf Foundation ($68K); Uf Health Jacksonville ($60K); Deerwood Rotary Charities INC ($40K); Ymca Of Flor” source

Trust breakdown (2/3 checkable facts verified)

SignalWeightResultNote
deadline0.350%rolling claimed but not stated
apply link0.075100%link in source
funder0.075100%named in source
source quality0.1550%social or search hit
model confidence0.190%model self-report
corroborationbonus+10%28 sources

Fit breakdown (against the ORG_* profile)

SignalWeightResultNote
model fit0.510%model rated 10%
ecosystem overlap0.250%stellar vs aleo
category overlap0.1517%security vs zk, privacy, infra, dev_tooling, security, interoperability
tech overlap0.10%none vs rust, leo, zk

Sources (28)

RoleDocumentFromFetched
primaryStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-01
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-01
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-02
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-05
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-06
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-07
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-07
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-09
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-11
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-11
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-13
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-14
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-14
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-14
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-15
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-15
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-18
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-18
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-18
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-20
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-20
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-26
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-27
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-27
mirrorStellar.org | Response Policy | HackerOneWeb discovery: ecosystem sweep2026-10-27
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-27
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-10-27
mirrorStellar | Bug Bounty ProgramWeb discovery: ecosystem sweep2026-11-17

History (27)

vChangedFields
272026-11-17summary
262026-10-27summary
252026-10-27summary, amountMin, amountMax, currency, amountMinUsd, amountMaxUsd, applicationUrl
242026-10-27summary, amountMin, amountMax, currency, amountMinUsd, amountMaxUsd, applicationUrl
232026-10-27summary
222026-10-27summary
212026-10-26summary
202026-10-23summary
192026-10-23summary
182026-10-18summary
172026-10-18summary, type
162026-10-18summary, type
152026-10-15summary, type
142026-10-15summary, type
132026-10-14summary, type
122026-10-14summary
112026-10-14summary, type
102026-10-13summary
92026-10-11summary
82026-10-09summary
72026-10-07summary
62026-10-07summary, type
52026-10-06summary, type
42026-10-05summary
32026-10-02summary
22026-10-01summary, applicationUrl
12026-10-01created

Extracted text

Stellar | Bug Bounty Program

[](index.html)

[Dev Docs](https://developers.stellar.org/)

Menu

Jump to...

Grants & Funding

# Bug bounty program

The Stellar Bug Bounty Program provides bounties for vulnerabilities and exploits discovered in the Stellar protocol or any of the code in our repos. We recognize the importance of our community and security researchers in helping identify bugs and issues. We encourage responsible disclosure of security vulnerabilities via our bug bounty program described on this page.

Responsible Disclosure

## We're on it.

Our development team has up to 90 days to implement a fix based on the severity of the report. Please allow for this process to fully complete before you publicly disclose the vulnerability.

Programs

## File a bug report

The Stellar Development Foundation has partnered with these trusted bug bounty platforms to ensure reports are handled in a fair and timely manner. The payout models vary based on the severity/impact. Please refer to the payout structures supported on [Immunefi](https://immunefi.com/bounty/stellar/) and [HackerOne](https://hackerone.com/stellar?view_policy=true) terms.

*   Try to include as much information in your report as you can, including a description of the bug, its potential -impact, and steps for reproducing it or proof of concept
*   Please allow 3 business days for us to respond before sending another email

Please refer to Immunefi's point classification system [here](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-3/).

There are two Immunefi bounties supported by the Stellar Development Foundation.

**Stellar Bounty**

Identify vulnerabilities related to Stellar network or Soroban smart contract core tech.

**Stellar Contracts OpenZeppelin Bounty**

Identify vulnerabilities related to OpenZeppelin developer tooling and contract standards.

[Stellar Bounty](https://immunefi.com/bug-bounty/stellar/information/)

[OpenZeppelin Contract Bounty](https://immunefi.com/bug-bounty/openzeppelin-stellar/information/)

Identify vulnerabilities in the Stellar network web applications and domains.  

[Explore Bounty](https://hackerone.com/stellar)

## Eligibility

Generally speaking, any bug that poses a significant vulnerability to the security or integrity of the Stellar network could be eligible for an award. However, it’s entirely at our discretion to decide whether a bug is significant enough to be eligible for an award.

In general, anything which has the potential for financial loss or data breach is of sufficient severity, including:

*   Implementation bugs that can lead to financial loss
*   Access to our production servers
*   Remote Code Execution
*   Protocol bugs
*   Crash bug in Stellar Core or Horizon (ex. a bug that can crash the app by sending a special request, not by sending thousands requests)

## Exceptions

In general, the following would not meet the threshold for severity:

*   Recently disclosed 0-day vulnerabilities
*   Vulnerabilities on sites hosted by third parties unless they lead to a vulnerability on the main website
*   Vulnerabilities contingent on physical attack, social engineering, spamming, DDOS attack, etc
*   Vulnerabilities affecting outdated or unpatched browsers
*   Vulnerabilities in third party applications that make use of Stellar’s API
*   Bugs that have not been responsibly investigated and reported
*   Bugs already known to us, or already reported by someone else (reward goes to first reporter)
*   Issues that aren’t reproducible
*   Issues that we can’t reasonably be expected to do anything about

Severity

## How serious is it?

The severity of a bug, i.e. how many participants in the Stellar network are affected, is taken into consideration when deciding the bounty payout amount. For example, an exploit that relies on an implementation bug in stellar-core affects the network as a whole and very deeply. There are no alternate implementations of stellar-core and so a payout that affects stellar-core would pay out higher than for example, an XSS bug.

Eligibility

## Bounty guidelines to participate

The Stellar Development Foundation (“**SDF**”) Research and Development (“**R&D**”) Grants Committee will only consider bounty submissions that meet the following eligibility criteria, so please read through these guidelines prior to submitting materials to the SDF Bounty Program.

## 1\. eligibility

1.1 The Bounty Program is only open to: (a) Eligible Individuals, as defined in Section 1.3 below; (b) teams of Eligible Individuals (“**Teams**”); and (c) organizations (e.g., corporations, limited liability companies, partnerships, and other corporate entities) that consist of Eligible Individuals and that are duly organized or incorporated and in good standing at the time of submission (“**Organizations**”). Eligible Individuals, Teams, and Organizations are collectively referred to herein as “**Participants**.”

1.2 When a Team or Organization submits materials to the Bounty Program, they should authorize a single Eligible Individual (a “**Representative**”) to represent, act, and prepare the submission on their behalf. By entering a submission on behalf of a Team or Organization, you are representing that you are authorized to act on behalf of such Team or Organization.

1.3 An “**Eligible Individual**” is a natural person who:

*   is the greater of: (i) 18 years of age or (ii) the minimum age that is legally permitted to use and hold cryptocurrencies and/or to participate in the Bounty Program in the jurisdiction where such person resides;
*   is not located in, under the control of, or a national or resident of Cuba, Iran, North Korea, Syria, any Russian-controlled regions of Ukraine, or any other country or region subject to sanctions by the U.S. Department of Treasury Office of Foreign Asset Control (“**OFAC**”), as may be updated from time to time;
*   is not identified on the Specially Designated Nationals or Blocked Persons list provided by OFAC; and
*   does not reside in a jurisdiction where the transfer and holding of cryptocurrency is illegal or would require a special license or authorization that such person does not possess.

1.4 Applicable law and our internal policies restrict SDF from providing XLM awards to certain categories of projects. The following types of projects will not be considered for the Bounty Program (or any XLM award in connection therewith):

*   violates any applicable laws, regulations, orders, judgements or rules or infringes or violates any proprietary right of any party, including patent, trademark, trade secret, copyright, right of privacy, right of publicity, or other rights;
*   involves, facilitates, supports, or promotes unlawful activities, including, but not limited to: fraud, drug trafficking, purchases on dark web markets, theft, illegal arms trafficking, human trafficking, abduction, extortion, embezzlement, corruption of public officials, acts of terrorism or terrorist financing, and intellectual property violations;
*   involves, facilitates, or promotes gambling;
*   is offensive, deceptive, harmful, or libelous;
*   is or contains sexually obscene content;
*   is discriminatory or abusive toward any individual or group; or
*   contains, transmit, or instills malware or phishing pages or devices.

If you are unsure whether your submission or project falls into one or more of these categories, please contact us at [\[email protected\]](email-protection.html#36645872764542535a5a574418594451) to discuss.

1.5 SDF complies with all applicable laws and regulations in the distribution of XLM awards. If your bounty submission is selected for the Bounty Program, you, your Team or your Organization (as applicable) will be required to complete certain compliance checks and submit certain tax forms to facilitate the receipt of any XLM award under the Bounty Program. Failure to submit appropriate documentation or failure to pass the required compliance checks may result in your disqualification from consideration. SDF is under no obligation to make any XLM awards if there are no eligible submissions or eligible Participants or if Participants do not successfully complete and comply with all necessary compliance and tax obligations.

1.6 To determine the number of XLM equal to the USD value of any award, the USD valuation of XLM shall be calculated using the CF Stellar Lumens-Dollar Settlement Price as administered, maintained, and reported by the cryptocurrency index provider CF Benchmarks Ltd. (using the ticker “**XLMUSD\_RR**”) (available at https://www.cfbenchmarks.com/indices/XLMUSD\_RR), or, if such settlement price is unavailable the settlement price as reported on a substantially similar and equally reputable cryptocurrency index provider selection by SDF in its reasonable discretion. The USD valuation of XLM for any particular award shall be calculated using the CF Stellar Lumens-Dollar Settlement Price (or equivalent) reported on the day such award is scheduled to be distributed. Participants acknowledge and understand that XLM is a highly risky and volatile asset, and that SDF does not provide any representations, warranties, or guarantees of its value.

1.7 Participants should inform themselves as to any legal and tax requirements or consequences applicable to them in respect of the acquisition, holding, and disposition of XLM. Participants are responsible for reporting the receipt of any XLM award to relevant government departments or agencies where applicable and paying all applicable taxes in their jurisdiction of residence (federal, state/provincial/territorial and local). SDF RESERVES THE RIGHT TO WITHHOLD A PORTION OF ANY XLM AWARD AMOUNT TO COMPLY WITH THE TAX LAWS OF THE UNITED STATES OR OTHER SDF JURISDICTION, OR THOSE OF A PARTICIPANT’S JURISDICTION.

## 2\. general conditions

2.1 SDF reserves the right, in its sole discretion, to cancel, suspend or modify the Bounty Program or any of these eligibility criteria for any reason. To the fullest extent permitted by law, any amendment will become effective at the time specified in the posting or, if no time is specified, the time of posting.

2.2 The Bounty Program is governed by the [SDF Terms of Service](terms-of-service.html) and these Eligibility Guidelines. If there is any conflict or inconsistency between the Terms of Service and these Eligibility Guidelines, these Eligibility Guidelines will prevail. 

2.3 SDF’s failure to enforce any term of these Eligibility Guidelines shall not constitute a waiver of that provision. Should any provision of these Eligibility Guidelines be or become illegal or unenforceable in any jurisdiction whose laws or regulations may apply, such illegality or unenforceability shall leave the remainder of these Eligibility Guidelines, to the fullest extent permitted by law, unaffected and valid. The illegal or unenforceable provision shall be replaced by a valid and enforceable provision that comes closest and best reflects the SDF’s intention in a legal and enforceable manner.

2.4 SDF may collect personal information in connection with a Bounty Program submission. Such information is subject to the [SDF Privacy Policy](privacy-policy.html).

### Contact

  
If you have any questions about the Bounty Program or your eligibility under these guidelines, please email [\[email protected\]](email-protection.html#a3f1cde7e3d0d7c6cfcfc2d18dccd1c4).

[](index.html)

### ABOUT US

*   [Stellar Development Foundation](foundation.html)
*   [Team](team.html)
*   [Careers](careers.html)
*   [Roadmap](roadmap.html)
*   [Brand Resource Hub](brand-resources.html)
*   [Press and Reports](press.html)
*   [Blog](blog.html)

### PRODUCTS AND SERVICES

*   [Use Cases](use-cases.html)
*   [Case Studies](case-studies.html)
*   [Products and Tools](products-and-tools.html)

### THE STELLAR NETWORK

*   [Anchor Directory](https://anchors.stellar.org/)
*   [Ecosystem Projects](ecosystem.html)
*   [Learn](learn.html)

### DEVELOPERS

*   [Stellar Network Docs](https://developers.stellar.org/docs)
*   [API Reference](https://developers.stellar.org/api)
*   [Dev Hub](developers.html)
*   [Bug Bounty](bug-bounty.html)

### CONNECT

*   [Community](community.html)
*   [Code of Conduct](code-of-conduct.html)
*   [FAQ](connect.html)