Bug Bounty Program
The zkSync Lite Bug Bounty Program rewards security researchers for identifying critical vulnerabilities that could lead to substantial loss of funds or protocol disruption. Researchers must be the first to report a valid issue, verify ownership via signature, and disclose responsibly through encrypted email to security@zksync.io. Payouts reach up to $500,000 for severe cases involving total loss of funds. Applications are ongoing with no fixed deadline.
Eligibility: Must be the first reporter of the vulnerability, able to verify a signature from the same address, and provide sufficient information about the issue.
Pipeline
Funder track record · does ZKsync actually pay grants?
🟡 Some payout evidence · 1 grantee found · last payout 2026-06-16 · checked 2026-10-31 · 1 forum reports, 6 web pages read
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 |
|---|---|---|---|
| 0xmadmaxx.eth | — | 2026-06-16 post date | “Final Report: ZK Stack Content Program (Community Activation RFP 2 – Extension)” forum |
Trust breakdown (2/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 | 0% | link not 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% | zksync vs aleo |
| category overlap | 0.15 | 17% | security vs zk, privacy, infra, dev_tooling, security, interoperability |
| tech overlap | 0.1 | 0% | none vs rust, leo, zk |
Sources (1)
| Role | Document | From | Fetched |
|---|---|---|---|
| primary | Bug Bounty Program | zkSync Lite Documentation | Web discovery: ecosystem sweep | 2026-10-13 |
History (1)
| v | Changed | Fields |
|---|---|---|
| 1 | 2026-10-13 | created |
Extracted text
# [#](#bug-bounty-program) Bug Bounty Program
* [Bug Bounty Program](#bug-bounty-program)
* [Scope](#scope)
* [Assumptions](#assumptions)
* [Disclosure Policy](#disclosure-policy)
* [The wrong way to disclose](#the-wrong-way-to-disclose)
* [The right way to disclose](#the-right-way-to-disclose)
* [Exclusions](#exclusions)
* [Eligibility](#eligibility)
* [Bounty Payout](#bounty-payout)
* [Contact](#contact)
* [PGP Key](#pgp-key)
## [#](#scope) Scope
Issues that can lead to substantial loss of money, critical bugs like a broken live-ness condition, blocking upgrade system, irreversible loss of funds, or enforced exodus mode.
## [#](#assumptions) Assumptions
In order to be eligible for the bug bounty, a bug should adhere to the security assumptions of zkSync. You can read more about them [here (opens new window)](https://github.com/matter-labs/zksync/blob/master/docs/protocol.md#assumptions).
## [#](#disclosure-policy) Disclosure Policy
Let us know as soon as possible upon discovery of a potential security issue.
Provide us a reasonable amount of time to resolve the issue **before any disclosure** **to the public or a third party.**
### [#](#the-wrong-way-to-disclose) The wrong way to disclose
The following actions will make you ineligible for the bug bounty program:
* Filing a public issue about the vulnerability
* Testing the vulnerability on mainnet or testnet
### [#](#the-right-way-to-disclose) The right way to disclose
Please email us at [security@zksync.io](mailto:security@zksync.io). We appreciate detailed information about confirming or fixing the vulnerability. If possible, please use the PGP key below to encrypt the message.
## [#](#exclusions) Exclusions
* Already known vulnerabilities.
* Vulnerabilities in code not leading to funds lost or frozen.
* Vulnerabilities not related to smart contracts or cryptography used by the protocol.
## [#](#eligibility) Eligibility
* You must be the first reporter of the vulnerability
* You must be able to verify a signature from the same address
* Provide enough information about the vulnerability
## [#](#bounty-payout) Bounty Payout

For severe cases involving a total loss of funds, we will pay a bounty of $500,000.
## [#](#contact) Contact
Please submit all your requests here: [security@zksync.io](mailto:security@zksync.io).
### [#](#pgp-key) PGP Key
The following PGP key may be used to communicate sensitive information to developers:
Fingerprint: `5FED B2D0 EA2C 4906 DD66 71D7 A2C5 0B40 CE3C F297`
```
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQINBGEBmQkBEAD6tlkBEZFMvR8kOgxXX857nC2+oTik6TopJz4uCskuqDaeldMy
l+26BBzLkIeO1loS+bzVgnNFJRrGt9gv98MzNEHJVv6D7GsSLlUX/pz7Lxn0J4ry
o5XIk3MQTCUBdaXGs6GBLl5Xe8o+zNj4MKd4zjgDLinITNlE/YZCDsXyvYS3YFTQ
cwaUTNlawkKgw4BLaEqwB2JuyEhI9wx5X7ibjFL32sWMolYsNAlzFQzM09HCurTn
q0DYau9kPJARcEk9/DK2iq0z3gMCQ8iRTDaOWd8IbSP3HxcEoM5j5ZVAlULmjmUE
StDaMPLj0Kh01Tesh/j+vjchPXHT0n4zqi1+KOesAOk7SIwLadHfQMTpkU7G2fR1
BrA5MtlzY+4Rm6o7qu3dpZ+Nc4iM3FUnaQRpvn4g5nTh8vjG94OCzX8DXWrCKyxx
amCs9PLDYOpx84fXYv4frkWpKh2digDSUGKhoHaOSnqyyvu3BNWXBCQZJ20rqEIu
sXOQMxWIoWCOOPRRvrHrKDA2hpoKjs3pGsProfpVRzb9702jhWpTfbDp9WjQlFtX
2ZIDxlwAxcugClgrp5JiUxvhg2A9lDNwCF7r1e68uNv5usBZQVKPJmnvS2nWgKy8
x9oJsnwrEjxwiRHd34UvfMkwY9RENSJ+NoXqBdS7Lwz4m6vgbzq6K56WPQARAQAB
tCRaa1N5bmMgU2VjdXJpdHkgPHNlY3VyaXR5QHprc3luYy5pbz6JAk4EEwEKADgW
IQRf7bLQ6ixJBt1mcdeixQtAzjzylwUCYQGZCQIbAwULCQgHAgYVCgkICwIEFgID
AQIeAQIXgAAKCRCixQtAzjzyl5y8EAC/T3oq88Dak2b+5TlWdU2Gpm6924eAqlMt
y1KksDezzNQUlPiCUVllpin2PIjU/S+yzMWKXJA04LoVkEPfPOWjAaavLOjRumxu
MR6P2dVUg1InqzYVsJuRhKSpeexzNA5qO2BPM7/I2Iea1IoJPjogGbfXCo0r5kne
KU7a5GEa9eDHxpHTsbphQe2vpQ1239mUJrFpzAvILn6jV1tawMn5pNCXbsa8l6l2
gtlyQPdOQECy77ZJxrgzaUBcs/RPzUGhwA/qNuvpF0whaCvZuUFMVuCTEu5LZka2
I9Rixy+3jqBeONBgb+Fiz5phbiMX33M9JQwGONFaxdvpFTerLwPK2N1T8zcufa01
ypzkWGheScFZemBxUwXwK4x579wjsnfrY11w0p1jtDgPTnLlXUA2mom4+7MyXPg0
F75qh6vU1pdXaCVkruFgPVtIw+ccw2AxD50iZQ943ZERom9k165dR9+QxOVMXQ4P
VUxsFZWvK70/s8TLjsGljvSdSOa85iEUqSqh0AlCwIAxLMiDwh5s/ZgiHoIM6Xih
oCpuZyK9p0dn+DF/XkgAZ/S91PesMye3cGm6M5r0tS26aoc2Pk6X37Hha1pRALwo
MOHyaGjc/jjcXXxv6o55ALrOrzS0LQmLZ+EHuteCT15kmeY3kqYJ3og62KgiDvew
dKHENvg7d7kCDQRhAZleARAA6uD6WfdqGeKV5i170+kLsxR3QGav0qGNAbxpSJyn
iHQ8u7mQk3S+ziwN2AAopfBk1je+vCWtEGC3+DWRRfJSjLbtaBG8e6kLP3/cGA75
qURz6glTG4nl5fcEAa6B1st0OxjVWiSLX3g/yjz8lznQb9awuRjdeHMnyx5DsJUN
d+Iu5KxGupQvKGOMKivSvC8VWk9taaQRpRF+++6stLCDk3ZtlxiopMs3X2jAp6xG
sOBbix1cv9BTsfaiL7XDL/gviqBPXYY5L42x6+jnPo5lROfnlLYkWrv6KZr7HD4k
tRXeaSwxLD2EkUyb16Jpp0be/ofvBtITGUDDLCGBiaXtx/v8d52MARjsyLJSYloj
1yiW01LfAiWHUC4z5jl2T7E7sicrlLH1M8Z6WbuqjdeaYwtfyPA2YCKr/3fn6pIo
D+pYaBSESmhA92P+XVaf5y2BZ6Qf8LveDpWwsVGdBGh9T0raA1ooe1GESLjmIjUa
z5AeQ/uXL5Md9I6bpMUUJYQiH19RPcFlJriI3phXyyf6Wlkk8oVEeCWyzcmw+x1V
deRTvE2x4WIwKGLXRNjin2j1AP7vU2HaNwlPrLijqdyi68+0irRQONoH7Qonr4ca
xWgL+pAaa3dWxf0xqK7uZFp4aTVWlr2uXtV/eaUtLmGMCU0jnjb109wg5L0F7WRT
PfEAEQEAAYkCNgQYAQoAIBYhBF/tstDqLEkG3WZx16LFC0DOPPKXBQJhAZleAhsM
AAoJEKLFC0DOPPKXAAEP/jK7ch9GkoaYlsuqY/aHtxEwVddUDOxjyn3FMDoln85L
/n8AmLQb2bcpKSqpaJwMbmfEyr5MDm8xnsBTfx3u6kgaLOWfKxjLQ6PM7kgIMdi4
bfaRRuSEI1/R6c/hNpiGnzAeeexldH1we+eH1IVmh4crdat49S2xh7Qlv9ahvgsP
LfKl3rJ+aaX/Ok0AHzhvSfhFpPr1gAaGeaRt+rhlZsx2QyG4Ez8p2nDAcAzPiB3T
73ENoBIX6mTPfPm1UgrRyFKBqtUzAodz66j3r6ebBlWzIRg8iZenVMAxzjINAsxN
w1Bzfgsi5ZespfsSlmEaa7jJkqqDuEcLa2YuiFAue7Euqwz1aGeq1GfTicQioSCb
Ur/LGyz2Mj3ykbaP8p5mFVcUN51yQy6OcpvR/W1DfRT9SHFT/bCf9ixsjB2HlZGo
uxPJowwqmMgHd755ZzPDUM9YDgLI1yXdcYshObv3Wq537JAxnZJCGRK4Y8SwrMSh
8WRxlaM0AGWXiJFIDD4bQPIdnF3X8w0cGWE5Otkb8mMHOT+rFTVlDODwm1zF6oIG
PTwfVrpiZBwiUtfJol1exr/MzSPyGoJnYs3cRf2E3O+D1LbcR8w0LbjGuUy38Piz
ZO/vCeyJ3JZC5kE8nD+XBA4idwzh0BKEfH9t+WchQ3Up9rxyzLyQamoqt5Xby4pY
=xkM3
-----END PGP PUBLIC KEY BLOCK-----
```
← [Security by correctness, isolation, and obscurity](/dev/security/approach/) [Vulnerability Disclosure](/dev/security/disclosure/) →