← Opportunities

Cosmos Bug Bounty Program

Funder
Cosmos · Cosmos Bug Bounty Program ⚪ No history
Type / status
other · open
Amount
—
Deadline
rolling
“Program policies, scope, and reward structures may be modified at any time without prior notice”
Ecosystems
cosmos
Categories
security
Tech stack
Apply
https://hackerone.com/cosmos
Source
https://cosmos.network/blog/updates-to-the-cosmos-bug-bounty-program
Fit
8% · poor fit · The Venture23 Aleo team works in the Aleo ecosystem with Rust/ZK/Leo tech stack, which is fundamentally different from Cosmos's SDK and blockchain infrastructure; they have no credible overlap in expertise or focus.
Trust
89% · model self-report 90% · first seen 2026-10-10 · v1
Verified
2026-11-17 · page still up, no closing language

The Cosmos Bug Bounty Program rewards security researchers for identifying vulnerabilities in the Cosmos Stack. Researchers should submit clear, high-quality reports with a valid Proof of Concept through the official HackerOne channel. The program focuses on in-scope systems and released code, with rewards granted at the discretion of the Cosmos team based on impact, quality, and validity. Participation is ongoing via HackerOne at https://hackerone.com/cosmos.

Eligibility: Open to security researchers who follow the program guidelines and submit findings through the official HackerOne channel.

Pipeline

Override status:

Funder track record · does Cosmos Hub / Interchain actually pay grants?

⚪ No payout history found · checked 2026-10-31 · 0 forum reports, 7 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.

Trust breakdown (3/3 checkable facts verified)

SignalWeightResultNote
deadline0.35100%source says rolling
apply link0.075100%link in source
funder0.075100%named in source
source quality0.1550%social or search hit
model confidence0.190%model self-report

Fit breakdown (against the ORG_* profile)

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

Sources (1)

RoleDocumentFromFetched
primaryUpdates to the Cosmos Bug Bounty Program | Secure and Performant Digital Ledger SolutionsWeb discovery: ecosystem sweep2026-10-10

History (1)

vChangedFields
12026-10-10created

Extracted text

![](/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2F9xlod89z%2Fproduction%2F957bfef8ddb317fe866f95cb228c985d747ca3dd-1200x675.png&w=3840&q=75)

# Updates to the Cosmos Bug Bounty Program

![bug-bounty-updates](https://cdn.sanity.io/images/9xlod89z/production/77e78c1f480457315aa74079e2130d56f223d458-5600x3000.png?w=3840&q=90&fit=max&auto=format)

*   Technology
    

*   [Key Program Guidelines](#key-program-guidelines)
*   [How to Contribute](#how-to-contribute)
*   [Program Disclaimer](#program-disclaimer)
*   [Thank You](#thank-you)

Security is fundamental to the long-term success of the Cosmos Stack. As part of our ongoing commitment to building secure, resilient blockchain infrastructure, we are sharing an updated overview of our bug bounty program policies. Our program has been in operation for 8 years now, protects hackers through Gold Standard Safe Harbor, and has a 98% response efficiency.

Recent advances in AI have created new challenges in organizations and the security research community, as researchers increasingly submit reports that do not comply with our program guidelines or policies.

These updates are intended to provide greater clarity, align expectations, and foster a strong, collaborative relationship with the security research community in response to these emergent challenges. By clearly defining how to participate, we aim to make it easier for researchers to contribute meaningful findings while helping us protect the broader ecosystem.

\[@portabletext/react\] Unknown block type "divider", specify a component for it in the \`components.types\` prop

## **Key Program Guidelines**

To ensure the effectiveness and integrity of the program, participants are expected to follow a few core principles:

*   Focus testing exclusively on in-scope systems and supported, released code
*   Submit clear, high-quality reports that include a valid Proof of Concept
*   Avoid duplicate, out-of-scope, or informational-only submissions
*   Limit testing strictly to what is necessary to demonstrate impact
*   Refrain from any activity that could disrupt systems, compromise data, or harm users
*   Contact the Cosmos team only through the official HackerOne channel

Failure to adhere to these guidelines—including repeated low-quality submissions, misconduct, violating confidentiality, or contacting us through unofficial channels—may result in report closure, ineligibility for rewards, or removal from the program.

\[@portabletext/react\] Unknown block type "divider", specify a component for it in the \`components.types\` prop

## **How to Contribute**

We welcome contributions from researchers who are committed to improving the security of the Cosmos Stack.

To get started:

*   Review the full program scope and participation requirements
*   Conduct testing responsibly and in accordance with the policy
*   Submit all findings through our official reporting channel on **HackerOne**

You can begin here: [**https://hackerone.com/cosmos**](https://hackerone.com/cosmos).

\[@portabletext/react\] Unknown block type "divider", specify a component for it in the \`components.types\` prop

## **Program Disclaimer**

To ensure transparency and proper expectations, please note the following:

*   Bounty rewards are granted at our sole discretion, based on factors such as impact, quality, and validity of submissions
*   Program policies, scope, and reward structures may be modified at any time without prior notice
*   We reserve the right to suspend or terminate the program, or remove participants from eligibility, at our discretion

Participation in the program constitutes acceptance of these terms.

\[@portabletext/react\] Unknown block type "divider", specify a component for it in the \`components.types\` prop

## **Thank You**

We would like to thank the security research community for your continued dedication to strengthening open, secure software systems. Your work plays a critical role in identifying vulnerabilities, improving resilience, and supporting the long-term health of the Cosmos ecosystem. We will be making additional changes and improvements to the program over the coming months that we hope will benefit both you and the program.

We appreciate your contributions and look forward to continuing this work together.  

![Alex Johnson](https://cdn.sanity.io/images/9xlod89z/production/a637bb7baa961c2fb1a4859c66c88aac39c37ba4-181x181.svg?w=3840&q=90&fit=max&auto=format)

Alex Johnson

Security Operations Lead

[LinkedIn](https://www.linkedin.com/in/alex-johnson-20087732b/)