Decentralized Security Marketplace
A request for proposals to build a decentralized security marketplace enabling projects to find auditors and whitehats for structured security tests and audits, with escrow and dispute resolution mechanisms. The platform would be built as a smart contract on parachains supporting WASM (e.g., Astar, Watr) using ink!.
Eligibility: Open to developers and teams capable of building smart contract platforms using ink! on WASM-compatible parachains.
Pipeline
Funder track record Β· does Web3 Foundation actually pay grants?
π‘ Some payout evidence Β· 7 grantees found Β· last payout 2026-01-27 Β· checked 2026-10-29 Β· 0 forum reports, 9 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 |
|---|---|---|---|
| Pop CLI | β | 2026-01-27 page date | βMilestone Report: Pop CLI | An All-in-one Tool for Polkadot Developmentβ source |
| Ink!ubator V2 | β | 2026-01-27 page date | βThe Final report of Ink!ubator V2β source |
| "Revive" Smart Contracts | β | 2026-01-27 page date | β"Revive" Smart Contracts: Status Updateβ source |
| Liberland Blockchain Team | β | 2023-03-13 | βThe Liberland Blockchain Team is happy to announce that they have received a grant from Web3 Foundation, and that they have successfully completed the first milestone.β source |
| Cere Network | β | 2021-09-17 | βCere Network has been awarded a Web3 Foundation grant, an award typically awarded to entities performing research and development in the field of decentralized software protocols.β source |
| open-web3-stack | β | undated | βORML is part of the bigger `Open-Web3-Stack` initiative, that is currently under a General Grant from Web3 Foundation.β source |
| Crust | β | undated | βCrust is the member of Web3 Bootcamp and Substrate Builders Program, and has received Web3 grant from Web3 Foundation.β source |
Trust breakdown (2/2 checkable facts verified)
| Signal | Weight | Result | Note |
|---|---|---|---|
| apply link | 0.075 | 100% | link in source |
| funder | 0.075 | 100% | named in source |
| source quality | 0.15 | 100% | official page or repo |
| model confidence | 0.1 | 70% | model self-report |
Fit breakdown (against the ORG_* profile)
| Signal | Weight | Result | Note |
|---|---|---|---|
| model fit | 0.5 | 70% | model rated 70% |
| ecosystem overlap | 0.25 | 0% | polkadot, astar, watrs vs aleo |
| category overlap | 0.15 | 33% | security, dev_tooling, dao_governance vs zk, privacy, infra, dev_tooling, security, interoperability |
| tech overlap | 0.1 | 33% | ink!, rust, substrate, wasm vs rust, leo, zk |
Sources (1)
| Role | Document | From | Fetched |
|---|---|---|---|
| primary | Decentralized Security Marketplace | Web3 Foundation Grants: RFPs (GitHub) | 2026-09-09 |
History (3)
| v | Changed | Fields |
|---|---|---|
| 3 | 2026-09-09 | summary |
| 2 | 2026-09-09 | summary |
| 1 | 2026-09-09 | created |
Extracted text
# Decentralized Security Marketplace :::caution This Request for Proposals is currently considered **under development**, meaning one or more grants have been signed to address the topic. We might be interested in additional implementations, but itβs better to double check this with the grants team. ::: * **Status:** [Under Development](https://github.com/w3f/Grants-Program/pull/1726) * **Proposer:** [Matteo Casonato](https://github.com/0xCaso), [Bhargav Batt](https://github.com/bhargavbh) ## Project Description :page_facing_up: According to the [*Immunefi's 2022 annual report*](https://assets.ctfassets.net/t3wqy70tc3bv/1ObYJk9jzWS4ExHICslYep/e2b5cee51268e47ee164c4dffbd78ad4/Immunefi_Crypto_Losses_2022_Report.pdf), there has been a total loss of ~$3.77B because of hacks in the web3 space. To increase a protocol's security, audits and bug bounties can be a useful tool. A **decentralized security marketplace** would allow projects to find reviewers/testers/auditors/whitehats and vice versa to pursue structured tests and audits. This would benefit everyone: - **Projects** would increase their security; - **Developers** would have the possibility to earn while using their skills, improving them; - The **ecosystem** would be more secure, with more projects being audited and more developers learning about security. Ideally, this marketplace would be built as a smart contract platform deployable on any existing parachain (that supports WASM smart contracts, such as [Astar](https://docs.astar.network/docs/getting-started) or [Watr](https://docs.watr.org/builders/substrate-contracts)) using [ink!](https://paritytech.github.io/ink/) ([here](https://github.com/paritytech/awesome-ink) you can see some examples). **Note**: This use case can be extended/applied to other areas. The main problem to solve here is to find a way to manage the *delayed* transaction between two parties (i.e., [escrow](https://en.wikipedia.org/wiki/Escrow)), and to ensure fairness and transparency (e.g., a reviewer is not able to deliver all the reports in time, and the project's team would like to decide whether to extend the escrow duration or just to pay a lower percentage of the established bounty). ### Actors :busts_in_silhouette: To ensure fairness and transparency, the marketplace could have the following actors: - **Projects** - The projects that want to be reviewed / tested; - **Auditors** - The developers that want to perform audits / hunt bugs; - **Arbiters** - The developers that will arbitrate the disputes between projects and auditors (they will be useful if a project opens a dispute for any reason). They could get a small percentage of the bounty. ## Deliverables :nut_and_bolt: The followings could be the initial deliverables of the project. Of course, improvements and additions are more than welcome. 1) Initial **research and design** of the protocol: - You can refer to what [Immunefi](https://immunefi.com/explore/) and [Code4rena](https://code4rena.com/) are doing (but bring that on-chain); - How to ensure the trustless interaction (e.g., projects could lock a percentage of the bounty to open the request); - What types of disputes could be risen and how to solve them; - How to manage time delays; - Look for other use cases (in or outside the security field); 2) Development of the **protocol**: - Development of the governance smart contract (e.g. to add/remove projects, auditors, arbiters, etc.); - Development of the auditing smart contract (e.g. to create audits); - Development of the arbitration smart contract (e.g. to create/solve disputes); 3) Development of the **frontend**, that enables the actors to interact with the protocol.