← Opportunities

Tezos Foundation Bug Bounty Program

Funder
Tezos Foundation · Tezos Foundation Bug Bounty Program 🟡 Some evidence
Type / status
bounty · open
Amount
—
Deadline
rolling
“The Tezos Foundation has set up a Bug Bounty program... Reward original contributions that are submitted in a complete, well-documented way.”
Ecosystems
tezos
Categories
security
Tech stack
ocamlrust
Apply
mailto:security@tezos.com
Source
https://tezos.foundation/security/security-policy-bug-bounty
Fit
26% · weak fit · The Venture23 Aleo team's expertise in ZK and Rust aligns with the security and tech categories, but they operate in the Aleo ecosystem rather than Tezos, making them an outsider applicant.
Trust
88% · model self-report 85% · first seen 2026-10-23 · v1
Verified
2026-11-14 · page still up, no closing language

The Tezos Foundation runs a bug bounty program rewarding security researchers for finding and responsibly disclosing vulnerabilities in the Tezos protocol, the Octez implementation, and other software using the Tezos blockchain. Bounties are paid in tez tokens proportional to severity and frequency of occurrence. Researchers must follow responsible disclosure rules and submit complete, well-documented reports via email to security@tezos.com.

Eligibility: Open to security researchers and contributors who are not Tezos core development teams, Tezos Foundation employees, or developers under contract with Tezos organizations. Must follow responsible disclosure rules and not publicly disclose vulnerabilities without coordination.

Pipeline

Override status:

Funder track record · does Tezos Foundation actually pay grants?

🟡 Some payout evidence · 4 grantees found · last payout 2026-08-01 · checked 2026-10-30 · 0 forum reports, 8 web pages read, 5 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
Teia—2026-08-01“After receiving approval for a second batch of Tezos Foundation grant funding in August, Teia spent September collecting community event proposals, with a deadline at the end of the month.” source
ECAD Labs—2024-11-04
page date
“Leading the charge in this grant cycle is ECAD Labs with its Taquito project, a prominent Web3 library within the Tezos ecosystem.” source
Signatory—2024-11-04
page date
“Another recipient, Signatory, has been recognized for its crucial role in Tezos operations.” source
Sugar Gaming—2024-11-04
page date
“Sugar Gaming, a leader in the gaming industry with a user base of 60 million, is also among the grant beneficiaries.” source

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.185%model self-report

Fit breakdown (against the ORG_* profile)

SignalWeightResultNote
model fit0.540%model rated 40%
ecosystem overlap0.250%tezos vs aleo
category overlap0.1517%security vs zk, privacy, infra, dev_tooling, security, interoperability
tech overlap0.133%ocaml, rust vs rust, leo, zk

Sources (1)

RoleDocumentFromFetched
primaryBug Bounty Program - Tezos FoundationWeb discovery: ecosystem sweep2026-10-03

History (1)

vChangedFields
12026-10-23created

Extracted text

# Security Policy & Bug Bounty

## Expectations

In order to continuously improve the security of Tezos, the Tezos Foundation has set up a Bug Bounty program. The policy below explains what security researchers and contributors can expect and the ground rules of the program.

Security researchers and contributors can expect the Tezos Foundation to: 

*   Review submissions relating to the improvement of the security of the Tezos ecosystem,
*   Work with them to understand and validate their reports, provide timely initial responses to submissions,
*   Work to remediate discovered vulnerabilities in a reasonable timeframe,
*   Reward original contributions that are submitted in a complete, well-documented way.

## Scope

In scope of this policy are all security-relevant bugs and errors found in the Tezos ecosystem.

These include, but are not limited to, the following:

1.  Bugs in the Tezos protocol
2.  Bugs in the Tezos implementation (Octez)
3.  Bugs in any other software that uses the Tezos blockchain

## Out of Scope

The Tezos Foundation’s infrastructure (web servers, DNS, email, CMS, etc.) is not in scope of this policy. Should you have doubts as to the eligibility of the identified bug please contact the [Tezos Foundation Security Team](https://tezos.foundation/security/security-policy-bug-bounty/#reporting).

## Bug Bounties

For confirmed vulnerabilities, presented with a complete, well-documented report a bounty in Tezos tokens (“tez”) will be offered. The bounty will be proportional to the frequency of occurrence and/or the severity of the vulnerability being reported. The report should include a full description of the bug/exploit along with when and how it was discovered. New bugs in any other software that uses the Tezos blockchain (see number 3 in the list above) will be rewarded with a finder’s fee: the bounty for reporting these bugs, if there is one, is the responsibility of the team that developed the software. 

### Ground Rules

To encourage vulnerability research, and to avoid any confusion between legitimate research and malicious attacks, we ask that security researchers attempt, in good faith, to abide by the following:

*   Play by the rules. This includes following this policy and any other commonly accepted best practices,
*   Promptly report any vulnerability discovered,
*   Avoid violating the privacy of others, disrupting systems, destroying data, and/or harming user experience,
*   Use only the channels defined in section below “How to report” to discuss vulnerability information with the Tezos Foundation,
*   Handle details of any vulnerability discovered confidentially,
*   Perform testing only on in-scope systems avoiding systems and activities which are out-of-scope,
*   Should a vulnerability provide unintended access to data:
    *   Limit the amount of data accessed to the minimum necessary to demonstrate the vulnerability,
    *   Cease testing and submit a report the moment user data is encountered including, but not limited to: Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data or proprietary information,
    *   Only interact with test accounts one owns or with explicit permission from the account holder,
    *   Do not engage in extortion.

### Exclusion

In order to establish a fair reward program, the following user groups are not eligible to receive bug bounties:

*   Tezos core development teams, Tezos Foundation employees and all other people paid directly or indirectly by the Tezos Foundation (i.e. subsidiaries, service providers, grantees…),
*   Any developer under contract with one of the Tezos organizations.

Furthermore, the following disqualifies the researcher from the Bug Bounty program:

*   Public disclosure of the vulnerability without coordination with the Tezos Foundation,
*   Submitting issues which have already been submitted by another security researcher or that already known to the Tezos Foundation. However, well-documented bugs submitted after having been previously submitted by other researchers lacking documentation, are acceptable.

**Legal Safe Harbor**

For vulnerability research abiding by the conditions set out in this policy, the Tezos Foundation will consider said research to be:

*   Authorized with respect to any applicable computer crime legislation:
    *   The Tezos Foundation will not initiate or support legal action against the security researcher for accidental, good-faith violations of this policy.
*   Authorized with respect to any relevant anti-reverse engineering legislation:
    *   The Tezos Foundation will not initiate or support legal action against the security researcher for circumvention of anti-reverse engineering restrictions.
*   Exempt from restrictions in the Tezos Foundation’s policy which would interfere with conducting security research, waiving said restrictions on a limited basis.

Security researchers are expected to abide by all applicable laws. Should legal action be initiated by a third party against a security researcher, and the security researcher is in compliance with this policy, the Tezos Foundation will take appropriate steps to make it known that the security researcher’s actions were conducted in compliance with this policy.

Should a security researcher have concerns or doubts regarding the compliance of their research with this policy they are invited to contact the [Tezos Foundation Security Team](https://tezos.foundation/security/security-policy-bug-bounty/#reporting).

## Reporting

The Tezos Foundation Security Team can be contacted via email to security@tezos.com ([PGP key ID 16D0433F59CC3AC701C088E1FE0703C196EE4A04](https://tezos.foundation/.well-known/pgp-key.txt)).