Rejected

small_tipper

Vote Nay - preimage not on chain. 

The Ambassador Fellowship had a successful first phase, even with challenges. The team did a great job and finished their work on time. They were supposed to get a payment, but some board members left, and the money was returned to the treasury instead. Now, the Ambassador Fellowship is still going and needs more funding. The person in charge thinks it's fair to ask for the team's payment again. You can find more information about the team and their work in the links provided. Thank you for supporting the Ambassador Fellowship.

During the first funded phase of the Ambassador Fellowship, we achieved remarkable success — even amidst periods of uncertainty and transition. This success was largely thanks to the dedication of individuals who stepped up as volunteers to ensure we not only met but exceeded our deliverables within the agreed timeframe.

Per the agreement with the Advisory Board (see[ Sprint Overview Document](https://docs.google.com/document/d/1zc0WAzXezZSFryfZ-xlpLPt4xgouvl4mLamy60fO15k/edit?usp=drive_link)), a discretionary payment was to be made to the core team upon successful delivery by May 3, 2025. Through careful financial stewardship — managed solely by myself — $230,000 remained in the Ambassador Fellowship fund. The plan was to distribute $29,000 to the team, with the remaining $201,000 returned to the treasury when the Board stepped down (five weeks later than anticipated).

The delivery deadline was met, and the Advisory Board confirmed the work was completed successfully.

However, during this period, several Board members resigned due to the extended duration of their roles. With diminished capacity and activity, decision-making became increasingly difficult. Ultimately, the remaining funds — including the portion intended for the team — were returned in full to the treasury for administrative ease. As a result, the promised payments were not made.

Today, the Ambassador Fellowship remains active and is preparing a proposal for further funding to support its continued growth. Cohort Two is currently being seeded, and a waitlist for Cohort Three is already forming — a clear sign of the program's community value and continued success. You can find our[ Delivery Report here](https://drive.google.com/file/d/18WwkjxAzOe5SIbSICl5vcQ2ziAtnUCwe/view?usp=drive_link).

After careful consideration and consultation, I believe the fairest path forward is to submit individual compensation requests on behalf of each team member. These individuals fulfilled their commitments and contributed significantly to the Fellowship’s outcomes. The full list of team members and corresponding payment amounts can be found in this[ Spreadsheet](https://docs.google.com/spreadsheets/d/16J8qxv9-Z0ky35yRFn-OlkuxoRZt5s7XO75kwtsFSoQ/edit?gid=755697593#gid=755697593).

Thank you for your continued support of the team, the principle of fairness within the ecosystem, and the enduring impact of the Ambassador Fellowship.

Ambassador Fellowship: Sprint Team Tip Request - Michelle

Ambassador Fellowship: Sprint Team Tip Request - Luke Schoen

TimedOut

small_spender

The RegionX Hub is a platform that has received positive feedback and requests for improvements. This proposal aims to fund the development of features and improvements to enhance the value of the hub. The proposal focuses on creating an easy-to-use interface for managing Coretime for projects and addressing confusion about the Agile Coretime model. The hub identifies four types of users: existing teams with Polkadot projects, new project teams, Coretime resellers, and enthusiasts. The proposal includes creating user-specific dashboards and help centers, as well as other features like urgent renewals, auto-renewals, and improved transaction status tracking. Development progress can be monitored on the public GitHub repository, and results will be visible on the RegionX Hub website.

Executed

## Overview

With the newly deployed [RegionX Hub](https://hub.regionx.tech/), we have received very positive feedback so far, along with feature and improvement requests — some of which came from Parity and Fellowship members.

We fulfilled the smaller requests and covered the development costs using funds from our previous proposal. This proposal is intended to fund the development of features and improvements that would significantly enhance the overall value the RegionX Hub provides.

With recent incidents, such as failing to renew Coretime on time, it has become clear how important it is to offer an easy-to-use, intuitive interface for managing Coretime for projects. 

We still feel that the majority of the community remains confused about how the Agile Coretime model works, what it offers, and how it can be used for their own purposes. We aim to address this by providing a clear, easy-to-use UI with dynamic dashboards and help centers tailored to specific types of users.

We have identified the following four types of users who use the RegionX Hub:

* **Existing teams that already have a project on Polkadot:** These users are primarily interested in renewing their core in each sale. However, they may choose to purchase a new core from the sale if the price is significantly lower than renewing their existing one. This is why it’s important for them to track both the current state of the bulk sale and the secondary market.
* **New project teams:** Users interested in purchasing a core either from the bulk sale or the secondary market. On the secondary market, it's possible to purchase regions that are usable immediately — unlike on bulk sale, where users must wait for the sale to end, which takes up to 28 days. The secondary market also allows users to purchase only a portion of a core, which is ideal for projects that don't require the full resources a core provides.
* **Coretime resellers:** Users who purchase cores from the bulk sale and sell them on the secondary market for profit. They may also end up partitioning or interlacing the purchased region and selling it that way in the sale.
* **Enthusiast:** Interested in tracking data related to Coretime sales and projects deployed on Polkadot. These individuals can be regular enthusiasts, developers, or investors monitoring Polkadot-related data.

For each user type, we want to establish a help center that provides all the relevant information specific to that user. This way, users won’t be overwhelmed by all the information about Agile Coretime, but will instead see only the parts that are relevant to them.

Also, the user-specific dashboards will display components relevant to the selected user type.

With this proposal, we aim to cover the development costs of delivering major features and improvements requested by the community and identified internally as valuable additions to the RegionX Hub.

Below is a table outlining the features and improvements covered by this proposal.

| Features & Improvements | | |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
| Task | Description | Reporting & Delivery Methods |
| Urgent renewals | From previous experience, we've seen what can happen when parachain teams don’t renew on time. If you're unfamiliar with this event, here are more details: link. Displaying ‘urgent’ renewals on the dashboard can greatly reduce the chances of this happening. Renewals that haven’t been completed but are required in the current sale cycle will be prominently displayed on the dashboard, so users are aware and can warn the parachain teams. | The development of this task can be monitored on the public GitHub repository. The end results can be seen on the RegionX Hub website. |
| Auto renewals | Display which parachains have enabled auto-renewals and whether the parachain account has sufficient funds for the next renewal. The UI will also provide a guide for enabling auto-renewal for a parachain. | The development of this task can be monitored on the public GitHub repository. The end results can be seen on the RegionX Hub website. |
| User specific dashboards | Provide different dashboards with relevant information tailored to each user type\:Existing teams that already have a project on PolkadotNew project teamsCoretime resellersEnthusiast | The development of this task can be monitored on the public GitHub repository. The end results can be seen on the RegionX Hub website. |
| Help centers | Gaining in-depth knowledge of the Agile Coretime model can be overwhelming for most users and also time-consuming.This is why, based on the selected dashboard type, we will provide a user-specific help center that offers only the most relevant information for that particular user type. This will reduce the likelihood of users making mistakes when interacting with the Agile Coretime model. | The development of this task can be monitored on the public GitHub repository. The end results can be seen on the RegionX Hub website. |
| Other features & improvements | Integrate with more multisigs. | The development of this task can be monitored on the public GitHub repository. The end results can be seen on the RegionX Hub website. |
| | Improved transaction status tracking after submitting a transaction | |
| | Ability to connect multiple wallets simultaneously and have access to all accounts at once | |
| | On-chain identity integration | |
| | Batch core purchases | |
| | Light client support | |

Here is the link to the full discussion: [https://docs.google.com/document/d/1yNL\_5FbTSN\_ik68K068W8adepdwUZoFevJG6-n\_4Pbs/edit?usp=sharing](https://docs.google.com/document/d/1yNL_5FbTSN_ik68K068W8adepdwUZoFevJG6-n_4Pbs/edit?usp=sharing)

RegionX Hub: [https://hub.regionx.tech/](https://hub.regionx.tech/)

RegionX Hub – New Features & Improvements

The Big Tipper project is an extension of rfp.fund, which was funded for Kusama with KSM RFP #2. The project aims to unlock multi-sig RFPs for Polkadot, enable bounty curators to associate Child Bounties with RFPs, and deploy an "RFP Board" to consolidate ecosystem RFPs across Kusama/Polkadot Treasuries and Kusama/Polkadot Child Bounties created through the app. The project has a budget of $5,000 for development, $3,000 for UI, $1,000 for supervisors, and $500 for contingency. Supervisors include Leemo and Jay Chrawnna. Excess or unused funds will be returned to the treasury by the supervisors. The timeline includes submission on Big Tipper Track on June 8, development beginning on June 15, UI work starting on July 8, and public launch on AAG on July 16. The project has three milestones: Polkadot Multi-sig RFPs, Child Bounty RFPs, and UI & Mainnet Deployment. The project also discusses the differences between multi-sig RFPs and Bounty RFPs for Polkadot and supports a new Bounty Pallet with multi-asset and cross-chain capabilities.

big_tipper

rfp.fund App - Polkadot, Child Bounty Integration & Public RFP Board.

WAGOI is a project that helps car owners control their car data and make money from it. It works with the EU Data Act and is built on Polkadot. Here are some important points about WAGOI:

1. It lets drivers own and control their car data.
2. Users can manage and sell their car data through a free mobile app.
3. Businesses can get access to this data if the users agree.
4. WAGOI can be the first app to follow the new EU law.
5. It has a big market of over $750 billion and can help Polkadot grow in Europe.
6. WAGOI already has over 1,000 users waiting and partnerships with big companies.
7. They plan to have many more users and business partners in the future.

WAGOI wants to show that Web3 can work well in the real world and follow rules. They want to use Polkadot as a trusted way to do this in Europe.

big_spender

[WAGOI](https://www.wagoi.eu/) is a consumer-first data space built on Polkadot that gives vehicle owners full control over their car data and allows them to monetize it in compliance with the EU Data Act. 

This is **not a concept**. It’s a project with real partners and a direct connection to **a $750 billion regulated market** that touches over 250 million vehicles across Europe.



**Proposal Summary**

* **Project Name:** WAGOI – Opportunity to put web3 at the heart of Europe’s data economy.&#x20;


* **Budget Requested**: $660,000 in 2 milestone-based payments


* **Timeline**: July – December 2025


* **Target Launch**: November 2025 (aligned with EU Data Act)



### **🚘 What is WAGOI?**

* A GDPR and EU Data Act-compliant platform giving drivers **ownership and control** over their vehicle data.


* Enables users to **access, manage, and monetize** car data directly through a free mobile app.


* Offers B2B clients (insurers, garages, leasing companies) **compliant, user-consented access** to verified data.


* Built using core Polkadot tools.



### **📈 Why this matters for Polkadot?**

* **$750B+ market**: The vehicle data economy is rapidly expanding, yet car owners are cut out. WAGOI changes that.


* **Regulatory timing**: The EU Data Act becomes enforceable **November 2025** – timing is everything.


* **First-mover advantage**: WAGOI could be **the first on-chain, real-world compliant app** under the new law.


* **Strategic EU visibility**: A win for WAGOI is a win for Polkadot as a **reference architecture** for Europe’s digital future.

 **🚀 Traction So Far**
* **1,000+ users waitlisted** via the WAGOI website


* **10+ Letters of Intent** from industry partners (automotive, insurance)


* **C-level Advisory Board** incl. Lynk & Co, Nissan, etc


* Tech led by **Blockdeep Labs** 

* Mobile App development by **Pluto Framework** 



### **🔁 On-Chain Impact (Forecast)**

| Metric | 2025 (MVP) | 2026 (1% of EU cars) |
| ------------------------- | ---------- | -------------------- |
| Wallet-linked vehicles | 2,500 | 2,500,000 |
| Monthly tx volume | 15k–20k | 15M–20M |
| Reward payouts (tx) | 7,500 | 7.5M |
| Smart contract executions | 1,000 | 1M |
| Read/write operations | 75k/7.5k | 75M/7.5M |

Projected **\~350k–385k tx/month** by Q2-2026 from 50,000 users and 30–50 B2B clients.



### **📣 Go-To-Market Strategy**

* **B2B2C model**: Partnerships with insurers & leasing firms → access to millions of users


* **Zero CAC (Customer Acquisition Cost)**: No paid marketing  -  warm intros, referrals & partner email campaigns


* **Waitlist active**: Organic user demand already in motion





We’re ready to prove that Web3 can work for real people, in a real market, with real compliance.

Let us bring Polkadot to Europe - as trusted infrastructure !&#x20;

**Here’s the link to the full proposal** - *(please read first before asking questions)* 



[https://docs.google.com/document/d/1djEBO7R7iu0JAFGNIYgCkWKw3LOOk6URLnr\_-5\_TjRQ/edit?usp=sharing](https://docs.google.com/document/d/1djEBO7R7iu0JAFGNIYgCkWKw3LOOk6URLnr_-5_TjRQ/edit?usp=sharing)

 WAGOI – Opportunity to put web3 at the heart of Europe’s data economy. 

The Treasury Proposal is about a collaboration between Mubert Protocol and Pudgy Penguins, powered by Polkadot. Mubert Protocol is building the first data rollup on Polkadot, focusing on streaming and consumable data like AI-generated music. They want to work with Pudgy Penguins, a popular Web3 brand, to host events and increase Polkadot's visibility. 

The main goal is to bring new users to the Polkadot ecosystem through real-world events, AI-driven music, and Web3 culture. They plan to have AI music DJ sets, on-chain music experiences, and community activations in different countries. This will help Polkadot reach a younger audience and show its connection to real-world experiences.

This proposal is supported by the Web3 Foundation, SubWallet, and Mythical Games. It will help grow the Polkadot ecosystem, change its narrative, and bring more users and partners to the network. The events will also help Polkadot connect with other chains and mainstream audiences.

medium_spender

# Treasury Proposal: Pudgy Penguins \<> Mubert Protocol Events Tour, Powered by Polkadot

***

\>>> [FULL PROPOSAL](https://docs.google.com/document/d/17dSg6c-uB7tscMf7G8xbwuMZAxE7VxDMRKDDNQkR5I8/edit?usp=sharing) \<\<\<

***

# **Context of the proposal** 

The motivation behind this proposal stems from the recent milestone achieved by Mubert Protocol-Team in building and launching the first data rollup on the Polkadot ecosystem. With the technical foundations established and early grant support from the Web3 Foundation (large grant from the Web3 Foundation), we seek to amplify our go-to-market strategy by co-hosting a high-impact series of events through a signed collaboration with Pudgy Penguins (also including technological efforts).

1. The origin of this proposal is deeply rooted in extensive ecosystem engagement and strategic alignment between Mubert Protocol, Polkadot, and the Pudgy Penguins brand. After finalizing a Memorandum of Understanding (MOU) with Pudgy Penguins, and working on a detailed Scope of Work (SOW), the opportunity arose to activate the partnership during the **Pudgy Penguins Asia Tour 2025** — a high-visibility, multi-country event series spanning Turkey, Japan, and Singapore (or Seoul).
2. This initiative was discussed across multiple communication channels including Telegram, meetings, and formal MOU negotiations, involving both the Mubert and Pudgy Penguins teams. Early collaboration efforts with SubWallet and Mythical Games (who are building the Pudgy Penguins Game) also played a pivotal role in aligning the vision to strategically showcase Mubert and Polkadot’s synergy during these events. (additionally, positioning Polkadot strategically)

## **Team Background and Motivation**

* **Mubert Protocol / Mubert Inc.**: A company building the first *Data Rollup* chain on Polkadot, focused on streaming and consumable data such as AI-generated music. The platform already boasts 28 million users. (in total 10+ team members)
* **Sarah-Maria Kollnitzer**: A seasoned BD and growth executive with over 12 years of experience in AI and Web3, and a driving force behind strategic partnerships and execution.
* **Alex Mubert**: Founder of Mubert, experienced in scaling B2C products, including Mubert’s user base and protocol roadmap.

The team is driven by the mission to bridge Web2 audiences (such as fans of Pudgy Penguins and AI-generated music) with Polkadot’s innovative infrastructure. Their motivation lies in creating real-world touchpoints, onboarding new users, and increasing ecosystem awareness via music, content, and on-chain engagement. There are **no conflicts of interest or affiliations** with Polkadot governance bodies that may influence this proposal unduly.

## **Ecosystem Alignment and Supporters**

* **Web3 Foundation**: Initial development funding of a large grant&#x20;
* **Pudgy Penguins**: Signed MOU with Mubert Protocol for Asia Tour activations, and integrations, as well as growth efforts.
* **SubWallet**: MOU in progress to integrate Polkadot wallet access for event attendees.
* **Mythical Games**: Collaboration in development to support the Pudgy Penguins game launch.
* **KOLs and Tier 1 VCs**: Planned inclusion through VIP networking events and livestreams. (list to be shared by Pudgy Penguins Team)

Through co-branded livestreams, AI DJ sets, and NFT-to-music demos, this proposal is designed not as a one-off sponsorship, but as a strategic funnel to drive long-term engagement with Polkadot across consumer, developer, and partner audiences.

## **Problem statement** 

Polkadot lacks (to a certain extent) strong visibility in consumer-facing use cases and cultural events (especially in music, and related to creator economy - an audience and target market Gavin Wood is passionate about). Despite having powerful tech, it's still seen as infrastructure-heavy and not connected to real-world, relatable experiences, and leveraging external communities like Pudgy Penguins.

There’s a gap in reaching Gen-Z audiences, creators, and music fans—groups that are already active in Web3 but rarely interact with Polkadot. Competing chains like Solana, SUI, and Polygon are more present in these spaces through events, partnerships, and media.

This proposal solves that by using Mubert’s signed partnership with Pudgy Penguins and upcoming event activations to position Polkadot at the center of high-visibility, creator-driven experiences—bridging a critical adoption gap in Asia and beyond.

## **Proposal objective(s) or solution(s)** 

This proposal aims to co-host and execute three high-impact activations as part of the Pudgy Penguins Asia Tour 2025, with the core goal of onboarding new users to the Polkadot ecosystem through real-world engagement, AI-driven music innovation, and Web3 culture. By integrating Mubert Protocol — the first data rollup on Polkadot — into widely attended events and digital campaigns, we directly link Polkadot to mainstream consumer touchpoints.

### **The Solution**

We’ve partnered with Pudgy Penguins, one of the most recognized brands in Web3 culture, to deliver co-branded event experiences powered by Polkadot. These include:

* AI Music DJ Sets (opening shows at major events) powered by Mubert
* On-chain music experiences linked to NFTs on the Mubert Protocol, powered by Polkadot
* Branded livestreams, panels, and content
* Community activations in Turkey, Japan, Singapore/Seoul&#x20;
 (Side Events, Community Events)
* Lead generation through live demos, IRL booths, and VIP networking

All branding, technology, and content will clearly position Polkadot as the infrastructure behind Mubert Protocol — making Polkadot part of the story, the experience, and the technology.

### **How This Changes the Network**

Today, Polkadot is still perceived as infrastructure-first and developer-focused. This proposal introduces Polkadot to a new, younger, and more mainstream audience — via culture, music, and content. It shifts the narrative from “just a protocol” to a real-world enabler of Web3 experiences.

It also activates Polkadot’s ecosystem partners like SubWallet, Talisman, and Mythical Games in real-life user-facing ways.

### **Who This Helps**

* Polkadot Ecosystem: Gains exposure to 100K–200K new users through livestreams and IRL activations. (estimation on lower end, as with last Livestream series, Pudgy Penguins generated 1m+impressions)
* Developers and Builders: More inbound demand for integrations and partnerships.
* Wallet Providers (e.g., SubWallet, Talisman): New users onboarded directly during activations, connected to Mubert Protocol on Polkadot
* Community: A stronger narrative around what Polkadot can do, not just how it works.

### **What Makes This Different**

We’ve seen Web3 events, NFT parties, and hackathons. But this proposal blends culture and infrastructure — integrating on-chain music, AI, NFTs, and physical events into one unified experience, powered by Polkadot.

### **Impact on the Polkadot Community**

This proposal directly supports:

* Ecosystem Growth: Generating real B2B and B2C leads, increasing partnerships, and onboarding users.
* Narrative Shift: Polkadot is no longer just developer-focused — it’s now part of cultural moments and consumer innovation.
* Onboarding Pipelines: Events are not isolated — they trigger content, email flows, in-app touchpoints, and long-term brand lift.
* Cross-Ecosystem Bridges: Through Pudgy Penguins and creators, we bring exposure across chains, apps, and mainstream audiences.

By tying everything back to measurable results — not just vibe — this proposal aims to deliver lasting ecosystem value.

**Example from Pudgy Penguins:**
[ https://www.notion.so/pudgypenguins/24-Hour-Abstract-Stream-Case-Study-1ce17ff2bdb78020b25cf4c84e1e73d3](https://www.notion.so/pudgypenguins/24-Hour-Abstract-Stream-Case-Study-1ce17ff2bdb78020b25cf4c84e1e73d3)

None of the above positioned a protocol like Polkadot at the center of the cultural moment. This one does.

***

[NOTION PAGE](https://shaded-park-62e.notion.site/pengu-asia-2025) - Pudgy Penguins Events Proposal 

[Twitter Pudgy Penguins](https://x.com/pudgypenguins)   [Twitter Mubert](https://x.com/mubertapp)    [Instagram Pudgy Penguins 
](https://www.instagram.com/pudgypenguins/)[Youtube Pudgy Penguins](https://www.youtube.com/channel/UCh884Rm4plIxpdRG00FDfVg)    [Mubert Instagram](https://www.instagram.com/mubert.app/)   [Mubert LinkedIn ](https://www.linkedin.com/company/mubert/posts/?feedView=all)

[Specific offer, Mubert + Events Plan \<> Pudgy Penguins ](https://shaded-park-62e.notion.site/mubert-ai-60)

[Pudgy Penguins started to position AI Music (Mubert) on official website](https://istanbulblockchainweek.com/blockdown-festival/)

***

\>>> [FULL PROPOSAL](https://docs.google.com/document/d/17dSg6c-uB7tscMf7G8xbwuMZAxE7VxDMRKDDNQkR5I8/edit?usp=sharing) \<\<\<

***

Pudgy Penguins <> Mubert Protocol Events Tour, Powered by Polkadot

The Polkadot Community Foundation (PCF) is a bridge between the Polkadot network's on-chain governance and real-world actions. It helps DOT holders influence off-chain activities. In its first year, the PCF worked on projects to grow the Polkadot ecosystem and market outreach. Now, it asks for more funding to continue its work.

The PCF has goals for its second year, like appointing two DOT directors and creating a transparent information hub. It wants to expand leadership and community engagement. The PCF also needs money for legal and insurance costs.

If the proposal is not approved, the PCF will have to wind down its operations, which could cause disruptions to ongoing projects and the need to find new ways to manage off-chain activities.

In conclusion, the PCF wants to continue helping the Polkadot ecosystem grow by connecting on-chain governance with real-world actions. Approving more funding will allow the PCF to keep doing this important work.

Polkadot Community Foundation (PCF) - Proposal for Renewed Funding for One Year

Gossamer is a team that works on Polkadot Relay Chain Validator using the Go programming language. They want to make the network better by being a full node and a validator node. They are asking for money to keep working on their project for six months. They will focus on building alternative implementations of Polkadot validator, JAM implementation, and improving Collator functionality. Gossamer has received funding before and they want to keep helping the Polkadot ecosystem grow. They will share updates on their progress every month.

Gossamer: Core Contributions to Polkadot [Q3/Q4 2025]

dAppForge is a project that aims to help developers build better decentralized applications (dApps), appchains, and parachains on the Polkadot network. They have completed three out of four milestones for their dAppForge V1.0. Here are the main points of their fourth and final milestone:

1. Improve the knowledge graphs for Solidity and Substrate, with a focus on Solidity and Foundry integration.
2. Integrate Polkadot Hub (AssetHub) documentation to help developers deploy Solidity smart contracts on AssetHub.
3. Benchmark Solidity performance using SolEval and compare it with other AI models.
4. Develop an API to allow developers to use the AI outside the plugin environment, like in bots for Discord/Telegram.

dAppForge's goal is to make it easier for developers to build on Polkadot and attract new developers to the ecosystem. They have a VS Code plugin that supports code generation and autocompletion for Solidity, Substrate, ink!, and Rust. This plugin helps developers understand the code better and build faster.

Hello everyone. This is the treasury proposal for dAppForge milestone 4.

I also did a discussion post before about it: [https://polkadot.polkassembly.io/post/3238](https://polkadot.polkassembly.io/post/3238)&#x20;

# 1. Project 

## 1.1 Summary of Important Points

We submitted a previous treasury proposal, [ref 1343](https://polkadot.subsquare.io/referenda/1343), and [completed all the tasks/milestones](https://x.com/og_tracker/status/1907813586266702158).

Milestone 3 of 4 for dAppForge V1 is now completed. 

Here is our 

* GitHub: [https://github.com/dappforge](https://github.com/dappforge) 
* Website: [https://dappforge.app/](https://dappforge.app/) 
* Here is also a [video of a performance test](https://www.loom.com/share/fe06df5a25934f42b1f59899c41fb570?sid=3a1db0bf-7b6e-4a3f-bb1c-c99f816e4f99) for solidity. 
 * Here is the [Google sheet with prompts](https://docs.google.com/spreadsheets/d/1EodMSMjJ6l49FCabetzZaLwY_Zk3hLW8-OczSM_YXoU/edit?usp=sharing) (link also in video description)

The dAppForge VS Code plug-in supports code generation and autocompletion for Solidity, Substrate, ink!, and Rust. It offers contextual insights into generated code, helping developers deepen their understanding and accelerate development. Each fine-tuned version increases performance and usability, enabling developers to build better and faster. This will lead to more applications being built on Polkadot. 

We have now completed 3 of the 4 milestones to build dAppForge V 1.0. To recap, these are the  4 milestones:

* **Milestone 1 (completed):** the first iteration of LLM ( substrate only) and the VS Code plugin alpha version. 
* **Milestone 2 (**[**completed: ref 985)**](https://x.com/og_tracker/status/1850186240659747303)**:** The product's beta version. It includes a fine-tuned LLM model for substrate, integrated ink!, and a chat feature. 
* **Milestone 3 (**[**completed: ref 1343**](https://x.com/og_tracker/status/1907813586266702158)**):** Added Solidity and Rust.
* **Milestone 4 (current and last treasury proposal):** These are the main points:
 * **Fine-tuning knowledge graphs** for Solidity and Substrate (Solidity will receive additional focus, including [Foundry](https://book.getfoundry.sh/) integration).
 * **Integrate Polkadot Hub (AssetHub) documentation** to enable developers to deploy Solidity smart contracts on Polkadot Hub (AssetHub). This is crucial considering the launch of Solidity smart contracts on AssetHub in Q3 2025.
 * **Benchmarking Solidity performance** using [SolEval](https://arxiv.org/abs/2502.18793) to compare dAppForge with other AI models like Claude. Results will be published on our site. 
 * **API Development** to enable developers to use the AI outside the plug-in environment (e.g., bots for Discord/Telegram). This will include a freemium model for broader accessibility.

## 1.2 Overview 

**Tagline:** AI-powered plug-in for Polkadot developers that reduces development time. 

**Brief description:** Building on Polkadot is complex, creating a high barrier to entry. dAppForge aims to enable Polkadot developers to build better dApps, appchains, and parachains faster, lowering the entry barriers for new developers. The model can be used for code generation and autocompletion. It provides insights into the code generated, which helps developers increase their understanding of the programming languages. 

We have integrated Solidity and now aim to enable developers to deploy Solidity smart contracts on the Polkadot Hub (AssetHub) once Plazza is completed in Q3 2025. 

**Motivation:**  Polkadot has the second-largest developer ecosystem and consistent growth in developer activity. dAppForge aims to empower existing developers and make it easier for new developers to join and build on Polkadot. With the launch of smart contracts on AssetHub, we want to make it as easy as possible to onboard this new category of developers (smart contract developers) into the ecosystem. 

Here is the complete proposal:

[https://docs.google.com/document/d/1t2D5w6yXkJwcHO4yYZRjyhyrIbmGsavGxePbufmXMRs/edit?usp=sharing](https://docs.google.com/document/d/1t2D5w6yXkJwcHO4yYZRjyhyrIbmGsavGxePbufmXMRs/edit?usp=sharing "Here is the complete proposal")

dAppForge Milestone 4 

This proposal is about fixing two problems with bounties on Polkadot.

1. Curators were removed from some active bounties by mistake. This let someone else remove them with mean comments. The proposal wants to put the original curators back for three bounties:
   - Open Source Developer Grants Program (Bounty 59)
   - Games Bounty (Bounty 38)
   - Polkadot Pioneers Prize (Bounty 10)
   
   The teams working on these bounties agree with this change. In the future, a new update will let bounties last forever, so curators won't need to renew their role.

2. The proposal also wants to clean up some bounties that are not active anymore. These bounties will be closed because they have been inactive, don't have enough money, or don't have enough information. The bounties to close are:
   - Bounty 42
   - Bounty 60
   - Bounty 61
   - Bounty 65
   - Bounty 66
   - Bounty 68

treasurer

Curator Reinstatements & Bounty Housekeeping

- Snowbridge is a bridge for Polkadot that connects to Ethereum and other networks.  
- It helps move money and messages safely between different blockchains.  
- The team is focusing on growth to bring more value to Polkadot.  
- Costs for 2024 are about $2.2 million, with plans to lower costs in the future.  
- Snowbridge has helped connect 24+ projects in the Polkadot ecosystem.  
- It currently holds over $60 million in value (TVL).  
- The team is asking for $5 million to continue their work.  
- They support other bridge projects like Hyperbridge too.

# June 18 Updates:

We've been speaking to various stakeholders and taken note of the comments above. We’d like to share a few updates and changes to the proposal that we believe address concerns and align our team’s efforts with growth and TVL creation for Polkadot. The updates fall into three areas:

# **1. Growth and Value Creation**

To date, our roadmap has blended engineering and BD. Going forward, we’re shifting focus **primarily toward growth and ecosystem value creation** to increase Polkadot TVL.

We’ve published an updated roadmap highlighting concrete growth initiatives:

## 👉 [https://www.notion.so/snowfork/Snowbridge-s-Plan-for-World-Domination-210296aaabef80edaa90dc9426375f68](https://www.notion.so/snowfork/Snowbridge-s-Plan-for-World-Domination-210296aaabef80edaa90dc9426375f68)

With the upcoming launch of Snowbridge V2, we also commit to connecting Snowbridge with all major Ethereum L2s — including Optimism, Base, Arbitrum, Unichain, and more — for seamless messaging and asset transfer with more high-liquidity ecosystems.

# **2. Cost Model & Incentives**

## **Costs**

A common theme in feedback was cost transparency — here's a breakdown:

* **2024 Costs: \~$2.2M**
 * Covers a 5-person team, travel, infrastructure/relayers/gas, audits, software, and legal/admin/payroll/accounting company margins.
* **2025 Projections:** Similar costs, focused on growth engineering, developer advocacy, and ecosystem support.
* **Longer-Term:** We expect to gradually downsize into maintenance/support mode at **\< $1M/year**, and even lower once the Polkadot Hub / Bridge Hub merge matures. The long-term cost to the treasury should be minimal unless further growth is pursued — which would be optional.

## **Incentives**

**Proposal Breakdown ($5M):**

* **$1M:** Milestone Vesting *(this is for work already completed 2 years ago, still vesting due to us agreeing to a 2-year vesting period)*
* **$300k:** Failed payment
* **$3.7M:** Long-term incentive funding

The **2025 incentive ask is effectively $1.5M** over and above our base costs.

We believe this is fair: the incentive structure was set 4 years ago, passed via multiple governance votes, and was based on concrete deliverables — notably, integrations across the ecosystem. The goal was 9; we did heavy B2B marketing and BD work and **we’ve delivered 24+,** and aided in wider Asset Hub and XCM adoption efforts.

**Snowbridge also ranks #2 in TVL across all Polkadot protocols, second only to Hydration.**

While \~$60M TVL is just a start, we’re aligned with the community in pushing that higher this year. Reducing pre-agreed and achieved incentives at this stage would feel like a rug pull — but we're committed to making things work and believe the shift to growth focus reflects that.

# **3. Comparisons and Context**

We’ve also seen questions about how our funding compares to others:

When Snowbridge began, other bridge projects were raising $10M+ with token upside in the tens of millions. We had similar offers — but chose instead to build Snowbridge as a **public good**, foregoing tokenomics and focusing on light-client integrity and Ethereum interoperability, which we believe serves Polkadot best.

Closer to home, Hyperbridge raised \~$6M, and their 20% team token allocation is likely to result in $10M+ total with even a modest token market cap.

Note: We do fully support Hyperbridge. We share a belief that well-funded core infrastructure efforts are still positive-sum for the ecosystem and we’re simply highlighting this to provide context for our proposal ask, which remains in line with or even below market norms for teams delivering comparable value.

Let us know if any parts require further clarification. We're committed to aligning our work with the network's needs and believe this proposal represents a reasonable and mutually beneficial path forward.

***

# Original Post

# **Full Proposal:** [**https://snowfork.notion.site/Snowbridge-2025-2026-Milestone-Payouts-1f2296aaabef803391dde2cfba18a7d6**](https://snowfork.notion.site/Snowbridge-2025-2026-Milestone-Payouts-1f2296aaabef803391dde2cfba18a7d6)

## Overview

Snowbridge ([https://app.snowbridge.network/](https://app.snowbridge.network/)) has now been live for almost a year, running successfully with no on chain issues and zero on chain downtime. It’s the longest running and most complex public goods project in the Polkadot ecosystem outside of Parity itself and since launch has become critical to the Polkadot ecosystem.

Snowbridge is the only fully trustless bridge in the ecosystem - meaning it is both fully governed by Polkadot itself and fully owned by the Polkadot Treasury as a system that can facilitate further growth and value flow into the treasury.

*(For a deeper dive into Snowbridge’s purpose and value to the Polkadot ecosystem, see the **“Purpose”** section in our* [*original funding proposal*](https://spinamp.mypinata.cloud/ipfs/QmehcCU8LjXRpj962YZYVJfHzwecvvdxbRH9BMEmiumcb9)*)*

Since our launch, we've seen:

* **Total Value Locked (TVL):** \~$63M
 * Top Assets: MYTH, KILT, TBTC, AAVE, WETH, ETH, wstETH
* **Ecosystem Integrations:** \~24 different integrations with parachains, wallets, apps, and other services across the Polkadot ecosystem. We’ve detailed all of these in the full proposal, but they include:
 * Helping Mythical launch their parachain, bridging over all their ERC20 tokens
 * Hydration integration with plans for their upcoming incentive program.
 * Major efforts towards Polkadot hub, integrating with Asset Hub and driving adoption of Asset Hub along with support in developing wallet integrations
 * Collaboration on design of XCMv5 and supporting XCM adoption in general.
 * StellaSwap integration and their newly launched liquidity program&#x20;

We’re also expecting a burst of additional TVL soon, as some new key assets and stablecoins will soon launch on Hydration and other chains.

## **Year in Review and Purpose of Proposal**

Our team has continued to ship tons of features and improvements for Snowbridge over the last year including significant cost and performance improvements, developer tooling for integrations and a major re-architecture into Snowbridge V2 for much improved arbitrary messaging support.

Our [original proposal](https://polkadot.polkassembly.io/post/1341) was in 2022, where our team and the Polkadot community agreed upon an expected milestone payment plan and incentives for the long-term project. This led to the successful development and launch of Snowbridge, and our [follow up proposal](https://polkadot.polkassembly.io/referenda/944) last year kicked off those milestone completion payments which have been unlocking monthly over the last year.

This proposal covers the next year of spends for the final 12 milestone payments and team incentives from June 2025 to June 2026. It also renews the insurance and bug bounty programmes that we put in place last year for further incentive alignment.

Our team has continued to deliver improvements over and above those in our milestones and we’ve become involved in a myriad of efforts that have brought significant value to the wider Polkadot ecosystem beyond just for Snowbridge. This proposal reviews our past year and suggests a continued roadmap with growth plan efforts for the coming year.

We'd also love to get early feedback from the community with regards to our future plans and opinions on how Snowbridge should continue to grow and evolve in ways to bring the most value to the Polkadot community - our team is committed to keep delivering value and if any further ideas come up for our roadmap, we'd love to consider them!

## Payment Overview

**Total amount:** 254,064 DOT and 4,062,500 USDC *(\~5M USD, based on the current Coingecko price of 4.10, with a 10% buffer for slippage)*, broken down into:

* **Milestone completion bonus:**
 * 21,172 DOT unlock per month from June 2025 to June 2026. Total 254,064 DOT *(based on $937,500)*.
 * Covers our final 12 months expected payouts for completed engineering and launch milestones
* **Successful operation incentives:**
 * 156,250 USDC & 156,250 USDT unlock per month from May 2025 to June 2026. Total 4,062,500 USDC.
 * Covers our final 13 out of 21 months payouts. *(based on the schedule agreed upon in our original proposal for longer term success in maintenance and development work on the bridge)*
* **Insurance and Bug Bounty:** The above milestone and operation incentives will also be allocated to be used for bridge insurance and bug bounty payments until they unlock.

**Beneficiary Address:** 129Uxho5oKBz6js8dwjoQLzLjYsEs4ZLBtS7KRotQbunVNfP

Snowbridge 2025/2026 Milestone Payouts

- Merkle Science is helping Polkadot's Asset Hub with compliance and security.  
- They want to make Polkadot safer for big companies and users.  
- This will help Polkadot grow in DeFi (decentralized finance).  
- They are working with Velocity Labs to bring in financial institutions like Crypto.com.  
- Their goal is to meet international rules and protect money.  
- They shared a proposal and are asking for community support.  
- You can learn more on their website or contact them.

In the spirit of open governance and collaborative development, we are excited to share our **Medium Spender Proposal** with the Polkadot community.

Over the past months, **Merkle Science** has been approached by the community, **Parity**, and the **Web3 Foundation** to support the next growth chapter of the Polkadot ecosystem—**the Asset Hub**.

Merkle Science will provide the Asset Hub with essential compliance and security capabilities—**removing critical barriers to institutional adoption**, **protecting users**, and unlocking Polkadot’s next phase of **DeFi innovation**.

Merkle Science is supporting the launch of the Asset Hub by helping financial institutions and startups meet international compliance standards—**unlocking their ability to build and deploy capital within the Polkadot ecosystem**. To ensure this growth is sustainable and trusted, Merkle Science is simultaneously enhancing security by providing cross-chain tracing solutions that address key gaps flagged by Parity, such as those exposed in the Parallel Finance exploit. This added layer of security complements the compliance framework by protecting institutional capital and fostering a safer environment for innovation.

**UPDATE June 23, 2025:**

We are delighted  to inform you that we have acted upon the feedback from the Community to work with the Polkadot BD team [Velocity Labs](https://www.velocitylabs.org/) to secure the onboarding of the mentioned financial institutions. More specifically, we are delighted to share that we are close to securing the onboarding of [crypto.com](http://crypto.com/) if our proposal 1586 is successful. We are actively working with Velocity labs to coordinate this project. We hope this demonstrates our commitment to driving the support of the Polkadot hub and we hope to be able to secure your approval after securing this significant milestone.

Proposal: [https://docs.google.com/document/d/1t\_cB5607bR6JZWOjwbLkdvG7UZzoHyjWNgV40tg6-bs/edit?usp=sharing](https://docs.google.com/document/d/1t_cB5607bR6JZWOjwbLkdvG7UZzoHyjWNgV40tg6-bs/edit?usp=sharing)

Discussion:

[https://polkadot.polkassembly.io/post/3232](https://polkadot.polkassembly.io/post/3232)

Contact: [justus.delp@merklescience.com](mailto\:justus.delp@merklescience.com), Solutions Architect

Element Handle: @merkle\_science\_official

Learn more: [https://www.merklescience.com](https://www.merklescience.com/)

Merkle Science paving the way for Institutional Adoption and DeFi Innovation

Avatar Accounts is a technology that allows users to interact with Polkadot SDK parachains directly through their existing Ethereum wallets. This means no downloads, new keys, or friction. It is a plug-and-play solution for builders using a simple Substrate pallet and JavaScript SDK. The proposal aims to fund the next 6 months of development, support, integrations, and GTM efforts to bring Avatar Accounts to multiple parachains and dapps.

The team behind Avatar Accounts has experience in both Ethereum and Polkadot ecosystems. They won ETHIndia 2022, the world's largest Ethereum hackathon, and are Polkadot Blockchain Academy graduates. The team lead, Tushar Ojha, is an ETHIndia Fellow and has been building in the Polkadot ecosystem for years.

For more information, you can visit their full proposal, watch a 1-minute explainer video, see a demo video, or check out their slides. The team can be contacted through Tushar Ojha, the founder of True Network.

Avatar Accounts: Bringing The Whole Web3 To Polkadot

This proposal asks for 1,200,000 DOT to extend the Polkadot Marketing Bounty for six more months. The current Marketing Bounty has saved a lot of money, going from spending $16.10 million to $4.47 million, while keeping the administrative costs at 4%. They have worked on many projects with different groups and companies in 19 countries. They have made the Polkadot name more popular and worked on many marketing and communication projects. They have also made important partnerships with companies like BLAST Premier and Serotonin. They want to keep getting money to help launch the Polkadot App and other projects. They are also adding two new people to their team to help with their plans.

Marketing Bounty Refill May 2025

The Gitorial VS Code Extension is a new tool that helps developers learn and build projects using step-by-step tutorials directly within Visual Studio Code. It was created to solve the problem of disjointed learning experiences in fast-paced ecosystems like Polkadot. The extension is integrated with Git, making it easy to follow each step and maintain accurate information. It also helps developers be more productive by giving them immediate access to language servers and code execution within the IDE.

The Gitorial VS Code Extension was built in collaboration with Shawn Tabrizi and Batman from DotCodeSchool. They are working on integrating the extension with their platform and planning future updates, like creating and editing tutorials directly in VS Code.

The proposal asks for funding to cover the initial development and launch of the extension, as well as minor improvements and bug fixes. The total cost is 1660 DOT, which is about $7,470. The money will be split between two proponents, with one receiving 1560 DOT and the other receiving 100 DOT. The hourly rate for the work is $90/hr, and the total time spent on the project is 83 hours.

You can try out the Gitorial VS Code Extension and explore the spec draft using the links provided. The creators, Andrey Dodonov and Andrzej Sulkowski, are graduates of the Polkadot Blockchain Academy.

[Retroactive] Funding for Gitorial VS Code Extension (Interactive Git Tutorials)

This proposal has been created accidentally.
Please ignore

Ignore

Polkadot-sdk has a security issue. A fix is being made with a runtime upgrade. The upgrade is on the Whitelisted Caller track, which means the Fellowship will vote on it. You can review and vote when you have time. More information about the issue and fix can be found in a post-mortem report.

whitelisted_caller

[Whitelisted Caller] Runtime Upgrade to v1.5.1

- **Epico** helps Polkadot chains work with Ethereum wallets like MetaMask.  
- No need for new wallets or plugins—users can use their existing Ethereum accounts.  
- Makes Polkadot apps easier to use for Ethereum users.  
- Already tested with 5 interested teams, including Mythos and Frequency.  
- Demo shows it working smoothly.  
- Open-source release planned with guides and support.  
- Budget: $246,330 USDC for development and maintenance.  
- Goal: Bring more users to Polkadot by simplifying wallet access.

## <img height="351" width="624" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfTkJDeeH4qaPCgShb4I0ToGhA6HJMTI-WMWdcJ4_wwRf7nJ0aXBIiWeZxg0Wp7T37Bij5HCp_5g_gZ83TG6lQUu1WqXTeb7dl75NOq_5hqxzWop1oSk3tJ6Km3F4AznUZwYajV7w?key=FSdueCfSwPsfw-tX90v8eusb" />

## Table of Contents

* TL;DR
* Interest Received
* Details
* What Epico Enables
* Demo
* Epico Limitations
* Ecosystem Impact and RoI
* Proposed Funding Model
* Scope of Work
* Out of Scope
* Our Past Work
* Duration and Timelines
* Contact
* Budget

## TL;DR

### Brief

We are seeking Polkadot Treasury’s support for the development and open source rollout of Epico — an Ethereum wallet compatibility layer for the Polkadot SDK. Epico will enable Polkadot SDK chains to seamlessly interface with Ethereum wallets — without the need for EVM emulation, or wallet plugins (snaps).

### Scope of Delivery

* Epico source code
* Integration guides
* Technical Support for 3 months

### Budget

$246,330 USDC

## Interest Received

We announced Epico and published a recorded demo right before EthDenver 2025 (late February), and spoke with several parachain teams during and after EthDenver for potential integration of Epico in their chains. We have received interest from 5 teams so far, 3 of which are listed below and the other two didn’t wish to be named in the proposal.

* Mythos
* Frequency
* Polimec

As and when we publish the Epico source code and integration guide, we expect more teams to adopt the solution in their Polkadot SDK based chains.

We also received the following words of support from Mythos and Frequency:

“*At Mythos, our mission is to lower the barriers to Web3 adoption starting with gaming, but extending to the broader ecosystem. A key part of that is meeting users where they already are. By enabling Ethereum RPC compatibility via Epico, on the Mythos parachain, we make it possible for millions of users to interact using wallets they already trust, while still benefiting from the throughput improvements of Substrate. This would significantly reduce friction and open up seamless access to the MYTH token, whether on Ethereum or within our parachain.*” - Cameron Thacker, VP, Mythical Games

“*The Frequency core contributors support this proposal. We believe there is a requirement for interoperability with the Ethereum community for the success and expansion of the Polkadot ecosystem. We also see this as a perfect pairing with the ongoing work on Pallet Revive. Epico has the chance to accelerate the rollout of Ethereum RPC compatibility for Frequency, a major goal for us this year. We have previously had great experiences with BlockDeep, including the code reviews they did for Frequency, and have confidence in BlockDeep’s ability to deliver the work for this proposal.*” - Harry Evans, CTO, Project Liberty

## Details

One of the largest barriers to mainstream adoption for Polkadot-based chains has been the unfamiliarity users face when interacting with Substrate-native accounts and wallets. The majority of crypto users today, especially those coming from Ethereum and EVM-compatible ecosystems, rely on MetaMask and other Ethereum-centric wallets as their default gateway into Web3.

The following graphs show absolute domination of MetaMask, sourced from [Dune dashboard: Wallet War](https://dune.com/hashed_official/wallet-war)

<img height="307" width="624" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfZ3dswfP9dW2cvDzR5-DB4RDFSqL20nQqlvQpY92JEn4de9o0pPJOMgvlgX5oUTsPV_Z4rpfBdn5303RIPbqiwN8VVfv4-l77CyQqqsMhbZSkM5gAmz89tXoMXXD2_GNBUYGvn8Q?key=FSdueCfSwPsfw-tX90v8eusb" />

<img height="231" width="624" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdoJSL9BRCXSh80qQag0ny8TJDwbtVCgpiP8PGgoIxOzpCfD-9X7Mka-fZeJZch03xGCj27_lgWodjUjA1ZCLzpZ9dd1ML2mP1RtI4F5VcwzgLknt9FgPPNtW27vb1SotS7YKsG?key=FSdueCfSwPsfw-tX90v8eusb" />

Epico directly addresses this challenge by enabling users to sign and send transactions using their existing Ethereum wallets like MetaMask to Polkadot SDK chains, without needing to install snaps (plugins) or understand new account formats.

## What Epico Enables

* MetaMask and Ethereum Wallet Support: With Epico, any Polkadot SDK chain that integrates the solution will allow users to connect using their Ethereum accounts and sign transactions via MetaMask and other Ethereum wallets — just as they would on any EVM chain.
* Familiar UX for New Users: Users will no longer need to manage separate Polkadot-specific accounts or learn new address formats. A single Ethereum wallet address can now interact with both Ethereum and Polkadot-based applications on chains that adopt Epico.
* Frictionless Onboarding: Whether a user is exploring DeFi, NFTs, games, or decentralized identity apps on Polkadot, Epico allows them to skip the typical onboarding hurdles like creating new wallets, backing up new seed phrases, or converting assets via bridges.

## Demo

We integrated Epico with a solo-chain node and recorded the following fully functional demo. We encourage the community to take a look at the demo before casting their vote.

[https://www.youtube.com/watch?v=CS74zbi9OYI](https://www.youtube.com/watch?v=CS74zbi9OYI) 

## Epico Limitations

\[UPDATE]: **In light of [Polkadot SDK PR 8757](https://github.com/paritytech/polkadot-sdk/pull/8757), Substrate accounts can be deterministically represented as Ethereum addresses. As a result, Epico’s previous limitation of working only with native Ethereum accounts no longer applies.**

In its current form, Epico focuses on enabling seamless interaction between MetaMask (and other Ethereum-compatible wallets) and Substrate-based chains. This is achieved by integrating chains that natively support Ethereum-style accounts (such as Mythos).

However, chains that exclusively use Substrate’s account format (AccountId32) do not yet benefit from Epico. To address this limitation, we’ve been actively exploring solutions that would allow Substrate chains to support Ethereum accounts while maintaining full backward compatibility with their existing native account systems.

One approach involves leveraging Ethereum accounts as proxies for Substrate accounts — a mechanism we have already successfully demonstrated in our [smart accounts project, Otro](https://blog.blockdeep.io/introducing-otro-substrate-smart-accounts-ff56179f2f10).

## Ecosystem Impact and RoI

Epico is built with one clear goal: to remove the invisible walls between the Polkadot and Ethereum ecosystems from the user's perspective.

By allowing users to access Polkadot-based chains and applications directly through MetaMask and other Ethereum-compatible wallets, Epico will:

* Make Polkadot-based apps immediately accessible to the largest wallet user base in the blockchain ecosystem.
* Reduce the learning curve and eliminate the need for new wallets, boosting adoption of both new and existing dApps built on Polkadot SDK.
* Encourage broader user engagement in the Polkadot ecosystem by removing the need for wallet switching.

### Potential RoI

Epico is focused on improving user experience by enabling access to Polkadot-based apps using wallets people already use. [MetaMask alone has over 30 million monthly active users (as on Jan 2024)](https://blockworks.co/news/metamask-monthly-active-users-blockaid). With Epico, a good part, if not all, of those users will be able to use their Ethereum wallets to interact with Polkadot chains, without installing new tools or learning new formats.

This can lead to:

* More users trying and staying with apps built on Polkadot.
* Easier onboarding for dApps and better conversion from marketing efforts.
* Better cross-ecosystem liquidity and network effects.

Our strategy includes two parts:

* Build a reliable, well-documented tool that is easy to integrate.
* Work closely with parachains and dApp developers to promote real-world use cases and adoption.

Our goal is not just to publish code, but to enable meaningful adoption that brings more users and activity into the Polkadot ecosystem.

## Proposed Funding Model

Our proposal differs slightly from most others seeking prospective or retrospective funding. Epico was built over the course of several months — from initial analysis and design to development and testing. It has been an iterative journey, during which we explored multiple approaches before arriving at a solution that truly works.

Once the technical work was complete, we began evaluating potential ways to sustain and distribute Epico. One option was to adopt a closed-source, per-integration licensing model, allowing teams building on Substrate to purchase access. The alternative was to open-source the project and rely on retrospective funding.

The first path would require significant time spent on sales cycles, which we felt would divert our focus away from what we do best — building and improving the technology. The second path risked turning the project into an unmaintained code dump if retrospective funding didn’t materialize, which would ultimately not result in a useful solution.

Instead, we’ve chosen a middle-ground approach: one that allows us to deliver polished, high-quality code while ensuring support and maintenance. We are committed to open-sourcing Epico under the Apache 2.0 license upon completion, giving the community full access to the codebase.

Upfront funding will enable us to finalize the remaining work: cleaning up the code, writing comprehensive documentation, conducting peer reviews, and ensuring alignment with ecosystem standards. This ensures the project will be released in a state that is truly useful, reliable, and maintainable from day one.

We believe open-sourcing without proper funding risks leaving behind incomplete or poorly documented code, which can create more confusion than value for the ecosystem. Our goal is to avoid that by releasing a professional, well-supported open-source project — not just publishing a code dump.

## Scope of Work

* Completion of Epico core features. Open-sourcing of the entire codebase.
* Documentation, tutorials, and integration guides to streamline adoption by parachain and solo chain teams.
* Fully functional demo with Epico integration and a demo UI for anyone to try it out.
* Technical support/advisory for the first 3 months (after open sourcing) to any team who intends to integrate Epico in their chain.
* Maintenance and update to latest Polkadot SDK quarterly releases for at least 6 months. 

## Out of Scope

* Security audits are out of scope of this proposal. However, we will approach PAL for audits, or may create another proposal for that if needed.
* Development effort for integration with specific chains is out of scope, however we commit to providing technical support for integration as mentioned in the scope section above.

## Our Past Work

In our \~1 year of operations so far, BlockDeep Labs has delivered the following to the Polkadot ecosystem:

* Development and migration of [Mythos parachain](https://blog.blockdeep.io/bringing-mythos-to-polkadot-the-mythical-games-parachain-development-story-b6450374c3a2) (funded by DF program).
* [Delivery of Ecosystem Services](https://blog.blockdeep.io/blockdeep-labs-ecosystem-services-delivered-d4e3b25de82c) as part of our last treasury proposal.
 * In-depth code reviews for 20 teams
 * Detailed [Polkadot SDK best practices book - Libro](https://libro.blockdeep.dev/)
 * [Delivery Partners Program](https://blog.blockdeep.io/launching-the-delivery-partners-directory-394a0dfad607)
 * [Release analysis reports](https://forum.polkadot.network/tag/release-analysis)
* Development of [Smart Account Abstraction](https://blog.blockdeep.io/introducing-otro-substrate-smart-accounts-ff56179f2f10) and [XCM Tracer](https://blog.blockdeep.io/introducing-xcm-tracer-a0889c1397ab).
* Currently under development - [RFC-0097: Fast Unbonding of Staking rewards](https://x.com/0xBlockDeep/status/1924910399750549562).
* Advisory to several pre-launch teams building in the ecosystem.

## Duration and Timelines

* Epico source code, integration guides, documentation, and demo will be delivered within 3 months of this proposal passing.
* Technical support will be provided for 3 months after open sourcing the code.
* Maintenance and upgrades to Polkadot SDK quarterly releases will be provided for 6 months after open sourcing the code.

## Contact

* Email: [info@blockdeep.io](mailto\:info@blockdeep.io)
* Element (Technical Support): [`https://matrix.to/#/#epico-blockdeep:matrix.org`](https://matrix.to/#/#epico-blockdeep\:matrix.org)
* Telegram: @web3gautam (Founder, BlockDeep)

## Budget

This section outlines the scope of work completed, remaining tasks, and projected support requirements for the Epico project, along with associated costs.

### Time and Resources

So far, we’ve already spent \~185 person-days (roughly **1.5 FTE** for **\~5 months**) of effort on the tasks detailed in the section below. The FTE working on Epico are **senior Rust engineers** with experience on Substrate and Ethereum both. In addition, there was some oversight and architecture effort from a team lead/manager, and some PM effort for coordination.

### Tasks Completed

* Detailed analysis of all standard Eth RPCs.
* Analysis of API calls made by MetaMask.
* Analysis of Frontier project and identification of reusable components for Ethereum signatures support.
* Designing Epico on-chain and off-chain (node side) components.
* Designing of Epico DApp side components (JavaScript snippets).
* Solving efficient storage for transaction receipts. This was a heavy design effort considering Substrate does not have transaction receipts by design.
* Detailed analysis of Ethereum Gas and Substrate Weights, and a conversion mechanism for RPC APIs. This required quite a bit of trial and error to find the right conversion ratio. We wrote a detailed [blog post](https://blog.blockdeep.io/ethereum-gas-vs-polkadot-weights-a-comparison-51303ec36fea) about it too.
* Development and in-depth testing of all components:
 * RPC implementation
 * Gas conversion
 * Transaction wrapper
 * Signature verification
 * Transaction receipts
* Integration with parachain and solochain node templates.
* Reorganizing and packaging rust code into easily usable crates.
* Building an end to end demo for users to click through and try.

### Future Tasks

We require another 20 person-days of effort for the following tasks:

* Code reviews (not security audits)
* Documentation and integration guides
* Polishing and deployment of the demo

In the future, to provide technical support to teams integrating Epico in their chains, we estimate a total of 25 person-days of effort spread over a 3 month period.

### Cost Estimates

**Total Effort:** 230 person-days

**Daily Rate:** USD 900 (\~ EUR 800 per day or **EUR 100 per hour**)

**Sub Total (230\*900):** $207,000
A detailed breakdown of the budget is available [here](https://docs.google.com/spreadsheets/d/1nUjZZgUObIGSVA8EwpOFfsKqxvdvQoRHAcMH8bxvjbs/).

**German VAT at 19%:** $39,330
Note about VAT: BlockDeep is a German company, with registered address in Berlin. We have to report all company income in our VAT returns as per law. Considering, in this case, the recipient of our services is Polkadot Network Treasury, which is a decentralized entity without any registered address, we have to report and file full VAT for this treasury payment. Please see a relevant discussion on this [Polkadot forum post](https://forum.polkadot.network/t/vat-on-services-in-to-the-ecosystem/2119/6?u=gautam), which is also applicable for other EU countries.

**Total:** $246,330 USDC

Thank you for considering our proposal. We're happy to answer any questions and provide further details as needed. Looking forward to engaging with the community and moving Epico forward together.

Epico: Ethereum Wallet Compatibility for Polkadot SDK Chains

A proposal called Ref 703 was made to get money for a project, but the people who asked for the money missed the chance to get it. They made a new proposal to fix this problem and get the money they were supposed to get. They already did the project, which was a big success. They want to make sure they get the money they were promised, and they are asking for help to fix this mistake.

TL;DR

The payout for [Ref 703](https://polkadot.polkassembly.io/referenda/703) expired before we could claim. This ref intends to rectify the payout that was originally approved under Ref. 703.

The preimage was pulled as an additional measure to prove that the payout was not disbursed.

**Q: Why was the payout not claimed?**

A: Due to an oversight on our part, we failed to track the timeline properly and missed the deadline to claim the payout.

**Q: What is the purpose of this proposal?**

A: Since the claim on our previously approved proposal has expired, we are currently unable to claim the originally approved funds. We are submitting this proposal to rectify this so that we may continue to deliver on the original proposal.

**Q: Are you still planning to fulfill the proposal?**

A: Absolutely, we executed in any case, and the Scalability Hackathon has been a big success.

**Q: Can you verify the payment address?**

A: Yes, the payment address is an Encode-controlled address, identical to the one used in the original proposal.

Your vote will accelerate the rectification of this payout previously approved. Thank you for the support! 🙏❤️

Full proposal here: [https://docs.google.com/document/d/1P-LiroEAL1Sdqum-vsHug1ab2lPFjETWOAoh6fNkLxg/edit?usp=sharing](https://docs.google.com/document/d/1P-LiroEAL1Sdqum-vsHug1ab2lPFjETWOAoh6fNkLxg/edit?usp=sharing)

Payout approved by Ref 703 expired - Encode Club

Project "Fund the World" is a proposal to integrate a funding application into the Polkadot ecosystem. The goal is to create a registry of Polkadot projects seeking support, increase their visibility, and drive ecosystem growth. The team behind the project includes Frank Dierolf, a senior Polkadot developer, Trevor Parks, a founder focused on Web3 applications, and Watson Lewis-Rodriguez, a cross-chain developer. The project has a 2-month timeline with objectives such as creating a comprehensive directory, developing customized components, building a metadata enhancing system, and connecting donors and job seekers with projects. Expected outcomes include a comprehensive registry, enhanced visibility, developer onboarding, and ecosystem partnerships.

**Prepared by**: Frank Dierolf, and Trevor Parks, Watson Lewis-Rodriguez&#x20;
**Account Address**: 5EqCSiiLohswtoquksJCDoY7RvkQNjt9yoyczdeje2AXSwYE
**Project Website**: [https://fundtheworld.arthurlabs.net/](https://fundtheworld.arthurlabs.net/)

## Definition

For the purposes of this proposal, "Project" refers to any startup, mini-application, independent builder, collective, organization, charity, or group within the Polkadot ecosystem.

## Summary

Our team requests funding to integrate our "Fund the World" application (launched at Bitcoin Vegas in May) to the Polkadot ecosystem. We aim to create a comprehensive registrar of Polkadot Projects seeking support, increasing their visibility, facilitating connections, and driving ecosystem growth.

## Our Team

* **Frank Dierolf**: Senior Polkadot developer with strong European ecosystem connections (https://gitlab.com/frankbevr)
* **Trevor Parks**: Founder focused on creating elegant Web3 applications (https://github.com/trevorparks)
* **Watson Lewis-Rodriguez**: Cross-chain developer with extensive Web3 experience (https://github.com/5eh)

## Project Objectives (2-Month Timeline)

1. Create a comprehensive directory of Polkadot ecosystem Projects with in-depth contextual data
2. Develop customized components that funnel viewers directly corresponding applications
3. Build a metadata enhancing system for Projects to improve their search engine visibility
4. Connect potential donors, volunteers, and job seekers with Projects matching their personal interests

## Deliverables & Timeline

### Month 1

* **Project Database Development**
  * Create detailed profiles of active Polkadot ecosystem Projects
  * Integrate treasury wallets for optional direct donations and transactions
* **User Experience & Interface**
  * Develop interactive components to drive viewer engagement
  * Design conversion funnels to increase Project interactions
* **Community Building**
  * Establish dedicated social media accounts focused on Polkadot Projects
  * Cross-promote participating Projects to increase visibility
* **Educational Resources**
  * Create onboarding guides for new Polkadot developers
  * Develop resources to lower barriers to ecosystem participation

### Month 2

* **Project Launch Preparation**
  * Finalize and announce verified Project listings
  * Coordinate with ecosystem influencers (e.g., The Kusamarian, WebZero)
* **Content & Communication**
  * Implement ongoing weekly newsletters highlighting new participants
  * Generate tailored Project profiles with optimized metadata
* **Technical Implementation**
  * Deploy production-ready application with Polkadot-specific features
  * Integrate wallet connections for seamless donations
* **Marketing & Optimization**
  * Execute social media strategy to drive adoption
  * Implement SEO best practices for maximum Project visibility

## Expected Outcomes

1. **Comprehensive Registry**: A centralized database of Polkadot Projects for improved ecosystem communication
2. **Enhanced Visibility**: Improved search engine optimization for emerging Projects
3. **Developer Onboarding**: Clear pathways for new developers to join the Polkadot ecosystem
4. **Ecosystem Partnerships**: Opportunities for collaboration between aligned Projects

## Conclusion

By converting our Hackathon submission into Polkadot entirely, we will create a valuable resource that connects Projects with supporters, increases visibility for builders, and strengthens the overall ecosystem. We greatly appreciate your consideration of this proposal!

Request to develop a Polkadot registrar of projects.

root

wish_for_change

staking_admin

lease_admin

fellowship_admin

general_admin

auction_admin

referendum_canceller

referendum_killer

OpenGov Referenda

Origin able to dispatch a whitelisted call.

Origin for signaling that the network wishes for some change

Origin able to cancel slashes and manage minimum commission.

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

Origin for managing the composition of the fellowship.

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

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

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

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

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

OpenGov Referenda

Referenda Tracks