**OG Tracker Rating 2/3**

**Clear display of deliverables✅**
- Wallet integration (polkadot.js, Talisman, SubWallet, Nova, PolkaGate)
- Core abstraction layer (@luno-kit/core)
- React Hooks (20+ hooks like useLunoConnect)    
- UI Component Library (v1)
- Theme system (light/dark mode support)
- State management & session persistence
- Network switching & chain management
- Documentation    
- Demo preview & site deployment
- UI design drafts
- Project management & testing

**Clear display of a valid direct point of contact❌**

- Not provided.
- The proposal lists the team members with their github profiles, but no specific contact details are provided.
- Could you please share a valid point of contact in case someone needs to reach out?

**Clear display of proposal’s duration✅**
- The duration of this proposal is 3 months.


_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._

PolkaWorld votes AYE

1.	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.

2.	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](https://southern-manicure-6ee.notion.site/1624-LunoKit-Developer-friendly-Web3-account-connection-infrastructure-218a3c644fba80959ed5ff050bd14ffb?source=copy_link).

[@polkaworld](12mP4sjCfKbDyMRAEyLpkeHeoYtS5USY4x34n9NMwQrcEyoh-polkadot) 

Thank you to PolkaWorld for the AYE vote !
We will strictly follow the development plan to ensure high-quality and on-time delivery, continuously contributing value to the Polkadot ecosystem.

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](https://reactivedot.dev/) and also [wagmi](https://wagmi.sh/) 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.



[@niftesty](1soESeTVLfse9e2G8dRSMUyJ2SWad33qhtkjQTv9GMToRvP-polkadot) 
Thank you very much for raising this concern.

To clarify, our Lunokit component library is intentionally focused on **account-related UI components**, which we see as an essential part of building a consistent and developer-friendly experience for wallet connection and beyond.

Luno's broader vision is to provide a robust, open-source Web3 account connection infrastructure for the Polkadot ecosystem. Wallet connect is just the first milestone — with future plans including Web2 social login, account abstraction, and more. To support these goals effectively, a dedicated, focused component library is necessary.

At the same time, our **hooks library is designed to be fully independent from the UI components**, giving developers the flexibility to use only the hooks with their own custom UI, or to combine them with Lunokit for a complete out-of-the-box solution. This separation ensures that teams with their own design systems, or those using the UX bounty component library, can still leverage our hooks without any friction.

We fully respect and support the UX bounty initiative and see it as complementary rather than conflicting. Their unified component library aims to cover broad, general-purpose UI needs for the entire ecosystem, while our work addresses the more specific requirements around **account connection infrastructure**.

Thank you again for your valuable input and support!

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?

[@SIM-DOT](15wbv2fXuFoeRcrWK4Q1Y5oM9LfsJyGmMXaUWDoAWXpZzWSp-polkadot) 

1.Our on-chain identity has already been successfully verified.

2.We have included the GitHub accounts of our team members in the proposal.

3.We've already submitted a demo preview for your reference.Additionally, I would like to emphasize that our demo is not just a simple interactive UI mockup. It showcases a real wallet connection and actual on-chain interaction, demonstrating the core technical capabilities of the product.

[@Luno-lab](14pGVuuBxbN9dVNGh2a6dNqAEP7f48z7ks5vH9WNXKakUm7Z-polkadot) 

The frontend profile do not demostrate relevant contributions:
![photo_5104928472702234361_y.jpg](https://subsquare.infura-ipfs.io/ipfs/QmeMyzXLiJAvPNptVcBcLpDFS9rcu9AkkTxVN4zxhEHChS)

And the core developer shows just a forked public repo for polkadot activities:
![photo_5105252300351451046_x.jpg](https://subsquare.infura-ipfs.io/ipfs/QmfZCoALxcwdeNhvt3ZRBRRC71rqGo4BmgknujyxL7tJCr)

After analyze the modules it's possible to see inconsistenses between topics and budget requested; the wallets mentionated had clear documentation about how to do sucessfully integrations. The $6k requested looks hight for that, the same for theme system. And finally to put together project management & testing is not a good practice in software development

Without relevant contribution on the ecosystem the suggestion is to try a W3F grant for software development, the open source bounty or OpnGov in a retroactive way. Meanwhile the vote is NAY for this request

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.

[@1THD...9Eoe](1THDCviNjyo7fUmoGZ9f8u3TznQNryWBWQCeZmDe11f9Eoe-polkadot) 
Thanks for your feedback! I fully understand your concerns and would like to clarify and emphasize a few important points:

Currently, the Polkadot ecosystem lacks an account connection infrastructure that is fully mature in terms of UI/UX and product functionality. Ethereum-based solutions like RainbowKit and Reown clearly demonstrate the value of such infrastructure, significantly reducing developer friction and gaining widespread adoption within their developer communities.

Although account integration is fundamental to DApp development, developers frequently encounter repetitive and fragmented workflows. LunoKit addresses this by providing comprehensive infrastructure—including standardized account management, wallet connections, chain switching, and session recovery—allowing developers to avoid redundant tasks and focus on core innovation.

With the launch of Polkadot Hub, we anticipate many more developers will join the ecosystem to deploy products. LunoKit will substantially reduce their development costs associated with account integration, helping them launch faster and more efficiently.

Therefore, we strongly believe LunoKit is not merely a set of UI components but rather a mature, feature-rich account connection infrastructure optimized for UI/UX, significantly reducing developer overhead.

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](https://voting.opensquare.io/space/truthdao/proposal/QmV7rD7otTB5HvqLM8xCbBFc1CJtaNkgPwi9qJXuvp4e1R).

📖[Truth DAO Governance Statement](https://southern-manicure-6ee.notion.site/Truth-DAO-Manifesto-0-0-1-1e9a3c644fba807fb88ef3eb5adc711b?pvs=4)

💭 Contact: [Email](open@truthdao.cn), [Telegram](https://t.me/truthdao_public)

🗳️ [Delegate](https://polkadot.subsquare.io/user/13dVYCGL27HhTWaAby3gAVPQkSqbGAyHQfdeUxsttDZi6afh/posted/referenda)

[@Truth DAO](13dVYCGL27HhTWaAby3gAVPQkSqbGAyHQfdeUxsttDZi6afh-polkadot) Thank you so much to TruthDAO for the support and constructive suggestions!We really appreciate your recognition of the proposal’s cost-efficiency and focus on improving the developer experience on Polkadot — that’s exactly our goal with LunoKit.As for the WalletConnect and Polkadot Hub extension suggestions — great points! I’m happy to share that WalletConnect support will be included in the first version of LunoKit.

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](https://docs.permanence.io/voting_policy/voting_policy_v0.2.html), 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](https://voting.opensquare.io/space/permanence/proposal/QmavNZwCtVcWeS3KnRgtGVYUi3bnHei56bcUTUY89nJXkt).

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](https://cal.com/permanencedao/office-hours) 💬 [Public Telegram](https://t.me/permanencedao) 🌐️ [Web](https://permanence.io) 🐦 [Twitter](https://twitter.com/permanencedao) 🗳️ [Delegate](https://polkadot.subsquare.io/user/15ubZj6T7NUYyQw6j4XBkEMJ2vew5w9kqKEcN1QG7Z1weKDV/votes)

[@PERMANENCE DAO/GOV-PROXY](13znFMMjHyM2UvSewvaKMC2bLUcySRMzcM8BAMTzm1G2P5ju-polkadot) Thank you so much for the detailed feedback and support! Really appreciate the time and consideration from the Permanence DAO .We fully understand the concerns some members raised regarding the current landscape, and we share the view that healthy competition and practical, developer-friendly solutions can help improve the ecosystem.
We’ll continue building LunoKit with that mindset.

✅ 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.

[@BILL](16frLykgLH5w8pNsvzEMTzCESMpLqWJMr4SGJUJQgYniDzdb-polkadot) Thank you for your feedback. Some of the products we developed in the past were not open-source. But regardless of whether this proposal is approved or not, we will continue working hard to build and improve our products and earn the recognition of the community.

beneficiary

The proposal is cancelled. We plan to develop the product first.After obtaining the recognition of the community, apply for the proposal.

assetKind

amount

validFrom

Rejected

Submitted

DecisionDepositPlaced

DecisionStarted

small_spender

LunoKit: Developer-friendly Web3 account connection infrastructure

root

whitelisted_caller

wish_for_change

staking_admin

treasurer

lease_admin

fellowship_admin

general_admin

auction_admin

referendum_canceller

referendum_killer

small_tipper

big_tipper

medium_spender

big_spender

Origin able to dispatch a whitelisted call.

Origin for signaling that the network wishes for some change

Origin able to cancel slashes and manage minimum commission.

Origin for spending up to 10,000,000 DOT from the treasury as well as generally administering it.

Origin for managing the composition of the fellowship.

Origin able to spend around 250 DOT from the treasury at once.

Origin able to spend around 1,000 DOT from the treasury at once.

Origin able to spend around 10,000 DOT from the treasury at once.

Origin able to spend around 100,000 DOT from the treasury at once.

Origin able to spend up to 1,000,000 DOT from the treasury at once.