Summary

This proposal requests the deployment of the Universal Deterministic Deployment Proxy (CREATE2 factory) at canonical address 0x4e59b44847b379578588920ca78fbf26c0b4956c on Polkadot Asset Hub mainnet.

Problem Statement

The CREATE2 deterministic deployment proxy is critical infrastructure for Ethereum-compatible chains, enabling protocols like Uniswap, Safe, and others to deploy contracts at the same addresses across all EVM chains. However, it cannot be deployed on Asset Hub through normal means due to a gas price incompatibility.

Technical Details:

The way to deploy this contract on a new chain is to submit a well-known presigned tx,
the tx includes a high gas price of 100 gwei but it's still not high enough to work on Asset Hub

• The proxy's deployment uses a pre-signed transaction with a hardcoded gas price of 100 gwei
• Polkadot Asset Hub enforces a minimum gas price of 1000 gwei (10x higher)
• The transaction signature cryptographically commits to all parameters including gas price
• Modifying the gas price of the presigned transaction would result in different contract/deployer addresses, defeating the purpose of universal deterministic deployment

Proposed Solution

Use OpenGov to execute a privileged utility_dispatchAs using the canonical create2 proxy deployer address 0x3fab184622dc19b6109349b94811493bf2a45362 as the origin of this call. The polkadot-sdk equivalent of this address is 12SUqsDfLk4k5LS7XWi6fC3jC5xeT8sFivVY776NGm26dXr4. The call executes instantiate_with_code on pallet-revive instantiating the CREATE2 proxy contract and ensuring we maintain the deterministic deployment address 0x4e59b44847b379578588920ca78fbf26c0b4956c.

• This call been successfully executed on paseo asset hub : https://assethub-paseo.subscan.io/extrinsic/4724501-2

Precedent

This approach has been successfully tested on Paseo Assethub using sudo privileges, confirming:

• The contract deploys to the correct canonical address 0x4e59b44847b379578588920ca78fbf26c0b4956c
• The CREATE2 mechanics work correctly in pallet-revive
• See: https://polkadot.testnet.routescan.io/address/0x4e59b44847b379578588920ca78fbf26c0b4956c

Benefits

• Protocol Compatibility: Enables Uniswap, Safe, and other major protocols to deploy at their canonical addresses on Asset Hub
• Cross-Chain Address Parity: Contracts can maintain the same addresses across Ethereum, L2s, and Polkadot
• Developer Experience: Standard tooling (Foundry, Hardhat plugins) will work as expected
• Ecosystem Growth: Removes a critical blocker for EVM developers building on Polkadot

Impact

• No Risk: This is a well-tested, standard contract deployed on hundreds of EVM chains
• One-Time Action: Once deployed, no further governance intervention needed
• High Value: Unblocks an entire class of protocol deployments and developer tooling

References

• Issue: https://github.com/paritytech/contract-issues/issues/263
• Deterministic Deployment Proxy: https://github.com/Arachnid/deterministic-deployment-proxy
• EIP-1014 (CREATE2): https://eips.ethereum.org/EIPS/eip-1014

OpenSquare has been actively developing products to improve the usability of polkadot. Our products includes subsquare, statescan, dotreasury and off-chain voting. We are writting this proposal to seek support to our work in 2026. The funding will cover infrastructure cost, daily maintenance work and new features development.

Infrastructures

• We are using some services to support the business.

• Domains: we are using 4 domains for the products.

Daily maintenance

We are maintaining 4 products(subsquare, statescan, dotreasury and off chain voting) and deploy them for over 20 chains with over 100 runing scripts. The maintenance work includes:

• Server deployment maintenance: daily server monitor, upgrading products versions, emergency handling, etc.
• Codebase maintenance: code refactor, bug fixes, performance enhancement, UI tweaks, dependency upgrading, etc.
• Answer user questions, collect user feedbacks and then design new features.
• Collaboration with other teams to provide api support and some governance explanation.

Features development

Subsquare OpenGov referenda related features

• User vote actioins
  Index all tally affected user actions and show them on the referendum detail page. These actions include vote, remove vote, change vote, delegate, change delete, undelegate. With this feature users can easily know how and when proposal tally is affected.
• Referendum curve chart enhancement
  • Add preparing stage data view into the curve chart, so users can see the whole lifecycle data.
  • Show voter actions on the curve chart popup and show their avatars on the curve chart, so users can see when and who affected the tally in a very visualized way.
  • Add a new curves tab under the post content to show curve and votes data.
• Add a new referenda template to support batch treasury spend, so users can create milestone based proposals on subsquare.
• Show referenda confirming and treasury request warnings on the overview page and referenda list page.
• Support post content translations.
  We now support Chinese, German and Russian translations. It will help non-native English spearkers better read a referendum.
• Support replying comments from polkassembly.
• Bind bounty info if a referendum is related with a bounty. We decode the call info and show bounty link on the referendum navigation bar.
• Remark style info enhancement if a referendum calls contain a system#remark call.

Treasury statistics on subsquare

• Write scripts to read and set price field to various proposals in DB.
• Calc funded value by addresses and show beneficiary rank on the new developed treasury status page.
• Show treasury assets panel and to be awarded panel on the new developed treasury status page.
• Mark treasury funded project info, category and bind proposals to projects. Then we developed a treasury projects page to show all category based project funded info.
• Mark and show tags to beneficiary address.
• Add treasury burn page to show treasury burn records and some statistics data like how much is burnt in total.
• Redesign and develop summary components on treasury spends, proposals, bounties and child bounties list page. So we can see statistics data about various treasury proposals, like total amounts, active amounts, etc.

Decentralized voices support on subsquare

Decentralized voices program plays an important role in the polkadot governance process.

• All cohorts and related info are listed on a page.
• We develop a panel to show DV delegates vote amount statistics and participation, win rates data.
• We develop a heat map to show DV delegates vote details.
• We list all referenda and show whether they are affected by DV votes.

Pages can be checked here.

Intime data for subsquare

We index finalized blocks for on chain data mainly to extract various business, but this may cause some delay with the latest on chain data. We developed a intime scan package to index the latest data which includes votes, preimages and proxies.

These indexed in time data will be served through a graphql API and fronted pages will show them.

Multisig enhancement on subsquare

• Support users to add or import a multisig address.
• Support users to create a multisig call on behalf of the created multisig address. There are multisig call templates for users to quick composing a multisig call.

Foreign assets support

• As an user, I can see all my foreign assets and transfer my foreign assets to others.
• As an user, I can see all my foreign asset transfer records.
• As an user, I can see all on-chain foreign assets.

New info on subsquare profile page

• We will show treasury beneficiary info on the profile page, so users can see how much fund an address got from the treasury.
• Show assets info. These assets includes native assets and foreign assets in assethub, total balance value on hydration.
• Vesting info of an address including total/locked/unlockable vesting balance and schedule details.

Vesting features enhancement on subsquare

• Aggregate vesting info by addresses and show all schedules of an address with locked vesting balance.
• Support users to unlock vesting balances.
• Support users to create a vested_transfer.

Others development on subsquare

• Support users to connect their address with polkadot vault and sign extrinsics.
• Develope a page to show all scheduler tasks here.
• Develope a page to show all whitelist calls here.
• Support teleporting assets support between system para chains.
• Show gas and nonce as advanced info on signing popup.
• As an user, I want to know how much is paid to curators in a bounty.
• As an user, I want to know treasury yearly spend.

Dotreasury development

• Show multi assets for polkadot treasury.
• Remove dotreasury server and the fronted will fully rely on the subsquare API for fronted data.
• Develop a new price query on dotreasury graphql API and subsquare will use it for related price calculation.

Statescan development

Staking features including reward data indexing, show staking rewards and nominations on account detail page and an all validators page. Related PR: #1084, #1133, #1136, #1137, #1152, #1155, #1156.

off-chain voting development

• Support collective voting. Users can create a space with dedicated members(addresses) and only members can vote a proposal.
• Anonymous support. We can set a voting space as anonymous, so users can see the vote result, but can't see who has voted the proposal.

Proposer: 12mP4sjCfKbDyMRAEyLpkeHeoYtS5USY4x34n9NMwQrcEyoh

Requested Amount: 278,256 USDT

Funding Period: 12 months (April 2026 – March 2027)

If you prefer to view it in a document, click here.

1. Proposal Summary

PolkaWorld is requesting 278,256 USDT to support Polkadot Chinese-language content and community operations over the next 12 months.

During the previous funding cycle, PolkaWorld consistently delivered articles, livestreams, interviews, educational short videos, WeChat video channel content, and bilingual (Chinese–English) social media distribution.

From April 2025 to February 2026, we completed:

• 270 articles, generating 307,587 total reads within the Chinese community (compared to 232,164 reported in the previous proposal)

• 64 livestreams

• 11 interviews

• 43 educational short videos, reaching 71,268 views (compared to 65,000 in the previous cycle)

• 155 videos published on the WeChat video channel, with 287,847 total views

• The English X account reached 3.8 million impressions over the past year (compared to 1.9M previously)

• The Chinese X account reached 1.3 million impressions over the past year (compared to 819.5K previously)

Please note that these delivery metrics do not yet include March 2026.

In the upcoming funding cycle, we plan to continue operating at the following monthly cadence:

• 24 articles per month

• 6 livestreams per month (4 in Chinese, 2 in English)

• 4 educational short videos per month

• 1 in-depth interview per month

• Ongoing management of PolkaWorld’s two X accounts

• Daily distribution of key Polkadot updates across Chinese community channels

As one of the most important markets in Web3, the Chinese-speaking community has long been a key strategic region where many ecosystems compete to build presence and engagement. Polkadot established strong roots in this market early on.

Although the current market is often driven by short-lived narratives, we firmly believe that in the long run, the market rewards products and protocols that remain committed to the core values of Web3.

Our role is to remain consistently present, continuously delivering Polkadot-related content and information to the Chinese-speaking community.

This proposal is not a new experimental initiative, but rather a continuation and refinement of an already established and proven workflow.

2. Why Is This Work Important?

Polkadot has long maintained a certain level of presence in the Chinese-speaking market. Sustaining this foundation requires not only timely updates about Polkadot’s ongoing developments, but also continuous communication that is accessible, contextualized, and easy to understand.

PolkaWorld’s work mainly focuses on three areas:

2.1 Providing a Consistent Information Gateway for the Chinese Community

A large portion of important Polkadot information first appears in English-speaking environments, including X, forums, GitHub, livestreams, and various ecosystem channels.

One of PolkaWorld’s core roles is to continuously track these developments and translate them into information that Chinese users can access and understand.

2.2 Providing Explanatory Content Around Key Developments

As the Polkadot ecosystem becomes increasingly complex, simple information translation is becoming less valuable. More and more important topics require explanation and interpretation, including developments such as JAM, DOT issuance reduction, Polkadot Hub, Dual-VM architecture, developer experience, interoperability, product direction, and the broader strategic shift toward Polkadot’s “Second Age.”

PolkaWorld’s role is not only to report what is happening, but also to help explain what these changes mean.

2.3 Serving as a Communication Bridge Between Chinese Users and the Broader Ecosystem

Through livestreams, interviews, social media, and community operations, PolkaWorld helps Chinese users better understand projects, builders, and key discussions within the ecosystem.

At the same time, it also helps bring the perspectives and concerns of the Chinese community back into the broader Polkadot conversation.

Long-term thinking has always been a core value of PolkaWorld. Our work is not a short-term marketing effort, but rather an ongoing effort to support communication and understanding across the ecosystem.

3. Significance and Impact

For the community, what matters is not only how much content PolkaWorld produces, but also what role this work actually plays within the ecosystem.

Based on our experience over the past several years, the value of PolkaWorld’s work is mainly reflected in the following areas.

3.1 Maintaining Polkadot’s Ongoing Visibility in the Chinese Information Environment

PolkaWorld’s content does not remain confined to its own channels. It often flows further into the broader Chinese information ecosystem.

In previous work, PolkaWorld articles have been reposted or cited by Chinese crypto media outlets such as WuShuo Blockchain, PANews, and Foresight News. One specific example occurred when Polkadot APAC planned to publish Polkadot-related content through Foresight News. Before doing so, the editorial team at Foresight News contacted PolkaWorld to better understand the current state of the ecosystem before deciding how to structure their coverage.

Similarly, community members have observed that some PolkaWorld content has been translated or referenced by the official information channels of exchanges such as Binance and Bitget, while Polkadot-related updates have also appeared on project update pages of exchanges like OKX and Binance. Even if part of this distribution may occur through platform aggregation or automated systems, it still indicates that the content produced by PolkaWorld has, to some extent, become one of the information sources about Polkadot within the Chinese market.

(Screenshot from OKX exchange)

(Screenshot from Binance exchange)

3.2 Establishing Stable Information Distribution and Community Reach Channels

Long-term and consistent content production does more than generate individual article or livestream metrics. Over time, it also forms stable communication channels, including:

• WeChat official accounts

• Private WeChat community networks

• Telegram groups

• Chinese and English X accounts

For Chinese users, these channels form a continuously updated Polkadot information network that can be accessed repeatedly. A single piece of content may not immediately lead to long-term engagement, but the existence of stable channels lowers the barrier for users to follow ecosystem developments over time.

3.3 Providing Contextual Understanding and Collaboration Capacity Built Over Time

PolkaWorld has been deeply involved in the Polkadot ecosystem for six years. The value created through long-term accumulation goes beyond higher content production efficiency. It also includes a deeper understanding of the ecosystem’s background, governance history, project relationships, and evolving narratives.

This accumulated experience allows PolkaWorld to explain ecosystem developments in a more accurate, rational, and contextualized way, rather than simply repeating surface-level information. This is particularly important when discussing complex topics such as governance decisions, technical upgrades, and strategic shifts.

In addition, long-term operations have also created practical collaboration capacity within the ecosystem. Although PolkaWorld does not primarily focus on offline events, it can still assist when quick coordination, partnership connections, or regional collaboration is required. For example, during the process in which Pala Labs proposed the JAM China Tour, PolkaWorld was able to help connect relevant partners and resources in a relatively short time.

3.4 The Public Value of This Work

From a proposal perspective, PolkaWorld’s work is not only about growing its own channels. Rather, it continuously maintains an information distribution node, an explanatory channel, and a community connection point around Polkadot within the Chinese market.

The value of this type of work may not always be fully captured by a single metric. However, it plays a sustained foundational role in helping the Chinese community understand ecosystem developments, follow key changes, discover important projects, and maintain long-term participation in the Polkadot ecosystem.

4. Past Deliverables

PolkaWorld is one of the few teams that reports deliverables to the community on a monthly basis. Over the past year, in addition to publishing monthly reports in the comment section of the original proposal #1522, we have also shared our work updates in the Polkadot Direction group and on X. If you are interested, you can follow the links provided to review the reports.

PolkaWorld Progress Summary (April 2025 — February 2026)

During the 11-month period from April 2025 to February 2026, PolkaWorld continuously carried out content production, community communication, and bilingual (Chinese–English) outreach around the Polkadot ecosystem.

Our work covered multiple formats and platforms, including articles, livestreams, interviews, educational short videos, WeChat video channels, and X (Twitter).

During this period, PolkaWorld did not focus on short-term content around a single event. Instead, we maintained consistent output centered on major developments within the Polkadot ecosystem. Against the backdrop of technical upgrades, governance discussions, narrative shifts, and increasing focus on product development, PolkaWorld’s work mainly focused on three areas:

1. Continuously updating the Chinese community on ecosystem developments
2. Producing explanatory content around key topics
3. Building clearer information connections between different communities through livestreams, interviews, and bilingual communication

Overall, from April 2025 to February 2026, PolkaWorld delivered:

• 270 articles, generating 307,587 total reads in the Chinese community (approximately 1,139 reads per article on average)

• 64 online livestreams

• 43 educational short videos, reaching 71,268 total views

• 155 videos published on the WeChat Video Channel, with 287,847 total views

• 11 interviews

In terms of social media reach:

• The English X account achieved 3.8 million impressions over the past year (compared to 1.9M the previous year)

• The Chinese X account achieved 1.3 million impressions over the past year (compared to 819.5K the previous year)

Overall, PolkaWorld has developed a relatively comprehensive content workflow, with long-form articles, livestreams, interviews, short videos, video channel content, and bilingual social media operating simultaneously, while maintaining a relatively stable monthly output.

If you have more time, you can continue reading below for a more detailed breakdown of deliverables.

4.1 Articles: Maintaining a High Publishing Frequency While Gradually Developing an Explanatory Content Structure

Over the past 11 months, PolkaWorld’s article output has remained relatively stable. With the exception of a few months affected by holidays, most months maintained a publishing range of 24–27 articles, supported by a relatively consistent workflow for topic selection, editing, and publication.

Article readership during this period fluctuated noticeably, but the overall baseline remained stable. Changes were mainly influenced by market conditions, holiday schedules, and shifts in content structure. Broadly speaking, the period can be divided into three phases:

Phase 1: April – June 2025

Monthly readership remained relatively steady, ranging between 22,000 and 24,000 reads.

Phase 2: July – October 2025

Overall performance improved, with monthly readership remaining consistently high during this period. In particular, October reached 42,690 reads, marking the peak of this phase.

Phase 3: November 2025 – February 2026

Due to holidays, changes in content structure, and the Chinese New Year period, readership declined somewhat. However, content production remained consistent and continued to maintain basic coverage.

In addition, our content focus has gradually shifted from simple information updates toward more explanatory and contextualized content, including topics such as:

• Long-term perspectives and ecosystem direction from Gavin Wood

• Infrastructure developments such as JAM, Polkadot Hub, Dual-VM, and 2-second block times

• Governance-related topics including OpenGov, DOT issuance reduction, governance structures, and the Treasury

• The broader narrative of Polkadot’s Second Age and the transition toward a product-focused strategy

• Ecosystem projects such as Hyperbridge, Hydration, and Bifrost

• Longer-term topics such as Human Agency and Proof of Personhood

4.2 Livestreams and Interviews: A Continuous Communication Mechanism

Livestream frequency has also remained relatively stable. Over the past 11 months, PolkaWorld hosted 64 livestreams, with most months maintaining 5–6 sessions per month. These livestreams covered both Chinese and English-speaking communities.

The main topics included:

• Governance and OpenGov: ongoing discussions around active proposals, governance mechanisms, Treasury usage, and institutional adjustments.

• Polkadot Hub and ecosystem opportunities: focusing on development, applications, and ecosystem collaboration following the launch of Polkadot Hub.

• Technical progress and developer experience: discussions around infrastructure changes such as Dual-VM architecture and 2-second block times, and their impact on developers.

• Application layer and ecosystem projects: covering topics such as payments, bridges, RWAs, liquidity, and related ecosystem projects.

• Ecosystem direction and long-term narratives: discussions around Polkadot’s evolving stage, market conditions, and longer-term development themes.

It is worth noting that the value of these livestreams is not fully reflected in the view count of a single session. More importantly, their continuity helps PolkaWorld maintain long-term communication with the community, developers, and ecosystem projects.

In addition, interviews have gradually developed into a consistent content format. Over the past year, PolkaWorld has continued producing bilingual (Chinese–English) interviews, featuring a variety of ecosystem participants, including:

• EasyA Co-founder
• Hyperbridge Co-founder Seun
• Apillon Founder Matjaz
• Parity Product Lead Karim
• The WebZero team
• Magenta Labs Co-founder Marco Moshi
• PaperMoon Founder Alberto Viera
• OpenGov Watch member Alice und Bob
• Parity Finance Lead Dave

These interviews typically go beyond simple project introductions and instead focus on broader questions related to Polkadot’s current stage, such as:

• How the developer experience is evolving
• What Polkadot Hub means for the application layer
• The practical challenges of ecosystem collaboration and business development
• The relationship between product adoption and infrastructure development

In this sense, the interviews function more like a long-term information bridge, helping the Chinese community better understand the perspectives of core builders while also introducing external builders to Chinese users in a more accurate and contextualized way.

4.3 Short Videos and WeChat Video Channel: Gradually Becoming an Effective Complement

From April 2025 to February 2026, PolkaWorld published 43 educational short videos, generating 71,268 total views.

In absolute terms, this segment is still smaller than the total readership of long-form articles. However, its importance lies in providing a lighter and more easily shareable format for explaining complex topics.

In practice, the videos that performed best typically focused on:

• Governance structures and OpenGov-related topics
• Polkadot Hub and the launch of smart contracts
• Ecosystem projects with clear use cases, such as Hydration and Hyperbridge
• Key perspectives and more controversial topics related to Gavin Wood

For an ecosystem like Polkadot, which often involves high information density, short videos cannot replace written articles. However, they are effective in lowering the barrier to understanding and highlighting key issues.

In addition, the WeChat Video Channel has become an important distribution channel. Over the past year, PolkaWorld published 155 videos on the platform, reaching 287,847 total views.

On a monthly basis, performance has fluctuated, but overall the channel has maintained consistent updates and a steady level of audience reach.

4.4 X Platform: Bilingual Communication in Chinese and English

The performance of PolkaWorld’s English X account has shown some fluctuations over the past year, influenced by changes in platform algorithms, market conditions, and the nature of the topics themselves.

However, overall, through continuous efforts to surface meaningful information, the English X account increased its impressions by 100% year-over-year, while the Chinese X account increased impressions by approximately 58.6% year-over-year.

In several key months, the English account saw particularly high engagement, mainly around topics such as:

• Major international events such as Web3 Summit and sub0
• Discussions and viewpoints related to Gavin Wood
• Technical narratives including PolkaVM, JAM, and Polkadot Hub
• Widely discussed topics such as DOT issuance reduction, ETFs, governance, and ecosystem direction
• Major ecosystem shifts, including Polkadot’s “Second Age” and strategic adjustments by Web3 Foundation

The overall reach of the Chinese X account is smaller than that of the English account, but its interaction quality has remained relatively stable. Its strengths include:

• More continuous engagement with Chinese-speaking users
• Faster responses to discussions around governance, issuance changes, and ecosystem debates
• A greater tendency to generate discussion and dialogue, rather than simple passive viewing

4.5 Phase Changes: Content Focus Adjusted as Polkadot Entered a New Stage

Overall, across articles, videos, livestreams, and interviews, PolkaWorld’s content focus from April 2025 to February 2026 was not static. Instead, it gradually evolved alongside changes within the ecosystem itself.

For example, from early to mid-2025, the focus was primarily on technical progress and ecosystem projects. During this period, content largely centered on topics such as:

• JAM, Coretime, and Elastic Scaling
• Ecosystem projects such as Hyperbridge, Hydration, and Bifrost
• Events and updates including Web3 Summit, Sub0, technical conferences, and product releases
• Governance discussions and proposals related to DOT issuance reduction

Toward the end of 2025, the proportion of in-depth content increased. In particular, between October and December, content increasingly addressed broader and more structural topics, including:

• Long-term perspectives from Gavin Wood
• Structural issues within OpenGov
• The complexity of governance and practical challenges in implementation
• Long-term challenges related to Polkadot as both an engineering and organizational system
• The broader narrative of Polkadot’s Second Age and the shift toward a product-focused strategy

Entering January and February 2026, the content direction further evolved to focus on:

• The launch of smart contracts on Polkadot Hub
• The reality of the Dual-VM architecture (EVM + PVM)
• The transition from infrastructure toward real products
• Developer experience, business development, and ecosystem collaboration
• Forward-looking themes such as Proof of Personhood (PoP), privacy, AI, and Human Agency

It is worth noting that these shifts in content structure reflect an intentional effort. PolkaWorld has not simply repeated the same updates mechanically, but has consistently tried to align its content focus with the evolving priorities of the Polkadot ecosystem.

4.6 Key Characteristics of This Phase of Work

Consistency

Over the 11-month period, PolkaWorld maintained a continuous publishing rhythm without significant interruptions.

Multi-channel distribution

PolkaWorld’s work is no longer limited to long-form articles. It now spans written content, livestreams, interviews, short videos, WeChat video channels, and bilingual social media communication.

A stronger emphasis on explanatory content

As the Polkadot ecosystem has become more complex, the value of simple news updates has decreased. As a result, PolkaWorld has gradually increased its focus on explaining complex topics, which is particularly important for the Chinese community.

Alignment with the ecosystem’s development cycle

From governance discussions and technical upgrades to the launch of Polkadot Hub, and from immediate ecosystem developments to longer-term narratives such as Human Agency, PolkaWorld’s content direction has largely stayed aligned with the ecosystem’s evolving priorities.

Overall, while maintaining consistent long-term output, PolkaWorld has gradually established a comprehensive content workflow spanning articles, livestreams, interviews, short videos, WeChat video channels, and bilingual social media.

Through this system, PolkaWorld continues to explain, organize, and communicate key technological developments, governance changes, and evolving narratives within the Polkadot ecosystem to the Chinese-speaking community.

4.7 Additional Deliverable Reports

In addition to the past year’s reports, you can also review PolkaWorld’s deliverable reports from the past four years here.

5. Planned Work (April 2026 – March 2027)

Over the next 12 months, PolkaWorld plans to continue building on its existing structure and deliver the following monthly outputs.

5.1 Articles

24 articles per month

Publishing cadence:

• 1 article per weekday
• 1 weekly report every Saturday

Content types include:

• Ecosystem updates
• Original commentary and explanatory articles
• Progress updates from ecosystem projects
• Chinese versions of English interviews, livestreams, or other high-quality English content

Distribution channels include:

• WeChat Official Account
• Foresight News
• Binance Square
• Chinese X account
• Chinese community groups and private community channels

In addition, it is important to note that since PolkaWorld was founded, our guiding principle for topic selection and content has remained consistent:

• to publish content that users care about,
• content that users can easily understand,
• and content that is most relevant and important to the community.

5.2 Video Content

4 educational short videos per month, with additional commentary clips produced when appropriate.

Content may include:

• Educational short videos focused on important Polkadot-related topics
• Highlight clips extracted from English interviews, livestreams, and ecosystem discussions
• English content with Chinese subtitles added for broader distribution

Distribution channels include:

• WeChat Video Channel
• YouTube
• X

5.3 Livestreams

6 livestreams per month (4 in Chinese + 2 in English)

Planned recurring series include:

Polkadot Hub & Ecosystem Opportunities Series

Discussions focused on development opportunities, application directions, ecosystem collaboration, and the broader implications following the launch of Polkadot Hub.

Technical Progress & Developer Experience Series

Covering changes such as the Dual-VM architecture, developer tooling, and broader infrastructure evolution.

Application Layer & Ecosystem Projects Series

Discussions around payments, bridges, RWAs, liquidity, and updates from specific ecosystem projects.

Governance / OpenGov Series

Ongoing coverage of active proposals, governance changes, Treasury discussions, and broader participation in OpenGov.

English Ecosystem Livestream Series

Including builder conversations and monthly ecosystem recaps aimed at a broader international audience.

All livestreams will be broadcast on YouTube and X, with recordings available afterward. Selected highlights may also be repurposed into articles or short videos.

5.4 Interviews

1 in-depth interview per month.

Potential interview guests may include:

• Members related to Web3 Foundation
• Members of the Parity team
• Ecosystem builders
• Infrastructure teams
• Product-oriented project teams

Interview outputs may include:

• Full video interviews
• Chinese written summaries
• Highlight clips featuring key insights
• Distribution across YouTube, X, WeChat, and media platforms

5.5 X / Social Media Operations

PolkaWorld will continue operating two X accounts:

• PolkaWorld (English)
• 波卡世界 (Chinese)

Operational target:

• On each weekday, each account will publish at least three posts related to Polkadot.

This work includes:

• Monitoring X, forums, ecosystem discussions, and project updates
• Identifying important developments
• Filtering information that is genuinely valuable to users
• Reorganizing and presenting the information in ways that are clear for both Chinese and English audiences

Although this work may appear relatively simple, our experience shows that it is often the most time-consuming and labor-intensive part of the process.

While AI tools can help summarize daily developments, the information they provide is often too high-level. We still need to spend significant time tracking information flows across X, the Polkadot forum, Element discussions, and updates from key ecosystem projects, identifying meaningful signals, filtering noise, and restructuring the information into a format that ordinary users can easily understand.

The goal is to provide the community with the most up-to-date, insightful, and valuable information possible.

5.6 Chinese Community Distribution

Important Polkadot-related information will be shared daily across the following channels:

• Chinese WeChat groups
• Telegram groups
• PolkaWorld’s private WeChat accounts

This work helps maintain continuous engagement with the Chinese-speaking community and ensures that important information does not remain confined to public timelines alone.

5.7 Monthly Deliverable Reports

PolkaWorld will continue publishing monthly deliverable reports summarizing the work completed, data metrics, and overall progress.

This practice has been maintained across multiple funding cycles and remains an important part of ensuring transparency and accountability to the community.

6. OKRs for This Funding Cycle

Over the course of the 12-month period, PolkaWorld plans to deliver:

• 288 articles
• 48 educational short videos
• 72 livestreams
• 12 interviews
• Ongoing operation of two X accounts
• Ongoing information distribution within the Chinese community
• 12 monthly deliverable reports

These targets are based on the continuation of the current workflow and operating structure.

7. Team Structure

This proposal is expected to be supported by the following roles:

• 2 Editors-in-Chief
• 1 English Livestream & Interview Lead
• 1 Chinese Livestream Lead
• 1 Video Lead
• 1 Designer

Key Responsibilities

Editors-in-Chief

• Content research and weekly topic planning
• Article writing and editing
• Distribution of articles to media platforms
• Daily operation of the X accounts

English Livestream & Interview Lead

• Designing topics for English livestreams and interviews
• Coordinating with guests and scheduling sessions
• Managing monthly English interviews
• Organizing English-language livestreams

Chinese Livestream Lead

• Designing topics for Chinese livestreams
• Organizing Chinese livestream sessions
• Managing livestream channels and coordinating the overall process

Video Lead

• Planning and publishing educational videos
• Managing the WeChat Video Channel
• Editing highlight clips from livestreams and interviews
• Distributing video content across multiple platforms

Designer

• Article illustrations and visuals
• Livestream promotional posters
• Interview promotional posters
• Short video cover images
• Visual materials for holidays and special events
• Brand-related visual support

8. Budget

Total Amount Requested: 278,256 USDT

Funding Period: 12 months

Below is the current personnel budget structure.

Budget Notes

• The budget for this proposal mainly consists of personnel costs required to maintain the current multi-channel content workflow.
• This is not a proposal to build a new team from scratch, but rather to sustain the existing operational workflow and delivery structure that has already been established.
• The current USD to RMB exchange rate is calculated at 1:6.9.

9. Why This Work Deserves Continued Support

This proposal is not based on vague promises about the future. Instead, it is built upon a publicly documented track record of deliverables.

During the previous funding cycle, PolkaWorld has demonstrated its ability to:

• Maintain a consistent publishing cadence
• Operate multiple content formats simultaneously
• Sustain ongoing visibility in the Chinese-speaking market
• Adjust content direction in response to shifts within the Polkadot ecosystem
• Regularly publish public deliverable reports

Therefore, this request is not funding for a brand-new experimental initiative, but rather support for continuing a content and communication system that has already been operating publicly and has demonstrated consistent delivery.

Over the next year, PolkaWorld’s goal remains clear:

to continue providing stable, accessible, and sustainable multi-channel content and communication for the Chinese community, while maintaining bilingual visibility around key ecosystem discussions related to Polkadot.

We welcome questions and feedback from the community.

Contact:

Telegram: @xiaojie_web3world

Email: [email protected]

Polkadot Sensei v1.0.0

Amount: 25,500 DOT
Track: 33 | Medium Spender

Full Proposal: vonFlandern.org/polkadot-sensei/proposal | 🕐 15 min read

What is Polkadot Sensei?

An onboarding engine that converts curious newcomers into verified, active Polkadot participants.

What is being funded?

The technical foundation (game mechanics, OCR, CEA, leaderboard) is already live as a working beta — built at the proposer's own expense.
This referendum funds exclusively the content creation for Polkadot Sensei v1.0.0.

Payout Schedule

DOT/USD rate at submission: 1.46 — Total: 25,500 DOT ≈ 37,300 USD

DotBot

Executive Summary

DotBot is a conversational interface for the Polkadot ecosystem that allows users to execute blockchain operations using natural language instead of complex technical interfaces.

The project focuses on translating user intent into safe, runtime-aware transactions across Polkadot Asset Hub and selected parachains. While basic asset transfer functionality is already implemented, further work is required to ensure correctness guarantees, robust transaction validation, and predictable behavior across wallets and runtimes.

This proposal requests funding to complete the stabilization and beta-level hardening of DotBot’s execution layer, including transaction simulation, end-to-end scenario validation, and modular infrastructure that can be reused by wallets and applications. Development began prior to this proposal submission and continues independently. This request covers both completed foundational work and committed future deliverables.

DotBot aims to serve as foundational infrastructure that improves accessibility, safety, and usability across the Polkadot ecosystem.

Live version: https://live.dotbot.zelmacorp.io/

Problem Statement

Interacting with the Polkadot ecosystem currently requires users to understand
chain-specific user interfaces, runtime details, and transaction semantics.
Even simple actions such as asset transfers, staking, or governance participation
require navigating complex tooling that is inaccessible to most non-technical users.

While Polkadot provides powerful primitives such as XCM and runtime-level
customization, these same strengths increase cognitive overhead for end users.
As a result, many users rely on copy-pasted instructions, third-party tutorials,
or trial-and-error interactions that can lead to mistakes, failed transactions,
or loss of funds.

Existing wallet and dApp interfaces primarily expose low-level transaction
construction rather than intent-based interactions. This creates a gap between
what users want to do (“send DOT to Alice”, “swap assets”, “recover an account”)
and the actual operations required to achieve those goals safely.

DotBot addresses this gap by introducing a natural language interface that
translates user intent into runtime-aware, validated Polkadot transactions.

(In short, Polkadot’s technical power has outpaced its usability for non-expert users.)

Current State & Work Completed

Development of DotBot is already underway, and a functional prototype exists.
A live beta version is available at: https://live.dotbot.zelmacorp.io/

The current implementation focuses on intent-driven transaction execution rather
than traditional form-based workflows. In particular, DotBot currently supports:

• Conversational input for asset transfers using natural language
• Context-aware interpretation of user intent across multiple messages
• Clarification prompts when user intent is ambiguous (e.g. resolving “Who is Alice?”)
• Explicit user confirmation before any transaction is constructed or submitted
• Visualized execution flows that expose each step of the transaction lifecycle
• Generation of runtime-compatible Polkadot extrinsics based on interpreted intent
• Wallet-based signing using standard Polkadot browser extensions
• A testing framework called ScenarioEngine, which can run and evaluate scenarios. While not required for end users, it is exposed via an advanced or developer-facing interface for verification, debugging, and auditability by power users and ecosystem developers.

Rather than immediately submitting transactions, DotBot presents users with a step-by-step execution flow that makes intermediate decisions visible and allows
users to validate or abort actions before signing.

During implementation and testing, we identified substantial complexity around
transaction correctness and execution guarantees across different runtimes and
wallet environments.

Specifically:

• Simulation and dry-run tooling behaves inconsistently across chains
• Wallets differ in metadata exposure, signing behavior, and account derivation
• Certain extrinsics that are syntactically valid fail during real execution
• Local and fork-based test environments cannot fully reproduce mainnet behavior

These findings reinforced the need to treat correctness, validation, and execution
transparency as first-class concerns rather than secondary features.

As a result, we intentionally shifted focus from feature expansion to robustness,
correctness, and execution guarantees. This led to additional engineering work that was not fully accounted for in the original proposal timeline.

While basic asset transfer functionality exists today, it is not yet at a level where we consider it safe to present as production-ready infrastructure.

These findings directly informed the revised scope and priorities of this proposal, which emphasize reliability, validation, and modular execution infrastructure over rapid feature expansion.

Strategic Pivot: From Feature Completion to Execution Guarantees

During development, it became clear that conversational blockchain interfaces
cannot be built reliably using traditional transaction construction patterns.

Large language models do not reason in terms of extrinsics or runtime calls.
They reason in terms of scenarios, goals, constraints, and expected outcomes.

Existing tooling assumes that:

• The developer already knows the exact transaction to execute
• The UI is static and pre-validated
• The execution path is deterministic and manually curated

None of these assumptions hold when the transaction originates from natural
language and is dynamically generated by an AI agent.

Rather than continuing to add features on top of unstable foundations, we made a
deliberate decision to prioritize execution correctness, debuggability, and deterministic behavior.

This led to the introduction of ScenarioEngine as a first-class abstraction:
a structured, end-to-end execution and validation layer that represents user
intent as an explicit, inspectable scenario rather than an immediate transaction.

ScenarioEngine acts as an execution contract between user intent, AI agents,
and the blockchain runtime.

A scenario defines:

• The intended outcome (e.g. “Send 5 DOT to Alice”)
• The entities involved (accounts, chains, assets)
• Preconditions and invariants
• One or more executable transaction paths
• Validation, simulation, and confirmation checkpoints

This approach is conceptually similar to test-driven development, but applied
at the level of end-to-end transaction scenarios rather than isolated unit tests.
Instead of asserting that individual functions behave correctly, ScenarioEngine
asserts that real user intents can be executed safely and predictably on-chain.

Technical Architecture (High-Level)

DotBot is built around modular, intent-driven execution with clear separation between user intent, transaction creation, and execution.

At a high level:

User Input & Intent Parsing

Users interact through natural language. The system interprets messages, maintains context, and asks clarifying questions when intent is ambiguous.

AI Planning Layer

Large language models (currently ASI.One, but Claude support is also underway) generate structured execution plans that describe what the user wants to achieve without directly constructing transactions.

Execution Layer

The Orchestrator turns AI-generated plans into runtime-compatible transactions (extrinsics) by calling the right agents and building the ExecutionArray. The Executioner handles signing, submission, and monitoring, keeping the process deterministic and auditable.

User Validation

Users review each step of the execution flow, confirming or aborting actions before signing.

Execution

DotBot will go through each step of the Execution Flow, user will be prompted to sign transaction, when needed.

Key Principles:

• Separation of concerns between planning, execution, and signing
• Deterministic, step-by-step transaction flows
• Modular components that can be extended or swapped
• Built-in simulation to ensure correctness, with Chopsticks.

This architecture ensures that DotBot is both safe and extensible, allowing us to add new features without compromising execution reliability.

Development Plan & Timeline

This proposal includes both retroactive funding for work already completed and
guaranteed deliverables to be completed after funding approval.

Development of DotBot is already underway and continues independently; however, the
items listed below represent the scope for which funding is requested and evaluated.

Deliverables & Milestones

Work Already Implemented (Retroactive)

The following deliverables are already implemented or functionally complete at the
time of submission and will be available for inspection during the proposal
evaluation period.

This work forms the foundational infrastructure of DotBot and demonstrates that the system is already functional, testable, and evolving in practice.

Work to Be Delivered After Funding

Upon approval and fund disbursement, the following deliverable will be completed
within one month

Only the items listed in this section constitute binding delivery commitments
under this proposal.

Further functionality (e.g. governance interactions, staking, multisig workflows,
advanced asset visualization) may continue to be explored but is explicitly out of scope for this funding request.

Team members

• Peter Ott
• Fanni Borbás
• Marklar
• Vonyi

Team's experience

Peter

Full Stack software developer with 4 years of professional development experience and 10 years in the cryptocurrency space, specializing in TypeScript applications. Previously won a price in the DAO Track at Polkadot Championship, demonstrating expertise in decentralized governance solutions. Has hands-on experience with decentralized technologies including IPFS and Swarm, combining deep blockchain knowledge with practical development skills.

Fanni Borbás

UX/UI Designer and Web Developer with 5+ years of experience creating digital solutions across diverse industries. Specialised in designing user-centric interfaces for AI-powered platforms, cryptocurrency tools, and mobile applications. Has successfully delivered complete brand identities, web designs, and motion graphics for tech startups and blockchain projects. Combines deep understanding of user experience principles with technical implementation skills, creating cohesive digital experiences from concept to deployment.

Vonyi

Has deep technical knowledge, including hands-on experience developing the first version of the VotingTool (Vercel-based) application and ongoing maintenance of polkadothungary.net. Brings strong ecosystem knowledge, broad crypto-related expertise, and a genuine crypto enthusiast mindset, enabling thorough software testing, realistic validation of edge cases, and effective feedback aligned with ecosystem standards and user expectations.

Marklar

Project Manager with a strong technical background in Python application development and AI-assisted systems, including hands-on experience building interactive tools and developer-facing applications. Prior work with procedural logic, state management, and applied AI workflows enables effective coordination between engineers, designers, and stakeholders. Brings an implementation-aware approach to planning, prioritization, and delivery, translating technical and AI constraints into clear, executable project goals.

Budget

The requested budget covers the personnel required to complete the stabilization and delivery scope outlined in this proposal. The allocation reflects a deliberate focus on execution correctness, validation, and beta-level reliability rather than rapid feature expansion.

The majority of effort is allocated to a single Full-Stack Developer responsible for the execution layer, ScenarioEngine hardening, and feature integration. This role spans both retroactive work already completed and forward-looking commitments, and is intentionally weighted toward correctness, testing, and reliability—areas that require sustained engineering effort.

Additional roles support usability, verification, and coordination:

UI/UX design to ensure complex execution flows and swap interactions are clearly and safely presented to users

Software testing to validate deterministic behavior across runtimes, wallets, and network environments

Project management to coordinate delivery, documentation, and milestone tracking

The overall scope represents approximately four months of full-time equivalent work, combining completed foundational development with committed post-approval deliverables.

Total requested amount: $75,360.

Risks, Constraints, and Non-Goals

Risks

Evolving runtimes and cross-chain behavior: Polkadot and its parachains continue to change; some edge cases may require ongoing adaptation.

AI-driven execution: Natural language interpretation introduces potential ambiguity. ScenarioEngine mitigates this risk, but does not eliminate all unexpected outputs.

Wallet differences: Variations in signing behavior, metadata exposure, and account derivation may cause inconsistencies that require careful monitoring.

Constraints

The system will operate within the current capabilities of Polkadot, XCM, and standard wallet integrations.

Development will focus on safe, validated execution flows; feature expansion is intentionally limited until core correctness is fully established.

Non-Goals

DotBot does not abstract away all blockchain complexity. Users will still interact with runtime concepts when necessary.

The proposal does not cover end-to-end production readiness for all possible chains or wallets; the goal is a beta-level, safe execution environment.

DotBot does not replace professional decision-making for sensitive operations; it provides guidance, transparency, and safety checks.

Long-Term Vision & Ecosystem Fit

DotBot aims to become the foundational natural language interface for the Polkadot ecosystem. Our long-term vision is to provide developers, wallets, and end-users with modular, reusable infrastructure that simplifies complex blockchain interactions while maintaining safety and transparency.

Key elements of the vision:

• Library-first approach: DotBot will be published as reusable packages, initially @dotbot/core for the execution and planning layer, and @dotbot/react for UI integration. This allows developers to embed DotBot functionality into their own applications without reimplementing the execution logic.
• Extensible Agent ecosystem: Additional agents will be added to cover the broader Polkadot ecosystem (staking, governance, asset swaps, multisig, cross-chain transfers), enabling natural language execution across a wide range of operations.
• Visual and interactive responses: Beyond text, DotBot will support rich visual feedback such as charts, progress indicators, and other UI elements to help users understand transaction outcomes and system state.
• Open-source ethos and community integration: By publishing the core libraries and encouraging contributions, DotBot will foster a shared ecosystem standard for safe, natural language blockchain interactions.
• User-centric accessibility: The ultimate goal is to make Polkadot usable for both technical and non-technical users, reducing cognitive overhead, avoiding errors, and enabling broader participation in decentralized finance and governance.

Through this approach, DotBot is positioned not only as a single application but as a reusable, extensible platform that supports future development of conversational interfaces for Polkadot and potentially other blockchain ecosystems.

Note on Retroactive Funding

A significant portion of this proposal covers work already completed. We believe
this is justified for the following reasons:

1. Previous Funding Attempts: We initially applied for an Open Source Bounty but were declined due to program runway constraints, not project merit. Rather than to halt development, we proceeded at our own risk to validate the concept and deliver value to the ecosystem.
2. Risk Absorption: Development continued for many months without funding to identify and solve real technical challenges (runtime inconsistencies, wallet variations, simulation reliability) before requesting treasury funds.
3. Deliverable Verification: Validators can inspect and test the existing implementation during evaluation via the public repository and live beta deployment: https://live.dotbot.zelmacorp.io/. The codebase is publicly available at https://github.com/ZelmaCorp/DotBot/.
4. Ecosystem Value: The foundational architecture (execution engine, simulation layer, ScenarioEngine) is already functional and can be reused by other projects immediately upon proposal approval.

We acknowledge that retroactive funding is not typical, but the demonstrated
working prototype substantially de-risks this proposal compared to purely
speculative requests. The treasury receives a functional product rather than a promise.

Preamble

Hey, assembly :)

As a good engineer I’m a bit lazy to write hundreds lines of a grant application before knowing whether anyone is actually interested in what I’m about to propose. So I’ve decided to start with this nice little discussion, mainly to see if there is at least some tension or interest around what we are building at Chain.Love.

I'd really appreciate a feedback - even negative. A clear “no” is better silence, cuz at least you know why you are failing.

Fable

Problem statement

So, let me start this with a simple question.

How do you personally discover services available in the Polkadot ecosystem?

While doing my research I came up with https://polkadotecosystem.com/tools

There are things that I definitely like and do not like about this page, namely:

Pros:
1) It is open-source. In an active community having an open-source documentation is a total must-have. Otherwise you are going to simply drown in following many updates that are happenning in the tools for the ecosystem

2) https://x.com/lvweb3 have been around Polkadot ecosystem for a couple of years now, and probably he gains trust of the Polkadot ecosystem, which can be clearly seen by the voting last year with more than 78% of voters voting in favor of issuing a grant.

3) Multi-language, so people can find information useful in their language, although I see that the portal is not fully translated and suffers from constant language switching when navigating through different pages.

4) The website is fully dedicated to the ecosystem. This approach is having it's own pros and cons, of course.

Cons:

1) How do I actually compare anything there? Like, when opening polkassembly I wanted to know if any of the wallets I'm already having is actually supporting both EVM networks and Substrate ones, just not to install yet-another-wallet-that-I-will-forget-soon, but can I do that? Or, when I'm thinking about developing a dApp - I want to check which of the RPC providers are having limitations, and what are these limitations really?

2) Are there at least links to these providers, so when I'm googling I'm not getting into a scammy website?

3) The last update was several months ago and some of the tools were not updated for much longer. Can we say that all the data stays the same when it comes to months of work? The problem is essentially lack of incentive for anyone to go and update this page beyond a https://x.com/lvweb3 man supporting it and a few contributors who appears around once a year.

The last point is not made to do any harm, but rather to ask a question - what incentive does one have to participate and keep all the documentation up to date? Keeping the documentation up to date will always be "an expense" for the ecosystem. And that is the problem we are aiming to solve at Chain.Love.

What is Chain.Love?

As a part of a team I have been working on a platform that can be described as a “marketplace” of Web3 services. It’s key component is called “Toolbox” - a place to discover, compare and access different services available over the ecosystem:

The points I've addressed above we are covering in the following way:

1) We build it on top of the open-source database: https://github.com/Chain-Love/chain-love .

2) We keep our contributors motivated - every adjustment that brings value to the ecosystem is paid according to the established set of rules (aka "Database population grant program").

3) We launch a subdomain that is dedicated to the ecosystem, with no network-switcher, so no "user leak" occurs here.

4) We have a fully-functional search, filter and side-by-side comparison across categories

5) We have been noted and trusted by a number of major ecosystems, examples:
a) Arbitrum

b) Filecoin

c) Algorand

d) ChainBase

6) We are not only verifying all the links in our database, we have also periodic automatic checkers that update all the outdated links and remove deprecated projects

7) We have a working AI search that helps users to get answers in their natural language. To clarify - regular AI is not as good because it does not have our database as an information source. And AI is only as good as its sources. Web3 service data is fragmented, non-standardized, and changes frequently. As a result, generic AI answers about RPCs, pricing, limits, or features are often outdated or simply wrong.

Try for yourself! Imagine you are an engineerthat wants to build adApp… on Ethereum. You don’t have much money, but your app will be super RPC call-intensive. Now, try asking any AI you know on what is a cheapest RPC provider on Ethereum from the query fee perspective. I can predict the answer more or less, since we used to run these tests dozens of times: “Absolutely! Here are the top-3 providers on Ethereum with lowest access fee as of <CURRENT_MONTH> 2026!” And then it will give you a list of 3 random provider names and their hardly comparable query fees, while proofing it with an article written back in 2023.

Now, try this for a change: Chain.Love ChatGPT

---

Now. Of course, the money have to come from somewhere, right? In Chain.love we are not only having our own runway, but we already secured more than $20k MRR (monthly recurring revenue) by selling side services (such as RPC, Indexing, Performance monitoring, Advertisment, etc.), and we are aiming to make a big leap towards becoming a transactional marketplace.

Roadmap: Transactional marketplace

We want providers to be able to "plug-in" their solutions and sell them in a fully automated mode via an OpenAPI standard we are currently developing.

That part is being under construction as we speak. We are actively looking for an ecosystem that may be interested in funding/investing into its development, to secure a flow of purchases through the ecosystem's native token. It’s a bigger investment, but also a much bigger outcome once real transactions start flowing.

Summary

We would love to deploy Chain.Love over Polkadot, and I’m curious here whether you see the value in such a solution?

There are three possible modes:

• a discovery / comparison layer (Toolbox) - it can be a quid pro quo, with us deploying it even for free in exchange for an active promotion inside of the ecosystem;
• same Toolbox, but as a paid servce - with all the SLAs and hard guarantees of regular updates from our team (see example of our reports here)
• a fully-featured services marketplace

I’m very curious whether either of these aligns with the current interests and priorities of the Polkadot ecosystem.

Thanks a lot to everyone who took the time to read this. Any feedback — positive or negative — is genuinely appreciated.

Looking forward to your thoughts,

Arsenii

Formal proposal

Chain.Love is a Booking.com–style marketplace for the Web3 infrastructure.

Used by developers and AI agents, it enables discovery, comparison, and access for infrastructure services (APIs, CPU/GPU compute, dev tools) via a single UI and API.

Our mission is to make blockchain services accessible, transparent, and reliable by providing networks, providers and developers with a unified hub for discovery, comparison, and consumption of Web3 services. We empower ecosystems to grow faster by reducing fragmentation, increasing trust, and enabling fair competition among providers.
A deeper story-telling dive into why the project is important and also a comparison with the existing solution is available at the Discussions tab

Problem-solution set

Problem

Web3 infrastructure is fragmented and inefficient. Developers building on new blockchains face a messy and time-consuming process when setting up services they depends on:
• Developers struggle to discover and compare infra by price, limits, features, and performance. The process is manual and time consuming
• Each chain documentation links to different SDKs, APIs, bridges, wallets, faucets, oracles, and other tools — all with their own docs, pricing, limits, and formats. More information about how this affecting the Polkadot ecosystem is available here.
• Every developer has different needs: some care about uptime, others about speed, privacy, programming language adoption, specific API methods, or regional access. But today, finding the right provider means digging through scattered resources and testing everything manually.

Solution

Our Toolbox layer is aligning the incentives. It acts as a single, trusted hub where developers can discover all available options and compare providers side-by-side:
• Devs get single UI/API to find, compare, and access all services for all networks. They may also leverage performance monitoring and load balancer as a service to achieve higher quality of the Polkadot's APIs.
• Providers get aggregated demand and lower customer acquisition cost
• Automatic fisherman-like verifications designed to verify the existence of the providers and the quality of their services

Costs justification

There are 3 main cost drivers:

• Engineering time — core marketplace development and performance module tuning, including initial configuration and testing aligned with Polkadot ecosystem parameters (API setup, validation, and benchmarking).
• Maintenance time — ongoing work required to ensure high availability and reliability of the Chain.Love service.
• Documentation, open-source database population, and developer engagement — maintaining and expanding public documentation, contributing to the initial dataset and its regular updates, actively participating in community channels (chats, forums, and other ecosystem venues), monitoring ecosystem development, proactively updating information about newly emerging services, and encouraging developers to contribute to the open-source database.

Milestones

Milestone 1

Amount (DOT): 5000
Timeline: within 1 week
Milestone description:
Developers want to be able to easily discover, compare and access service in the Polkadot ecosystem. They need verified, structured, comparable, visually-represented datasets when discovering web3 service providers. For that developers need a place where I can discover, compare and purchase Web3 servces. They can't rely on documentation alone, because once one decide to build on Polkadot, the questions one need to answer immediately become practical and comparative than the documentation may answer, namely:
- Is there an SDK/library for the programming language I'm planning to write on?
- Where to get free tokens? Which faucet are reliable? Do they provide enough funds for me? Will I need to perform the KYC?
- Is there a wallet that is compatible between all the network I plan to deploy on?
- Which oracles, RPCs, bridges do exist, and which have usable free tiers?
- Is there a company performing security audits?
- How do I compare all these options in a big ecosystem side-by-side without visiting 10 sites and reading inconsistent docs?

Today, there is no neutral, structured, up-to-date answer to these questions in the Polkadot ecosystem. The reality is described at the Discussions tab.
As a part of this milestone we deploy a life installation of Chain.Love Toolbox. A real-life example on how one looks inside of the Polkadot-based network - Astar - can be seen here: https://astar.chain.love

Deliverables

1) https://polkadot.chain.love toolbox
2) Embeddable Toolbox widget ready for inclusion in the Polkadot docs or any ecosystem pages (optional). Example: https://chain-love.gitbook.io/chain.loves-toolbox/features/widget-for-docs/example-of-our-widget
3) At least 5 (or maximum existing) providers listed per every existing category that matches the Polkadot ecosystem (currently there are 13 categories: apis, explorers, oracles, bridges, sdks, faucets, analytics, wallets, platforms, ramps, security, storages and other services; a number of categories is constantly increasing)
4) (Optional) New categories added where relevant to the Polkadot ecosystem
5) AI-powered search fully operational on Toolbox that returns relevant and consistent results for user queries. Why usual AI is not fitting here is described at the Discussions tab

Milestone 2

Amount (DOT): 5000
Timeline: within 3 months
Polkadot ecosystem deservers to see a real-time adoption and usage metrics of the solutions, that were bootstrapped using the grant funding. As a part of this milestone we will publish public real-time MAU analytics dashboard and will dedicate efforts to bootstrap the usage of the Toolbox in the Polkadot ecosystem. As well, we will continue our efforts on increasing the overall Toolbox adoption as an industry standard.

Deliverables

1) A growth of at least 25% MoM active usage is achieved for the first 3 consecutive months
2) Toolbox uptime ≥99.9% since launch
3) Developer feedback loop live (GitHub Discussions, Polkadot forum, or equivalent)
4) A set of patches in the existing Polkadot documentation proposed to include Chain.Love as the information source.

Milestone 3

Amount (DOT): 10000
Timeline: 12 months+
During the support phase that will last at least a year, and likely more (roadmap to full self-sustainability can be found at the bottom of this page) we will keep updating the Chain.Love database of the Polkadot ecosystem, improving the marketplace and encouraging regular developers to contribute into the open-source database of Polkadot ecosystem services

Deliverables

1) Regular database updates (at least 2 per month) with at least half of the contributions being done by external contributors. At least 15 unique contributors, with at least 30 pull request merged from them, updating information about the Polkadot ecosystem.
2) ≥3 top developer-requested features shipped based on community feedback
3) Monthly and quarterly updates summarizing progress, and a comprehensive maintenance report at the end of the 12-month period.
4) (optional) new categories added to better represent Polkadot ecosystem

Project success metrics

We believe that the key success criteria for this project is it becoming fully self-sustainable and supporting Polkadot ecosystem for years ahead. For that we need to keep increasing our adoption, and developing a distinct unique features, such as the one described later in this proposal in the Roadmap section.

As for the adoption part, we have a structured plan on how to attract more users and make our product more visible, namely:

1) Search indexing – provider pages and comparison pages (“RPC A vs RPC B”, “Best free Polkadot oracles”) indexed by the search engines similarly to Versus-style sites.
2) AI ingestion – MCP / structured access so LLMs pull fresh web3 services data instead of hallucinating.
3) Docs integration – we have an open-source widget that is basically a light embeddable version of Chain.Love that you may include into your network documentation.
4) Providing additional functionality on top - monitoring and load balancer as a service. Also, developing a transactional marketplace will solve a problem of services being scattered too much. The roadmap to it is described below.
5) Developers motivation - we believe that no matter how much we try we will not be able to keep up with the pace of changes in the such a rapidly developing ecosystem as Web3. This is why we’ve realized, that the path to succeed here - is to motivate those working with the chains - developers - to contribute into our database. For that purpose we’ve made it open-source, and for that purpose we are running a reward program, giving tiny, but stable[coin] rewards to those contributing. We are maitaining a balance by not providing too high bounties (and yet providing tangible ones) to ensure we attract visioners, not bounty hunters.
6) DevRel alignment – positioning Chain.Love as a complement to official docs, not a replacement. This approach has already been positively validated with DevRel teams and developers across multiple ecosystems (Arbitrum, Algorand, Filecoin, Flare, Sonic, Somnia). Here are the few examples of ecosystems posting about us:
-Arbitrum
-Filecoin
-Algorand
-Chainbase

Additional criterias include:
- High uptime of over ≥99.9% since launch
- Proven MAU growth trend with public analytics
- Alive community that submits PRs and suggest new features to implement.

Roadmap

Chain.Love team currently runs more than 15 live installations across multiple blockchain networks, serving over 1,000 real monthly active users (developers). We live off the initial investment from Protofire DAO, as well as a number of grants and recurring clients:

• $20k+ MRR
• Customers : Filecoin, Arbitrum, Somnia, Fuse, Algorand
• Grants received: Filecoin Foundation, Arbitrum DAO
• Winner of EigenLayer Hackathon, validating reliability module

To become fully self-sustainable we are in progress of transition to becoming a transactional marketplace. For that, we develop and OpenAPI specification (so providers can integrate with the Chain.Love in an automated way) and a x402-based system (so user purchases can be done automatically). The scope and the proposed butdget of this proposal, for now, remains on addressing the service discoverability problem (why this is a problem can be seen at the Discussions tab), however, should there be interest from the ecosystem in bringing the x402-payments to the Polkadot ecosystem, we would be very interested in collaborating and contributing in that direction.

This Referendum is canceled. Please (continue to) vote Nay.

A new version incorporating the feedback received here is up for vote: New Proposal

---

Voters have become increasingly cautious, making it harder for projects to gain approval for their proposals. Our project introduces a clawback mechanism to significantly reduce risks to the Polkadot Treasury. By implementing this safeguard, we aim to lower financial exposure and provide voters with peace of mind to confidently approve funding for impactful projects.

With our tool, a group of decentralized treasury guardians is incentivized to oversee scheduled payouts and intervene when necessary to protect the Treasury.

Key features of our proposal:

• No upfront payments are requested.
• All payouts are tied to milestone delivery, with sufficient time for the community to review and delay/ cancel disbursements if needed to ensure accountability on our behalf.Milestone Delivery Deadlines:
  Milestone 1: Nov 9 2025 -> Scheduled Payout: Dec 29 2025
  Milestone 2: Dec 7 2025 -> Scheduled Payout: Jan 26 2026
  Milestone 3: Jan 4 2026 -> Scheduled Payout: Feb 23 2026
  Milestone 4: Feb 1 2026 -> Scheduled Payout: Mar 23 2026
  Milestone 5: Mar 1 2026 -> Scheduled Payout: Apr 20 2026
  Milestone 6: May 29 2026 -> Scheduled Payout: May 18 2026

We are passionate about leading the charge to de-risk the Treasury, enhance its efficiency, and better align the interests of token holders and proposers. We eagerly look forward to collaborating with the Polkadot community and new + existing ecosystem teams to achieve these goals.

Read our full proposal here.