[BS] #1715 - DotFuzz - Hardening Polkadot through TryState invariants and CI-fuzzing
closed
Description

https://polkadot.subsquare.io/referenda/1715

  • A plan to make Polkadot safer from hackers
  • Adding checks (TryState) to important parts of Polkadot
  • Building a tool (DotFuzz) to find bugs automatically
  • Working with Polkadot’s team for 6 months
  • First step: Add safety checks to Polkadot’s code
  • Second step: Use fuzzing to catch hidden bugs
  • Deliverables: Reports, merged checks, and a public tool
  • Team has worked on Polkadot security before
Optionssingle
Results
Voters
3
one-person-one-vote
Information
Members
5
Timestamp
Created
Aug 18 2025 14:55
Start date
Aug 18 2025 14:55
End date
Sep 17 2025 14:55

Votes·3

14pa...oata
14pa...oata
14pa3BAYZLPvZfRDjWEfZXZWBVU45E67HUQEUxNCrdXGoata
Nay
Nay

投票为Nay
目前要价过高,产品有实际用途,但目前的价格显然高于了社区对其的期待

16ap...141C
16ap...141C
16ap6fdqS2rqFsyYah35hX1FH6rPNWtLqqXZDQC9x6GW141C
Abstain
Abstain

投票为 Abstain
暂时不清楚该项目的投入 ROI,希望从收集更多来自开发者的意见后再进行决定

15MF...fLzE
15MF...fLzE
15MFgTrCqjnLRPkDymuuhBMpzxQmcRyfFDETRiEtBRjpfLzE
Nay
Nay
  1. 提案中提到”在为期 6 个月的工作中,我们将与 Polkadot 的核心开发者及生态相关方紧密合作,本提案与他们的目标高度一致。“ 关于这一点,需要团队补充是在与哪些核心开发者和生态方在紧密合作,因为这关乎到 Polkadot SDK 的安全问题,需要类似 Parity 或 Fellowship 这样的核心开发者来确认是否在合作。
  2. 关于预算部分,没有进一步的解释为什么需要近 50 万美金的预算,以及没有明确有多少人参与开发,所以无法判断申请的金额是否合理。

Discussions·0

No current comments
Information
Members
5
Timestamp
Created
Aug 18 2025 14:55
Start date
Aug 18 2025 14:55
End date
Sep 17 2025 14:55
Results
Voters
3
one-person-one-vote
© 2025 OpenSquare. All Rights Reserved.