Quadrivium Polkadot-SDK improvements proposal 1

Deciding
Content
AI Summary
Reply
Up
Share
Request
288KUSDC
Status
Decision28d
Confirmation
4d
Attempts
0
Tally
1.2%Aye
98.8%Nay
Aye
69.9KDOT
Nay
6.01MDOT
  • 0.0%
  • 0.0%

    Threshold

  • 0.0%
Support
0.00%
33.14KDOT
Issuance
1.59BDOT
Votes
Nested
Flattened
Actions
Or do delegation here, check wiki.
Call
Metadata
Timeline3
Votes Bubble
Statistics
Comments

Hello,

Could you please share some estimated metrics related to the improvements that the implementation of this proposal will represent for the infrastructure?

Reply
Up

PolkaWorld votes NAY

1.	Work-hour structure is unreasonable: Project management + Shadow research + state archiving together account for nearly 1,100 hours, which is almost 46% of total hours — a very unusual allocation. The parts that actually deliver visible SDK-level functionality (like erasure coding, state sync, multi-slot collation) total only about 1,200 hours, roughly 50% of the total. For a 4-month technical proposal aimed at core SDK implementation, this ratio is disproportionately high.
2.	Some costs are opaque: Items like compliance expenses and tooling fees aren’t clearly detailed in the budget, making it hard to assess their validity.
3.	PolkaWorld rejects any proposal with an hourly rate above $100 — this proposal’s rate is $120/hour.

We recommend the team break down tasks more clearly and focus resources on the truly critical feature implementations to improve funding efficiency.

Reply
Up