Threshold
PolkaWorld votes AYE
LunoKit addresses some of the most pressing and practical pain points facing Web3 app development in the Polkadot ecosystem:
• High integration costs across multiple wallets
• Scattered and inconsistent account state management
• Repetitive, custom-built UI components
• Fragmented on-chain data subscription and caching
• Limited documentation and isolated code examples
These are real challenges every DApp team in the ecosystem encounters. LunoKit takes a pragmatic approach by bundling standardized SDKs and UI kits to solve them in a unified, developer-friendly way—offering strong ecosystem value.
The budget is reasonable and well-structured:
• A total of $49,200, covering three months of work for two full-time engineers
• Clear breakdown across modules (UI, hooks, core abstraction, docs, etc.)
• No inflated scope or padded time estimates
This makes the proposal financially sound, professionally scoped, and highly deliverable.
As a result, this proposal has received unanimous approval from PolkaWorld. You can view all feedback here.
Hello team,
thank you for this proposal, the initiative is very good. I think the ecosystem will benefit from having several frontend app tools available. I have one concern though.
As you know, UX bounty is currently in the phase of rolling out a component library as you know from this forum post: https://forum.polkadot.network/t/ux-bounty-request-for-feedback-a-unified-ui-component-library/13082. I think it would make most sense if you focussed on the hooks part with dedot and provide the hooks you mentioned above. As we can see from reactive-dot and also wagmi a hooks library is a proven approach. I think its also logically better to not mix the two.
A component library build on the hooks library could either be a milstone 2 with another funding request from the treasury or just fund a collaboration with the executors of the UX bounty component library too.
hello,
+on-chain identity not available
+Could you show previous collaborations using Polkadot technology?
+Could you provide previous work related to the topic of the proposal you've generated?
Nay on this because this likely already exists in the ecosystem or overlaps with work that most teams would naturally do as part of their development process. It also seems that the proposal is primarily focused on UI/UX improvements, so it would probably be better suited for the UI/UX bounty rather than as a standalone proposal. REEEEEEEEEE DAO.
TruthDAO votes AYE
Rationale:
• High cost-efficiency: A $49K investment to support the entire ecosystem’s developer base, with near-zero marginal cost.
• Improving the developer experience on Polkadot is a high-priority direction at this stage.
Suggestions for improvement:
Consider exploring integration with WalletConnect, and building Polkadot/Polkadot Hub extensions on top of an already widely adopted solution.
Read all feedback here.
📖Truth DAO Governance Statement
🗳️ Delegate
Edited
Dear Proposer,
Thank you for your proposal. Our first vote on this proposal is AYE.
The Small Spender track requires 50% participation and simple majority of non-abstain votes according to our voting policy v0.2, and any referendum in which the majority of members vote abstain receives an abstain vote. This proposal has received five aye and zero nay votes from ten available members, with one member abstaining. Below is a summary of our members' comments:
One member chose to abstain, citing an already crowded candidate field and questioning the urgency of the proposed account connection. However, a majority expressed support for the initiative, highlighting its potential to foster healthy competition within the ecosystem. They anticipated positive outcomes from the new solution, appreciated its reasonable budget, and noted its complementary nature to existing tools, particularly in terms of simplifying key management. Overall, the sentiment leaned towards optimism and enthusiasm for the proposal.
The full discussion can be found in our internal voting.
Please feel free to contact us through the links below for further discussion.
Kind regards,
Permanence DAO
Decentralized Voices Cohort IV Delegate
📅 Book Office Hours
💬 Public Telegram
🌐️ Web
🐦 Twitter
🗳️ Delegate
Edited
✅ Why Vote YES
• Massive DevX Improvement: Provides a plug-and-play TypeScript + React SDK that connects all major Polkadot wallets (polkadot.js, Talisman, SubWallet, Nova, etc.) in under 10 minutes.
• Full-stack Dev Support:
• @luno-kit/core: Wallet abstraction & signer management
• @luno-kit/react: 20+ React hooks (useConnect, useBalance, etc.)
• @luno-kit/ui: Pre-built UI components (wallet modals, asset panels, network switchers)
• Built for Polkadot Hub: EVM support coming post-launch, allowing seamless interaction with both Substrate and EVM accounts.
• Strong Team Track Record: The Lunolab team previously built OmniBTC (cross-chain aggregator with $2B+ in volume) and contributed to ComingChat (10M+ users).
• Fully Documented & Developer-Ready: Full API docs, live demo, and a future Playground for visual integration and code export.
⸻
❌ Why Vote NO
• Focused on UI/UX, not Protocol Innovation: While highly useful, LunoKit is a frontend/developer tooling layer—not a protocol-level advancement.
• EVM Support Is Future Work: EVM compatibility is a key value point but is not yet available in the current version.
• Moderate Budget Size: $49k for v1 might be seen as high for a two-person team, depending on Treasury priorities.
• Small Team: Just two developers working full-time; delivery and updates may depend on long-term continuity.
⸻
🎯 Conclusion:
LunoKit offers a critical building block to improve developer experience and wallet connectivity in Polkadot, especially for projects on Polkadot Hub. It lowers the barrier to wallet integration, accelerates frontend development, and may help Polkadot attract more dApp developers.
NOTE - I am speaking personally, not as a representative of Web3 Foundation.
The Github history of the contributors does not make me confident that they can actually produce this product. I would recommend anyone voting Aye to take a closer look at their Github history.
OG Tracker Rating 2/3
Clear display of deliverables✅
Clear display of a valid direct point of contact❌
Clear display of proposal’s duration✅
OGT Rating aims to help voters make better informed decisions and direct proposers towards certain common-good practices. We are providing feedback based on 3 simple yet crucial criteria which we believe should be included in every OpenGov referenda.
Edited