PlutoFramework
71 posts
@PlutoFramework
All in one framework for creating web3 mobile applications.
🗳️PolkaWorld Weekly Vote Recap 🗳️ This week we reviewed 6 proposals — here’s how we voted + some OpenGov thoughts at the end 🧵 ⛔️ #1667 Merkle Mountain Belts (MMB) – 340.2K USDC & 42.19K DOT #11" target="_blank" rel="nofollow noopener">polkadot.subsquare.io/referenda/1667…
ABSTAIN After a call with the team, we saw the value — but with an excessively high hourly rate, we ultimately chose to ABSTAIN. ✅ #1684 sub0 25 Polkadot Flagship Conference (Buenos Aires) – 738.75K USDC #8" target="_blank" rel="nofollow noopener">polkadot.subsquare.io/referenda/1684… AYE 2/3 in favor, 1/3 against. Supporters praised the clear budget & proven event quality. Opponents flagged the $700K price tag for 3,000 attendees as high with limited ROI. Overall → we supported it. ❌#1685 “What’s Up on Polkadot?” Hub by web3rdy – 1K DOT #5" target="_blank" rel="nofollow noopener">polkadot.subsquare.io/referenda/1685… NAY ➡️ Features will land in the Polkadot App soon. ➡️ Without major incentives, changing user habits is hard. ⛔️#1686 PolkaBiz Retroactive (May–July 2025) – 62K USDC #5" target="_blank" rel="nofollow noopener">polkadot.subsquare.io/referenda/1686… ABSTAIN Solid work & reasonable ask — BUT too little info on which startups made tangible progress + new PW rule: ❌ funding above $100/hr. ❌#1688 Gossamer’s Contributions to Polkadot-SDK – 815.36K USDC #3" target="_blank" rel="nofollow noopener">polkadot.subsquare.io/referenda/1688… NAY Team already received $4.9M for Gossamer (client never went live). Gossamer = Go. Polkadot-SDK = Rust. Do they have the capacity? Also: overlap w/ Parity? ❌#1689 Quadrivium SDK Improvements – 288K USDC #3" target="_blank" rel="nofollow noopener">polkadot.subsquare.io/referenda/1689… NAY 46% of hours on PM, Shadow research & state archiving. $120/hr (over PW’s limit). Some budget items opaque. We urged clearer task breakdown + focus on critical SDK features. —————————— 💭 OpenGov takeaway This week we spent a lot of time talking with teams — even holding several calls — and one thing became clear: while PolkaWorld has a strict rule of rejecting any proposal with an hourly rate above $100, we’re now running into some real-world complications. Some former Parity developers — who were earning high salaries — have left the company but continue contributing through Treasury-funded proposals. The challenge: when their proposals genuinely benefit the community but their hourly rate is still above $100, and they’re not willing to lower it, what do we do? Do we stick firmly to the “no >$100/hr” rule, or do we make exceptions for proposals like this? There are definitely special cases here that require more thought. One thing is certain though: as @Polkadot 's security costs drop to $90M, Treasury inflows will shrink dramatically. That will inevitably mean fewer proposals — simply because there won’t be enough money to fund an ever-growing number of teams. I believe the @Web3foundation will have to step up again in situations like this. For cases like these, W3F should be the one making judgment calls on teams and talent — and paying higher salaries when needed to retain talent for Polkadot. Meanwhile, the Treasury’s future role should shift to providing only baseline funding. After all, Web3 Foundation originally received around 25% of DOT’s allocation, while the Treasury’s balance (currently ~26M DOT) is only 1.6% of total supply. What do you think?
