### **Proposal Overview**

We propose to harden Polkadot and increase its hacking resilience by:

1. Embedding TryState invariants across high-impact pallets, and
2. Launching an OSS-Fuzz-style framework, DotFuzz, for continuous runtime fuzzing, leveraging the invariants to transparently find deep logic bugs in new feature requests.

During the 6-month effort, we will collaborate closely with Polkadot’s core developers and ecosystem stakeholders, with whom this proposal is closely aligned.

The effort’s first value contribution is embedding standardized TryState invariants into Polkadot SDK pallets (starting from prioritized high-impact logic), ensuring that critical code changes are systematically verified. This strengthens the network’s safety without slowing development.

The second pillar involves leveraging industry-leading fuzzing technologies, specifically: Adapting Google’s OSS-Fuzz approach into a Polkadot-specific DotFuzz. The project will reach near-complete coverage of the codebase logic, with robust reporting and a reproducible test corpus that fosters security assurance and continuous improvement at an early development stage.

Funding is sought to support the end-to-end development and deployment of these advanced security capabilities over the course of six months.

[Full Proposal](https://docs.google.com/document/d/1tu72xTMl674gMiXR1Dw5ka2_pw5ne8D3gnK-Uvi2Ysc)

### **Deliverables**

* **Month 1:** Technical specification of the fuzzing farmwork; documents outlining the prioritization of pallets for the next steps
* **By month 3:** TryState invariants merged into polkadot-sdk
* **By month 6:** Fully open-source pipeline for continuous fuzzing of substrate-based runtimes, and a public dashboard for polkadot-sdk fuzzing

### **About Us**

Security Research Labs is a cybersecurity consultancy committed to making the world more secure. Discover more about us on [our website](https://srlabs.de/).

We have created two projects through referenda in the past ([942](https://polkadot.subscan.io/referenda_v2/942) and [1045](https://polkadot.subscan.io/referenda_v2/1045)), and have collaborated with Parity and other Polkadot ecosystem partners since 2019.

### **We Appreciate Your Feedback**

How can we improve our proposal? Your input will help us refine our approach to better serve the Polkadot community.

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least
`amount` of `asset_kind` in the native asset. The amount of `asset_kind` is converted
for assertion using the [`Config::BalanceConverter`].

## Details

Create an approved spend for transferring a specific `amount` of `asset_kind` to a
designated beneficiary. The spend must be claimed using the `payout` dispatchable within
the [`Config::PayoutPeriod`].

### Parameters
- `asset_kind`: An indicator of the specific asset class to be spent.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The beneficiary of the spend.
- `valid_from`: The block number from which the spend can be claimed. It can refer to
  the past if the resulting spend has not yet expired according to the
  [`Config::PayoutPeriod`]. If `None`, the spend can be claimed immediately after
  approval.

## Events

Emits [`Event::AssetSpendApproved`] if successful.

#1714 DotFuzz - Hardening Polkadot through TryState invariants and CI-fuzzing

No Active Proposals