This proposal requests $392,500 USDC to fund the operational costs of the Paseo testnet for H1 2026. This is the first Paseo funding proposal denominated in stablecoins, made possible by the newly deployed multi-asset bounty pallet. The remaining DOT balance in the existing bounty (~38,946 DOT) will be returned to the Polkadot treasury upon transition.

For full proposal details, including scope of work, quarterly budget breakdown, SLOs, and curator information, see the full proposal.

Note: This is a resubmission of referendum 1878. The original contained a technical error in the metadata field of the call data.

ignore

Upgrade to Release v2.2.1 whitelisted by https://collectives.subsquare.io/fellowship/referenda/516

Snowbridge Bug Bounty Programme Proposal Aug 2026-July 2027

This proposal requests funding to renew the Snowbridge bug bounty programme, which expired on 16 April 2026. Snowbridge secures ~$35M in TVL and processes $10M–$20M in monthly volume - a vulnerability could result in catastrophic loss of user funds and severe reputational damage to the Polkadot ecosystem.

The previous programme, run on HackenProof for one year, was funded by the Snowbridge team out of their own milestones. It received over 500 submissions, of which approximately 5 were valid findings that led to fixes ($22,300 paid out with Hackenproof, $15,000 paid to a security report logged before the Hackenproof programme). The programme must be renewed to ensure proper security coverage.

The total request is $355,000, covering 12 months of bug bounty operations.

Programme Scope

In Scope

The bug bounty covers all Snowbridge on-chain code (Ethereum contracts and Snowbridge Polkadot on-chain code) Scope can be viewed at our Hackenproof programme: https://hackenproof.com/programs/snowbridge-on-chain-code 

Out of Scope

• Off-chain relayers
• Frontend / dApp
• SDK and tooling

Severity Levels and Rewards

Programme Operations

Platform

The programme will continue on HackenProof, which hosted the previous year's programme.

Reporting

Bi-yearly reports to the community on:

• Number of submissions received
• Number of valid findings and their severity
• Rewards paid out
• Remaining fund balance

Cost Breakdown

Bug Bounty Fund

The reward pool covers payouts for valid findings. In 10 months, we will liaise with the Treasury to determine plans for the next year of Snowbridge and unspent funds will either carry-over into the next year's pool or be returned to the treasury. The pool must be large enough to credibly incentivize security researchers to investigate critical-severity vulnerabilities. Should the reward pool be depleted before the 12 month period, the programme will be paused until a top-up proposal passes Treasury governance.

Triage and Response Engineering

Running a bug bounty is not passive. The previous year's programme received over 500 submissions, the vast majority being false positives (estimated 99%). Each submission requires investigation and triage, ideally within 24 hours. Valid findings require additional time for root cause analysis, fix development, testing, and deployment.

This workload is increasing due to LLM-generated submissions, which are higher volume but lower quality - still requiring human review to identify the rare valid finding. We are working on setting up triage automations, which will help manage the increasing volume but will not eliminate the need for human review.

Total

Summary

Snowbridge is Polkadot’s trustless bridge to Ethereum and its L2 ecosystem, providing critical infrastructure for liquidity and users moving between the two ecosystems. Over the past year the bridge processed ~21,000 transfers, maintained $10M–$20M in monthly volume, and generated 14,100 DOT in revenue for the Polkadot Treasury (view dashboard).

During the previous funding period the team delivered Snowbridge V2, reducing bridging fees by up to 90%, enabling arbitrary contract execution, and launching support for Base, Optimism and Arbitrum.

This proposal funds the basic maintenance and operation of the bridge for the next 12 months. The total request is $364,200 for 12 months, significantly smaller than the previous proposal.

Overview

Snowbridge is Polkadot’s common good trustless bridge to Ethereum and its L2 ecosystem.

Over the past two years it has become core infrastructure for cross-ecosystem liquidity, enabling users to move assets between Ethereum (and recently Base, Optimism and Arbitrum) and the Polkadot ecosystem without trusted intermediaries.

Statistics about the last year:

• TVL: TVL peaked at $180M in October 2025 and currently stands at ~$60M, reflecting the broader crypto market downturn rather than a decline in bridge usage.
• Monthly Volume: Despite the extreme bear-market, Snowbridge usage has grown, with monthly transaction volume consistent between $10M-$20M. In October last year, volume jumped to $70M.
• Snowbridge dApp: The Snowbridge dApp has had ~29k visitors in the last year, with 4.2k users using Snowbridge to transfer tokens (20% of all transfers).
• Revenue Generation for Treasury: Snowbridge is one of the few treasury-funded projects that directly returns revenue to the Polkadot Treasury through bridge fees. Snowbridge has generated approximately 14,100 DOT in revenue from fees, and this was automatically deposited into the treasury.
• Hydration: Snowbridge is the main bridge supporting transfers to and from Hydration, Polkadot’s most successful DeFi project. In the last year, Snowbridge has enabled ~13k transfers between Hydration and Ethereum.
• Transfers: There have been 21k transfers through Snowbridge in the last year.
• Third-party relayers: Third-party relayers have started appearing organically, a sign that Snowbridge is maturing into decentralized infrastructure that others are building on independently.

Snowbridge had two main goals for 2025, besides running a secure bridge:

• reduce bridging cost
• reduce transfer latency

Our team has delivered on this promise, slashing bridging fees for our users by at least 80%, and reducing latency where possible.

Our review of the last year can be viewed at: https://docs.google.com/document/d/1UY1-Ju5WvAlYM4gv8NbSJh7Rurdpu8zZOrs5Fv8d7Io/edit?usp=sharing

Why Snowbridge Matters for Polkadot

• Liquidity access: Snowbridge connects Polkadot to the largest liquidity ecosystem in crypto: Ethereum and its L2s.
• Trustless architecture: Unlike multisig bridges, Snowbridge verifies Ethereum consensus directly on Polkadot.
• Core ecosystem infrastructure: Projects like Hydration and NeuroWeb rely on Snowbridge for Ethereum liquidity.

Team

This proposal covers the scope of 2 full-time equivalent engineers (FTE). The core team commits to ensuring that two team members are allocated to the project at all times, regardless of the individual availability of specific team members.

Operations and Maintenance

Since software continuously evolves, ensuring Snowbridge continues to run securely and smoothly is by no means a passive task. Our team works on maintaining Snowbridge every day by investigating security reports logged through our bug bounty, ensuring our off-chain components are compliant with on-chain changes, such as updating our relayers and indexers when runtime upgrades occur. Our team is always on call for potential issues with transfers or user support.

Success metric: Snowbridge continues to run as a high availability and secure service.

Ethereum Hardforks

As part of Snowbridge’s trustless architecture, the Ethereum light client on BridgeHub needs to be compliant with the Ethereum consensus spec. About twice a year, Ethereum undergoes hardforks that changes the format of consensus updates. Our team needs to be proactive and update:

• Update the on-chain Ethereum light client, generate real test data and write tests
• Update relayers and verify proof generation and verification
• Update local end-to-end scripts to use the new consensus client (Lodestar node)
• Update Westend relayers and our self-hosted Lodestar Sepolia node, coordinating the Westend upgrade in time to test the switchover on Sepolia before mainnet
• Coordinate with Ethereum core dev PMs on mainnet fork timing to ensure sufficient lead time for a governance proposal
• Prepare and test the runtime upgrade release (including Chopsticks testing) in time for the hardfork
• Upgrade our Lodestar node to the required version before the fork

Ethereum’s latest upcoming hardfork, Gloas, is expected to enact within the next 6 months. Heze is expected before end of this proposal, between H2 2026 and H1 2027.

Bridge Support

The reason will monitor bridge availability during office hours, ensure relayers are running and providing consensus updates in a regular cadence.

Runtime Upgrades

Since Snowbridge is deployed on BridgeHub and AssetHub, runtime upgrades affect our off-chain infrastructure, and requires our team to update chain metadata in our indexer, gas estimator and sometimes UI and relayers.

Bug Bounty

The bug bounty fund is addressed in a separate proposal.

Past Year in Review

For a detailed review of the past year’s work, see Year In Review 2025/2026.

Cost Breakdown

The total ask is $364,200 covering the period from May 2026 to April 2027.

Engineering: $250,000

The two developers handle all ongoing Snowbridge development and maintenance work. The technical lead reviewer is our main Solidity expert, providing architecture oversight, code review and internal security audits over any Solidity changes.

Scope of Work

Estimated Hours Breakdown

Core Infrastructure: $64,200

Our team has done significant operational cost cutting over the past year, eliminating or self-hosting services that were previously paid for. We remove third party dependencies where we could and moved to self-hosting, to save on costs. We’re also only asking the treasury to cover infrastructure related to core bridge operations and consensus - not off-chain products, message relayers, frontend nor ancillary services.

Total core infrastructure costs are $64,200 annually.

Infrastructure

Summary

Payment Structure

Our budget has been kept minimal, focused on core bridge infrastructure, consensus costs and engineering costs that are far below market rates. In order to remain competitive, it’s important for our staff and business to have security for our runway, and so we’re asking for a single up front payment covering the year’s runway of $364,200.

ℹ️ Please view the counterpart proposals:

• Polkadot proposal live at referendum #1879
• Kusama proposal live at referendum #646

Summary

This proposal is for the global deployment of a progressively decentralized archive RPC network for the Paseo testnet and its system parachains. Please view the detailed forum post for the complete background of the initial deployment for Polkadot Asset Hub and Coretime.

DeServe is:

• Global RPC infrastructure - 14 locations, widest coverage
• Geo-steered load balancing
• Lowest latency among all major Polkadot RPC providers
• By a Polkadot-native infrastructure & software builder, ex-IBP Rank-6 member
• Path to on-chain, general-purpose infrastructure (DePIN)
• Launched on March 31st, 2026 as a single-chain deployment, >53M req/24h by day 10
• Testnet live on Paseo, para id 5150 (telemetry), proof of on-chain commitment, currently running a shell runtime with business logic upgrade planned
• 80% cheaper than IBP
• Webpage live at deserve.network
• Developer documentation: docs.deserve.network

This proposal requests $11,719.00 as the first payment, half of the first three months, to bootstrap the global rollout of all Paseo services. Subsequent payments will be requested via 3-monthly retroactive proposals, alongside full transparency reports covering expenses, performance, and request analytics.

Initial Traction & Updates

The following X posts document DeServe's first days of deployment:

• Launch announcement for Polkadot Asset Hub (post)
• >1.7M requests on day 1, Ethereum-compatible RPC deployment (post)
• >45M requests/24h, deserve.network launch (post)
• >50M requests/24h, docs.deserve.network launch (post)
• >53M requests/24h, Polkadot Coretime rollout and public dashboard launch (post)

Over the first two weeks of deployment, DeServe has served over 500 million requests, and is currently serving >36M requests/day.

Live request analytics are available at the public dashboard.

Deployment & Coverage

Complete Paseo rollout under this proposal

• Paseo Relay Chain
• Asset Hub
• Bridge Hub
• Collectives
• Coretime
• People

Infrastructure

• 14 locations across 6 continents, 7 providers including Helikon
  • Atlanta, GA, US
  • Gravelines, FR
  • İstanbul, TR
  • Johannesburg, ZA
  • Limburg, DE
  • London, UK
  • Miami, FL, US
  • Montreal, CA
  • Mumbai, IN
  • Seattle, WA, US
  • Sao Paulo, BR
  • Singapore, SG
  • Sydney, AU
  • Warsaw, PL
• 1G–10G uplink bandwidth
• Unmetered traffic on most nodes
• 950GB–14.72TB NVMe storage per node
• ECC RAM

Monitoring and High Availability

• Geo-steered load balancing: requests routed to the nearest node
• 15-second health checks: unreachable nodes removed from the pool
• Quick recovery from low-cost backup storage preferred over 2N redundancy for cost-efficiency
• Prometheus & Grafana monitoring and alerting across all nodes 24/7
• Monitoring network (in development): latency checks across the globe
• 99.9%+ effective availability through rapid failover
• Open-source DNS transition planned (see Roadmap)

RPC configuration

• 100 req/s without API key
• 2MB max request size / 7MB max response size
• 256 RPC subscriptions per connection

Performance

DeServe delivers the lowest latency among all major Polkadot RPC providers, verified via Compare Nodes, a global RPC performance inspector.

Full benchmark runs:

• DeServe vs IBP: Run 1, Run 2, Run 3
• DeServe vs OnFinality: Run 1
• DeServe vs LuckyFriday: Run 1
• DeServe vs Dwellir: Run 1

Cost Comparison

IBP is currently the only other provider offering a global geo-steered RPC service, making it the most appropriate reference for cost comparison.

Note that IBP operates on a 2N redundancy model, while DeServe operates on a single-instance model with rapid failover through backups, as detailed in the Monitoring & High Availability section.

Given the current cost constraints of the Polkadot ecosystem, we find that single instance per location with backup mechanisms in place should be sufficient under a highly responsive load-balancing system. DeServe’s current setup monitors endpoints every 15 seconds, immediately removing any unreachable endpoint from the pool.

IBP costs for Paseo are taken from the same billing view as the Polkadot and Kusama figures.

Our cost model is illustrated in detail in the initial forum post. DeServe also provides GeoDNS services for free as part of the package, whereas IBP charges $1,200.00/month for this service. DeServe also comes without curator payments, which add further overhead to bounty-based programs. IBP curator payments add approximately $3,400.00/month in additional overhead (reference).

Operation & Payment Details

Payment model

• First payment $11,719.00: half of the first three months ($7,813.00 × 3 × 0.5), requested upfront to bootstrap the global rollout
• Second payment $11,720.00: remaining half of the first three months, requested at the end of month 3 alongside the first transparency and performance report
• Subsequent payments $23,439.00/quarter: 3-monthly retroactive proposals alongside full transparency reports

Payment terms

• Stable or native coin (USDT, USDC, or DOT): first proposal submitted in USDT given current DOT valuations
• No lock-in: the treasury can cancel anytime
• Via regular spends: no long-term bounty top-ups or commitment
• Monthly transparency reports: expenses, performance, and request analytics
• Public monitors: service health and performance, live at public dashboard
• 99.9%+ uptime SLA: basis for payment validation

Labour costs

Labour costs for the current alpha phase are excluded from this proposal and covered by Helikon. As DeServe matures, operator labour costs will be standardized through protocol governance.

Roadmap

First 3 Months

• All Paseo services live within week 2 of proposal approval: Paseo Relay Chain, Asset Hub, Bridge Hub, Collectives, Coretime, People
• Monitoring network: real-time latency and health checks across all regions
• DeServe website: live node map, performance data, endpoints, and developer documentation (live at deserve.network)
• Open-source DNS: replacing Cloudflare for geo-steered load balancing, integrated with the monitoring network
• Polkadot-native provider onboarding: begin replacing cloud providers with native Polkadot infrastructure providers, onboarding criteria to be published
• Governance alpha phase: managed and governed by Helikon
• DeServe Unpaper: protocol design and vision document

First 6 Months

• Complete Polkadot-native operator onboarding
• Governance beta phase: network committee of ≥3 native operators
• On-chain service provision: on-chain payments, proofs, and governance, built on Polkadot

Submerge Commitment

Submerge is a data and compliance platform for Polkadot SDK chains, currently in development by Helikon. Submerge has received treasury funding and is behind schedule. Its two main components, Crystal (a chain indexer), Mycelium (a cross-chain indexer), along with their APIs for all supported chains will be delivered before any further on-chain submission for DeServe.

About Helikon

Helikon is a Polkadot-native infrastructure and software development collective based in İstanbul. A regular contributor to the Polkadot ecosystem at both the development and governance levels since late 2020:

• 5 active Kusama & Polkadot validators, former 1KV & Decentralized Nodes member
• Rank-6 ex-IBP member: infrastructure services for 26 blockchains
• Two-time Decentralized Voices delegate, once as founder of Permanence DAO
• Recently saved and revived Multix (post 1, post 2, post 3), a >$500K investment funded through Polkadot treasury proposal #236 and referendum #120, and child bounties 36_10 and 36_3054.
• Maintaining SubVT (iOS & Telegram Kusama/Polkadot), Chain Console, Chainviz/alpha, followthedot
• Built dv.report - analysis dashboard for the Decentralized Voices program cohorts 4 and 5
• Developing Submerge - data & compliance platform for Polkadot SDK chains

Contact

• info@helikon.io
• @helikonlabs
• @kukabi_
• Helikon GitHub
• kukabi GitHub
• Forum

ℹ️ Please view the counterpart proposals:

• Kusama proposal live at referendum #646
• Paseo proposal live at referendum #1880

Summary

This proposal is for the global deployment of a progressively decentralized archive RPC network for Polkadot and its system parachains. Please view the detailed forum post for the complete background of the initial deployment.

DeServe is:

• Global RPC infrastructure - 14 locations, widest coverage
• Geo-steered load balancing
• Lowest latency among all major Polkadot RPC providers
• By a Polkadot-native infrastructure & software builder, ex-IBP Rank-6 member
• Path to on-chain, general-purpose infrastructure (DePIN)
• Launched on March 31st, 2026 as a single-chain deployment, >53M req/24h by day 10
• Testnet live on Paseo, para id 5150 (telemetry), proof of on-chain commitment, currently running a shell runtime with business logic upgrade planned
• 80% cheaper than IBP
• Webpage live at deserve.network
• Developer documentation: docs.deserve.network

This proposal requests $24,112.00 as the first payment, half of the first three months, to bootstrap the global rollout of all Polkadot services. Subsequent payments will be requested via 3-monthly retroactive proposals, alongside full transparency reports covering expenses, performance, and request analytics.

Initial Traction & Updates

The following X posts document DeServe's first days of deployment:

• Launch announcement for Polkadot Asset Hub (post)
• >1.7M requests on day 1, Ethereum-compatible RPC deployment (post)
• >45M requests/24h, deserve.network launch (post)
• >50M requests/24h, docs.deserve.network launch (post)
• >53M requests/24h, Polkadot Coretime rollout and public dashboard launch (post)

Over the first two weeks of deployment, DeServe has served over 500 million requests, and is currently serving >36M requests/day.

Live request analytics are available at the public dashboard.

Deployment & Coverage

Current deployment

• Polkadot Asset Hub Archive RPC & Ethereum-compatible RPC (endpoints)
• Polkadot Coretime Archive RPC (endpoints)

Complete Polkadot rollout under this proposal

• Polkadot Relay Chain
• Bridge Hub
• Collectives
• People

Infrastructure

• 14 locations across 6 continents, 7 providers including Helikon
  • Atlanta, GA, US
  • Gravelines, FR
  • İstanbul, TR
  • Johannesburg, ZA
  • Limburg, DE
  • London, UK
  • Miami, FL, US
  • Montreal, CA
  • Mumbai, IN
  • Seattle, WA, US
  • Sao Paulo, BR
  • Singapore, SG
  • Sydney, AU
  • Warsaw, PL
• 1G–10G uplink bandwidth
• Unmetered traffic on most nodes
• 950GB–14.72TB NVMe storage per node
• ECC RAM

Monitoring and High Availability

• Geo-steered load balancing: requests routed to the nearest node
• 15-second health checks: unreachable nodes removed from the pool
• Quick recovery from low-cost backup storage preferred over 2N redundancy for cost-efficiency
• Prometheus & Grafana monitoring and alerting across all nodes 24/7
• Monitoring network (in development): latency checks across the globe
• 99.9%+ effective availability through rapid failover
• Open-source DNS transition planned (see Roadmap)

RPC configuration

• 100 req/s without API key
• 2MB max request size / 7MB max response size
• 256 RPC subscriptions per connection

Performance

DeServe delivers the lowest latency among all major Polkadot RPC providers, verified via Compare Nodes, a global RPC performance inspector.

Full benchmark runs:

• DeServe vs IBP: Run 1, Run 2, Run 3
• DeServe vs OnFinality: Run 1
• DeServe vs LuckyFriday: Run 1
• DeServe vs Dwellir: Run 1

Cost Comparison

IBP is currently the only other provider offering a global geo-steered RPC service, making it the most appropriate reference for cost comparison.

Note that IBP operates on a 2N redundancy model, while DeServe operates on a single-instance model with rapid failover through backups, as detailed in the Monitoring & High Availability section.

Given the current cost constraints of the Polkadot ecosystem, we find that single instance per location with backup mechanisms in place should be sufficient under a highly responsive load-balancing system. DeServe’s current setup monitors endpoints every 15 seconds, immediately removing any unreachable endpoint from the pool.

The compared numbers below are taken from IBP dashboard billing view.

Our cost model is illustrated in detail in the initial forum post. DeServe also provides GeoDNS services for free as part of the package, whereas IBP charges $1,200.00/month for this service. DeServe also comes without curator payments, which add further overhead to bounty-based programs. IBP curator payments add approximately $3,400.00/month in additional overhead (reference).

Operation & Payment Details

Payment model

• First payment $24,112.00: half of the first three months ($16,075.00 × 3 × 0.5), requested upfront to bootstrap the global rollout
• Second payment $24,113.00: remaining half of the first three months, requested at the end of month 3 alongside the first transparency and performance report
• Subsequent payments $48,225.00/quarter: 3-monthly retroactive proposals alongside full transparency reports

Payment terms

• Stable or native coin (USDT, USDC, or DOT): first proposal submitted in USDT given current DOT valuations
• No lock-in: the treasury can cancel anytime
• Via regular spends: no long-term bounty top-ups or commitment
• Monthly transparency reports: expenses, performance, and request analytics
• Public monitors: service health and performance, live at public dashboard
• 99.9%+ uptime SLA: basis for payment validation

Labour costs

Labour costs for the current alpha phase are excluded from this proposal and covered by Helikon. As DeServe matures, operator labour costs will be standardized through protocol governance.

Roadmap

First 3 Months

• All remaining services live within week 2 of proposal approval: Polkadot Relay Chain, Bridge Hub, Collectives, People
• Monitoring network: real-time latency and health checks across all regions
• DeServe website: live node map, performance data, endpoints, and developer documentation (live at deserve.network)
• Open-source DNS: replacing Cloudflare for geo-steered load balancing, integrated with the monitoring network
• Polkadot-native provider onboarding: begin replacing cloud providers with native Polkadot infrastructure providers, onboarding criteria to be published
• Governance alpha phase: managed and governed by Helikon
• DeServe Unpaper: protocol design and vision document

First 6 Months

• Complete Polkadot-native operator onboarding
• Governance beta phase: network committee of ≥3 native operators
• On-chain service provision: on-chain payments, proofs, and governance, built on Polkadot

Submerge Commitment

Submerge is a data and compliance platform for Polkadot SDK chains, currently in development by Helikon. Submerge has received treasury funding and is behind schedule. Its two main components, Crystal (a chain indexer), Mycelium (a cross-chain indexer), along with their APIs for all supported chains will be delivered before any further on-chain submission for DeServe.

About Helikon

Helikon is a Polkadot-native infrastructure and software development collective based in İstanbul. A regular contributor to the Polkadot ecosystem at both the development and governance levels since late 2020:

• 5 active Kusama & Polkadot validators, former 1KV & Decentralized Nodes member
• Rank-6 ex-IBP member: infrastructure services for 26 blockchains
• Two-time Decentralized Voices delegate, once as founder of Permanence DAO
• Recently saved and revived Multix (post 1, post 2, post 3), a >$500K investment funded through Polkadot treasury proposal #236 and referendum #120, and child bounties 36_10 and 36_3054.
• Maintaining SubVT (iOS & Telegram Kusama/Polkadot), Chain Console, Chainviz/alpha, followthedot
• Built dv.report - analysis dashboard for the Decentralized Voices program cohorts 4 and 5
• Developing Submerge - data & compliance platform for Polkadot SDK chains

Contact

• info@helikon.io
• @helikonlabs
• @kukabi_
• Helikon GitHub
• kukabi GitHub
• Forum

This referendum (1878) contains a technical error in the call data and will fail to execute even if it passes voting. The metadata field references an off-chain computed hash with no corresponding on-chain preimage, which causes a PreimageNotExist runtime error on execution.

A corrected referendum has been submitted: Referendum 1885

1. Overview

1.1 Proposal Details

1.2 Project Summary

LunoKit aims to build a customizable UI theme and developer-friendly Web3 account connection infrastructure for the Polkadot ecosystem. Previously, we received a grant from the Web3 Foundation and completed the delivery of all milestones within three months. It unifies wallet connection state management, account abstraction, chain switching, and session recovery, while also providing a rich set of UI components and multi-chain account support, greatly reducing the integration threshold for DApps built on Polkadot SDK chains.

As a frontend development library based on React + TypeScript, LunoKit also provides over 20 Hooks, including account state management, chain switching, connection control, and on-chain data subscription, with support for data caching. Developers can focus on core business logic while LunoKit handles the account module.

LunoKit’s capabilities span three layers:

1. Connection & account fundamentals: multi-wallet connectivity, unified connection state management, a unified signer interface, and network/chain configuration and switching (covering both Polkadot SDK chains and EVM/PVM chains).

2. Developer interfaces (Hooks): 20+ composable Hooks covering connection control, account state, chain switching, and selected on-chain subscription and caching capabilities.

3. Ready-to-integrate UI components: components such as Connect Button, Account Panel, and Network Switcher, with support for theme tokens and branding configuration (appInfo) to help ecosystem projects maintain consistent UI.

Its modular architecture is composed of three packages:

• @luno-kit/core: connectors, chain configuration, account management, and a unified signer interface

• @luno-kit/react: the React integration layer and Hooks

• @luno-kit/ui: UI components, theming system, and branding configuration (appInfo)

1.2 Why LunoKit is needed

In any blockchain ecosystem, account connection is foundational entry-layer infrastructure for every dApp: users must connect a wallet and sign before they can stake, swap, participate in governance, and more. The quality of this entry layer directly impacts ecosystem-wide usability, consistency of user experience, and developer onboarding cost.

Today, the ecosystem commonly faces the following practical challenges:

• Reinventing the wheel and hidden costs: multi-wallet compatibility, connection state management, network switching, and session recovery are highly repetitive across projects, with development and maintenance costs fragmented across teams.
• Compatibility and regression burden: as wallet ecosystems evolve continuously, behavioral differences and edge cases (disconnects, network changes, permission updates, etc.) keep introducing regression-testing overhead, creating significant long-term maintenance pressure.
• Fragmented experience: inconsistent implementations of connection flows, network switching, error handling, and session recovery across dApps reduce predictability for users when moving between apps, which in turn hurts the overall experience and confidence.
• Delivery efficiency for new teams: for hackathons and early-stage teams operating on short timelines, repeatedly implementing the entry layer adds extra development and regression workload, increasing costs and extending delivery cycles.

LunoKit is positioned as an open-source, reusable, configurable, and long-term maintainable connection infrastructure layer. It helps ecosystem projects reduce repetitive work, improve consistency, and focus more of their resources on business innovation and the product itself.

In addition, we have set our 2026 roadmap to focus on EVM account support: enabling dApps to integrate Substrate accounts and EVM accounts within a single, unified connection module through LunoKit—reducing the cost of implementing and maintaining two separate sets of connection logic and UI/state systems in multi-account environments. As more Solidity-based dApps emerge within the Polkadot ecosystem, demand for “dual-account / multi-account login” is expected to grow further. This model has already been validated in practice (for example, some dApps within Bifrost and Hydration support both account types). LunoKit aims to standardize and componentize these capabilities to reduce repetitive development effort across the ecosystem.

1.3 Ecosystem Adoption

The following list is not exhaustive; it only includes some representative online product integration cases that are still in continuous operation.

2. Team

Lunolab is composed of two core members with extensive blockchain development backgrounds. Since joining the ChainX team in 2020, they have been active in the Web3 field, participating in the incubation and development of multiple public chains and application projects.

Cris has over 5 years of Web3 product experience, focusing on cross-chain protocol design and user experience optimization. He led the product design of ChainX, worked as a product manager responsible for OmniBTC’s frontend product design and project management, and from 2023–2025 served as the product lead of BEVM/GEB, overseeing chain-level functionality design and developer tool planning.

Brain is a senior blockchain frontend developer. He joined the ChainX frontend team in 2020, began leading the frontend system development of OmniBTC in 2022 (including OmniSwap and OmniLending), and from 2023–2025 was fully responsible for the frontend architecture of BEVM/GEB, covering explorer, wallet, and developer tools, accumulating deep experience in blockchain frontend development.

• 2020 – ChainX Team
• June 2022 – OmniBTC (incubated within ChainX, now closed, social media X)
  OmniBTC was a cross-chain DeFi platform that included two core products:
  • OmniSwap: A cross-chain trading aggregator supporting 40+ public chains and 20+ cross-chain bridges, with a cumulative trading volume exceeding $2 billion.
  • OmniLending: A cross-chain lending platform with peak TVL of over $10 million.
• June 2023 – June 2025, BEVM (incubated within ChainX, later renamed GEB)
  BEVM was a public chain developed with the Substrate technology stack, aiming to be a Bitcoin Layer 2 compatible with EVM smart contracts, with over 990,000 on-chain addresses.

3. Work Completed

After completing all milestones of the Web3 Foundation Web3 Grant, Lunokit continued ongoing development and maintenance of the product based on real production integration needs and ecosystem feedback, resulting in a set of additional deliverables that have been completed and can be publicly verified. This section is intended to fully list the scope and evidence trail of this “completed work,” making it easy for the community to directly verify the actual output.

3.1 Work Completed Deliverables

Verification

• Public code verification: all PR commit histories above are publicly accessible and reviewable.

• Functional verification: Docs / examples / live demo can be used to validate connection flows, component previews, theming configuration, and integration-ready code export.

• Ecosystem usage verification: production integrations can be validated via the listed live applications (e.g., Snowbridge, Potatao, etc.).

3.2 Retroactive Budget & Cost Breakdown

This section covers only the work listed in the “Work Completed Deliverables” roadmap section (PR-based evidence). To align with OpenGov’s milestone-oriented funding approach and to reduce immediate treasury outflow, we structure the retroactive request as a partial reimbursement by applying a conservative, discounted hourly rate to the already completed and publicly verifiable work.

Budget Summary (Labor)

Rationale

• The work covered here is already completed and publicly verifiable (PR-based evidence, demos, and integrations).

• We are intentionally requesting reimbursement at 30 USD/hour, which is below typical market rates for senior Web3 engineering and product/UI work, to keep the proposal cost-effective and aligned with milestone-oriented funding expectations.

3. Development Roadmap

We will deliver LunoKit’s heterogeneous-chain support (Polkadot SDK + EVM) and other content through monthly milestones from April to September 2026. Each milestone has clear scope, measurable success criteria, and public verification anchors (PRs/commits, release tags, docs, examples, and demo updates).

3.1 Milestone 1 — April 2026 (Core Foundations)

Objective: Introduce a robust type system and configuration layer in @luno-kit/core to support both Substrate and EVM chains under a unified connection model while maintaining strict type safety.

Success Criteria

• @luno-kit/core can automatically detect configuration and load the corresponding heterogeneous connector instances.
• When calling createConfig, IDE autocomplete and compile-time inference correctly narrow types based on chainType (Substrate vs EVM).
• Developers can integrate Polkadot Vault into their dapp by modifying a few lines of code in the configuration file.

Public Deliverables / Verification Anchors (published upon milestone completion)

• Core API type definitions documenting the complete multi-track type system.

• createConfig implementation in packages/core (core initialization logic).

• A versioned release tag (or release notes) and the PR/commit list covering Milestone 1 scope.

3.2 Milestone 2 — May 2026 (React State Pipeline + Hooks Namespace Support)

Objective: Establish a bi-directional state synchronization pipeline and upgrade core hooks to support a namespace parameter with compile-time type narrowing and safe behavior across heterogeneous environments.

Success Criteria

• 15+ core hooks support namespace with strict type narrowing, enabling seamless switching between ecosystems.

• Substrate-only hooks degrade gracefully in EVM mode (no runtime errors).

Public Deliverables / Verification Anchors (published upon milestone completion)

• Updated @luno-kit/react implementation with namespace-aware hooks and overload-based type narrowing.

• A versioned release tag (or release notes) and the PR/commit list covering Milestone 2 scope.

• Docs updates describing the namespace model and recommended usage patterns.

3.3 Milestone 3 — June 2026 (UI heterogeneous-Chain Adaptation)

Objective: Upgrade UI components to handle dual ecosystems cleanly, improve guidance when both Substrate and EVM connectors coexist, and implement reliable activeNamespace restoration behavior.

Design Reference

Figma: https://www.figma.com/design/NRI1vLxg6qquNNdXmSxhlv/Lumo-Connect-v0.2.0?node-id=4001-2&p=f&t=CluGbjfRWkN6b0s1-0

Success Criteria

• UI adapts automatically based on activeNamespace, including icons, address format (SS58 vs 0x), and ecosystem visual indicators.

• When both ecosystems are available, users can reliably discover, select, and switch between Substrate and EVM wallet contexts without confusion.

• After page refresh, dual-session restoration behaves correctly and activeNamespace fallback logic prevents “stuck” states.

• The Manage Wallets component matches the linked Figma design and supports the expected dual-ecosystem management flows.

• Scrollable lists (wallets/network/addresses) render with a smooth edge-fade/scroll mask effect and maintain performance.

• Mobile layouts are optimized (touch-friendly sizing, spacing, and modal behavior) without regressions on desktop.

• New theming tokens (including connect text color) are available and reflected in the demo/configuration flows.

Public Deliverables / Verification Anchors (published upon milestone completion)

• Updated @luno-kit/ui package implementing heterogeneous-chain adaptations for ConnectButton, ConnectModal, ChainModal, plus the new Manage Wallets component.

• Demo updates showcasing dual-ecosystem UI flows (including Manage Wallets) aligned with the Figma design reference.

• A versioned release tag (or release notes) and the PR/commit list covering Milestone 3 scope.

• Demo updates showcasing: mobile refinements, new theme tokens, scroll mask effect, and Ledger multi-account selection UI (published upon milestone completion).

3.4 Milestone 4 — July 2026 (Unified Transaction & Signature Facade)

Objective: Provide a unified transaction and signing interface in React that supports both ecosystems while preserving access to underlying native status/details (Viem vs Dedot).

Success Criteria

• Developers can send transactions via a unified interface and receive both LunoKit-mapped status and the raw native (Viem/Dedot) status/data.

• AccountDetailsModal and related components correctly display heterogeneous addresses without formatting errors.

• Users can use any of the supported EVM wallets to send transactions.

Public Deliverables / Verification Anchors (published upon milestone completion)

• Unified transaction model/schema with raw-state passthrough.

• Updated React hooks (useSendTransaction, useSignMessage) and supporting types.

• A versioned release tag (or release notes) and the PR/commit list covering Milestone 4 scope.

• Demo/docs updates demonstrating unified transaction/signing usage.

3.5 Milestone 5 — August 2026 (Testing & CI Quality Gates)

Objective: Add comprehensive automated testing for core paths across Core and React hooks, ensuring stability for connect/switch/transaction flows in both ecosystems.

Success Criteria

• CI passes for the full test suite; core paths (connect/switch/tx) are covered.

• Transaction lifecycle states (signature → confirmation) behave consistently across both ecosystems.

• Coverage targets: Core ≥ 90%, React hooks core-path coverage ≥ 80%.

• When connecting a Substrate account using Ledger, you can choose which account to import.

Public Deliverables / Verification Anchors (published upon milestone completion)

• Automated test suite source code (unit + integration tests) and CI configuration updates.

• A versioned release tag (or release notes) and the PR/commit list covering Milestone 5 scope.

• A test results summary (e.g., CI artifact link or published report) demonstrating pass status and coverage metrics.

3.6 Milestone 6 — September 2026 (Reference DApp + Docs + v0.2 Release)

Objective: Deliver a flagship integrated demo dApp, improve edge-case stability in real browsers, publish complete documentation and migration guides, and ship LunoKit v0.2

Success Criteria

• A one-command runnable heterogeneous-chain demo site is available, showcasing dual-ecosystem transaction flows.

• Official docs cover all new APIs and heterogeneous-chain integration scenarios.

• The official Live Demo is updated to support and showcase the EVM-related features introduced in v0.2 .

Public Deliverables / Verification Anchors (published upon milestone completion)

• LunoKit v0.2 release across Core, React, and UI packages.

• example/integrated-dapp and a new publicly accessible live demo site.

• Updated developer documentation and migration guide.

• A versioned release tag (or release notes) and the PR/commit list covering Milestone 6 scope.

3.7 Budget Breakdown

Team Costs

Operational Costs

Total Requested Funding

Milestone Distribution:

• Milestone 1 (April 2026): $8,450
• Milestone 2 (May 2026): $8,450
• Milestone 3 (June 2026): $8,450
• Milestone 4 (July 2026): $8,450
• Milestone 5 (August 2026): $8,450
• Milestone 6 (September 2026): $8,450

3.8 Milestone scope note：

While the milestone plan describes the deliverables we commit to for funding and verification, we also

expect to ship additional fixes and features beyond the proposal in response to real developer needs and production integration feedback within the ecosystem. We will keep the community informed and ensure the committed milestone deliverables remain the priority.

This referendum formally closes the Polkadot Fast Grants and Open Source Developer Grants bounty programs following the completion of their defined scope and boundary conditions.

All outstanding obligations, pending evaluations, and eligible payouts have been resolved or terminated in accordance with the bounty rules and governance framework. Any remaining unallocated or unused funds are to be returned to the Polkadot Treasury.