The Conor Daly 2025 Polkadot Motorsports Program is a proposal to partner with Polkadot in the NTT INDYCAR Series. The program has several key performance indicators (KPIs), including onboarding five new venues, achieving 150,000 Polkadot app downloads, launching a merch store and sweepstakes initiative, partnering with UNIQUE Network for NFT activations, generating over 1 billion media impressions, increasing website traffic, and hosting VIP hospitality events. The program also includes primary sponsorship for six marque events, premium hospitality and B2B assets, elevated activation for consumer engagement, and a global ambassador role for Conor Daly. The 2025 Polkadot Motorsports Indycar lineup includes races in St. Petersburg, Thermal, Indy 500, Road America, and Iowa.

Rejected

big_spender

**Proponent:** [ConorDaly22](https://sub.id/1s2mPd5i2ryNafYRVueZbKSnYFtjbTspaTssjctDWL3qNJT) - 1s2mPd5i2ryNafYRVueZbKSnYFtjbTspaTssjctDWL3qNJT

**Beneficiary Pure Proxy Multi-sig 4/5** - 13n1iqNWkF3e8YQcZQV1rsrGCoW5L3QNMFDMh3DEQTte225J (signers: [ConorDaly22](https://sub.id/1s2mPd5i2ryNafYRVueZbKSnYFtjbTspaTssjctDWL3qNJT), [LearnPolkadot](https://sub.id/14m6YPTpa64jusibkvvCov4XsxW2ig7Hy3n23GpN9YVTqhUd), [The Phunky One](https://sub.id/1t67YMM4myXZ745px9a8PNWhU8FMyYJf5uXGowuwSAnp4x8), [Zugian Duck](https://sub.id/15tQ5joTz2nywZ4UgPYWDMN522s91W7yTmhvV1rp4hpVhZT3), [Stallings\_AG](https://sub.id/13Bm8YmgjH3aHMEWJAk8CgfwFJUMeJw3LSjbtaFmCFFsQSnh))

**Funds Requested:** $3,500,000 (requested in 1.75M USDC / 1.75M USDT)

---

# Conor Daly 2025 Polkadot Motorsports Program

2025 Polkadot Motorsports Partnership KPI’s

-   **5 New Venues Onboarded:** Successfully integrate Billfold payment services at five new venues in North America, secured through LOIs with minimum guarantees.  
      
    
-   **150,000 Polkadot App Downloads:** In collaboration with Parity achieve 150k downloads of the Polkadot App during the campaign through elevated activation efforts.  
      
    
-   **Merch Store & Sweepstakes Initiative:** Launching a season-long merch store initiative tied to a sweepstakes, featuring a grand prize drawing at the end of the season.  
      
    
-   **NFT Activation with UNIQUE Network:** Partner with UNIQUE Network to mint for weekly and event-based activations. Participants earn rewards and additional entries into the year-long sweepstakes.  
      
    
-   **1 Billion+ Media Impressions:** Generated over 1 billion global media impressions throughout the campaign.  
      
    
-   **Website Traffic Growth:** Increased traffic to [www.polkadot.com](http://www.polkadot.com) by approximately 20% in May.
-   **VIP Hospitality Events:** Host eight custom VIP hospitality weekends for VCs, investors, and B2B enterprise executives.

On-Track:

-   Primary sponsorship for six (6) marque events in the NTT INDYCAR Series in the 2025 season.
-   Premium hospitality and b2b assets that will be extended to different parachains within the Polkadot community
-   Elevated activation for consumer engagement x giveaways
-   Planning on pitching detailed plan to Marketing Bounty

Off-Track:

-   Global Ambassador (Conor Daly) on behalf of Polkadot
-   Featured virtual and in-person appearances on behalf of the brand throughout the year
-   Global media tour organized on behalf of the Polkadot leveraging CD
-   License free content to use for commercial x promotional purposes

## 2025 Polkadot Motorsports Indycar Lineup

\*All Races National Broadcast on FoxSports and also available streaming online

-   St. Petersburg - Florida - March 2nd
-   Thermal - California - March 23rd
-   Indy 500 - May 25th
-   Road America - Wisconsin - June 22nd
-   Iowa 1 -July 12th
-   Iowa 2 - July 13th

---

Discussion > [https://polkadot.polkassembly.io/post/2592](2592)

Get Involved - Community Engagement > [https://forms.gle/uzQ78VJcmVgHfWS27](https://forms.gle/uzQ78VJcmVgHfWS27)

Conor Daly - 2025 Polkadot Motorsports Program

Executed

small_tipper

SmallTipper

- A new proposal has been created to request funding in USDT.
- The money will be used to maintain a tool called substrate-api-client from January to June 2025.
- The substrate-api-client is a library that helps people connect to special nodes and works well with small devices.
- It is similar to another tool called Polkadot-js and allows developers to work with Polkadot and Kusama chains easily.
- This proposal is part of ongoing efforts to get funding for maintenance.
- The group is asking for $33,200 for the project.
- More information can be found in the full proposal linked in the content.

small_spender

Maintenance for the substrate-api-client Jan-25 to Jun-25

A problem occurred with a proposal called Ref. 1303, where a Relay Chain Proxy was set to receive AssetHub assets, making them inaccessible. To fix this, a new proposal is needed. The original proposal can be found [here](1303). The preimage was pulled before the confirmation period ended, and you can verify it [here](https://polkadot.subscan.io/extrinsic/0xec8ca6dbcfee1b25201b9e95b61e6eb890f7eee9d4f21aee060da7005d79c42c). Waiting for Pure Proxy Replication to solve this issue is not ideal, as it will take many months. Submitting a Root Ref to replicate the proxy was also considered, but it would take too long and tie up resources. Voting on this new proposal will help fix the payout issue approved in Ref. 1303.

medium_spender

### tl;dr

The preimage for [Ref. 1303](1303) was pulled during confirmation to avoid payout of AssetHub assets to a Relay Chain Proxy.

This ref intends to rectify the payout approved by Ref. 1303.

Full explanation as well as the original Ref can be found [here](1303).

### Q: What was the problem?

A: A Relay Chain Proxy as beneficiary of Asset Hub assets would mean the assets were inaccessible. Jay Chrawnna has [committed seppuku](https://x.com/GldnCalf/status/1867765364295446963) for the error.

### Q: Proof the Preimage was Pulled?

A: You can verify it [here](https://polkadot.subscan.io/extrinsic/0xec8ca6dbcfee1b25201b9e95b61e6eb890f7eee9d4f21aee060da7005d79c42c) - pulled hours before the end of the confirmation period.

### Q: Why not wait until Pure Proxy Replication is implemented?

A: [Pure Proxy Replication](https://github.com/polkadot-fellows/RFCs/pull/111) will solve this UX issue however it is unlikely to reach prod for many months which would render the assets useless until then.

### Q: Why not submit Root Ref to Replicate Proxy?

A: While such a ref has recently been submitted for [several other projects](https://polkadot.subsquare.io/referenda/1308) caught in this UX snare, we decided it would be unwise to tie the root track for a single instance. It would also take months during which time the assets would be useless.

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

Ratify Payout APPROVED by Ref. 1303 - The Kus

This proposal is asking for money to pay for work done to help the Polkadot ecosystem from July 1 to November 1, 2024. The person did many things like talking to new teams, helping with events, and making a handbook for Polkadot. They want to be paid $45,000 for working about 25 hours each week during that time. They have done a lot of work to help Polkadot grow and hope that the people in charge see how important their work is. Some of the main things they did include making the Polkadot Handbook, talking to teams that left Polkadot, and helping with business development and community activities.

Retroactive Funding for Ecosystem Activities

- Three accounts lost funds due to a bug in the runtime.
- The bug caused assets to be lost instead of being trapped.
- The bug has since been fixed.
- Funds lost due to this bug should be reimbursed.
- Assets that were trapped can be reclaimed, so they are not part of this proposal.
- A similar proposal was made for Kusama.
- The lost funds were from three specific extrinsics.

[Small Spender] Reimburse accounts affected by an XCM bug

### Summary
This proposal aims to increase Polkadot's visibility by requiring teams funded by the Polkadot Treasury to display the Polkadot logo on their websites, products, and social media. 

- Teams must show the logo as long as their project is active.
- They should specify where and how they will display the logo in their funding proposals.
- Teams can choose from phrases like "Funded by Polkadot" or "Powered by Polkadot."
- The Polkadot Brand Hub provides design guidelines.
- This rule applies to future funding requests but encourages past recipients to follow it.
- Exceptions can be made for cases where displaying the logo is not possible.

The goal is to boost Polkadot's brand awareness and show its support for funded projects.

wish_for_change

Wish For Change | Polkadot Branding Guideline

TimedOut

whitelisted_caller

Wrong Track - Please vote NAY

- The Polkadot/Código Brazuca Academy started in July to train developers in Brazil.  
- The project got less money than planned because of currency changes.  
- Over 750 students joined, and big partners like São Paulo City Hall and Petrobras support it.  
- Many classes (like JavaScript, Web3, and Linux) are already done and online.  
- Some classes (like Rust and Polkadot tools) are still being worked on.  
- The team needs more money to finish all the promised lessons.  
- So far, $47,657 has been spent, and $20,057 is left for the next steps.  
- The project will take 11 months instead of 8 because more students joined.

**Context and Problem**

The Polkadot/Código Brazuca Academy training program commenced in July, launching our endeavor to establish a community of developers within the Polkadot ecosystem in Brazil. Our approved project, sanctioned by governance, encompasses various focal points that we have resolved to address and further develop based on the real-world circumstances we have encountered — [https://polkadot.polkassembly.io/referenda/568](../referenda/568\).)

Between the proposal submission and the release of the funds, the currency devalued by 28.52%. The initial budget was set at US$ 95,000.00, but the project received a total of US$ 67,715.00 when the funds were released. At the time, there was no option to request funds in USDC or USDT, which could have mitigated the impact of this fluctuation. The team delivered many project milestones in the following months and achieved good results in Brazil. However, the team needs the total funds of the original proposal to accomplish the entire project and to deliver to the Brazilian community all the content that as promised.

**Report and Some Hight Lights**

Report: >> [Acess the Report](https://drive.google.com/file/d/1BXLbUEqhQC_oetaZ9ROoNb0tVe2cxMlk/view?usp=sharing) <<

Executive Summary: >> [Access the Executive Summary](https://drive.google.com/file/d/1EZgxQuekdoL-nXP83i9bYOJA-Huo0H3z/view?usp=sharing) <<

At the outset, our online program engaged around 450 students, with 18 participating in on-site sessions. Presently, our collective student and member count has reached 753 individuals. Notably, while our Discord server indicates active members, others have engaged at various intervals and may not be part of the current cohort. The program continues to demonstrate consistent growth in user numbers and has played a pivotal role in establishing significant partnerships within the Brazilian community. Notably, the São Paulo City Hall, the largest city in Latin America, will disseminate the program across the municipality, the Curitiba City Hall has come on board as a partner, and Petrobras intends to integrate some of the content for internal employee training. Furthermore, Instituto Eldorado, a prominent technology institute with programmers and professionals already catering to the Brazilian market, has also pledged support. These collaborations underscore the program's expanding reach and influence across diverse sectors in Brazil.

![](https://i.ibb.co/sPT4Rqv/Imagem-do-Whats-App-de-2024-07-15-s-15-53-25-6ca7c2d8.jpg)

![](https://i.ibb.co/FWSVgGf/polkadotturma.jpg)

**Milestones and Deliverables:**

The course is structured to provide a comprehensive learning journey designed to equip students with the necessary skills to navigate and build within the Web3 ecosystem, specifically focusing on Polkadot. The curriculum covers various topics and technologies, ensuring participants are well-prepared to engage with foundational and advanced concepts. Key modules include:

<div class="joplin-table-wrapper"><table style="border-collapse: collapse; width: 100%; height: 1120px;" border="1"><tbody><tr style="height: 49px;"><td style="width: 8.33333%; height: 49px;">id</td><td style="width: 20.4884%; height: 49px;">Phases</td><td style="width: 40.7566%; height: 49px;">Deliverables</td><td style="width: 30.4217%; height: 49px;">Status</td></tr><tr style="height: 154px;"><td style="width: 8.33333%; height: 154px;">1</td><td style="width: 20.4884%; height: 154px;">Course start administration</td><td style="width: 40.7566%; height: 154px;"><ul><li>Marketing</li><li>Student Selection</li><li>Teacher selection and training</li><li>Discord Structure</li><li>Starting Classes</li></ul></td><td style="width: 30.4217%; height: 154px;">Done Teacher Selection Student Selection Discord Ready Youtube Ready Welcome Classes</td></tr><tr style="height: 112px;"><td style="width: 8.33333%; height: 112px;">2</td><td style="width: 20.4884%; height: 112px;">Introduction discord *</td><td style="width: 40.7566%; height: 112px;"><ul><li>Online Classes&nbsp;</li><li>In-person class</li><li>Exercises</li></ul></td><td style="width: 30.4217%; height: 112px;">Done Recorded Edit Publish Classes</td></tr><tr style="height: 112px;"><td style="width: 8.33333%; height: 112px;">3</td><td style="width: 20.4884%; height: 112px;">Linux Basic*</td><td style="width: 40.7566%; height: 112px;"><ul><li>Online Classes</li><li>In-person class</li><li>Exercises</li><li>Extra Classes</li></ul></td><td style="width: 30.4217%; height: 112px;">Done Recorded Edit Publish Classes</td></tr><tr style="height: 112px;"><td style="width: 8.33333%; height: 112px;">4</td><td style="width: 20.4884%; height: 112px;">Introduction to Coding Logic and Algorithms (18 class videos)</td><td style="width: 40.7566%; height: 112px;"><ul><li>Online Classes</li><li>In-person class</li><li>Exercises</li><li>Extra Classes</li></ul></td><td style="width: 30.4217%; height: 112px;">Done Recorded Edit Publish Classes</td></tr><tr style="height: 49px;"><td style="width: 8.33333%; height: 49px;">5</td><td style="width: 20.4884%; height: 49px;">JavaScript (26 class videos)</td><td style="width: 40.7566%; height: 49px;"><ul><li>Online Classes</li><li>In-person class</li><li>Exercises</li><li>Extra Classes</li></ul></td><td style="width: 30.4217%; height: 49px;">Done Recorded Edit Publish Classes</td></tr><tr style="height: 49px;"><td style="width: 8.33333%; height: 49px;">6</td><td style="width: 20.4884%; height: 49px;">TypeScript (23 class videos)</td><td style="width: 40.7566%; height: 49px;"><ul><li>Online Classes</li><li>In-person class</li><li>Exercises</li><li>Extra Classes</li></ul></td><td style="width: 30.4217%; height: 49px;">Done Recorded Edit Publish Classes</td></tr><tr style="height: 70px;"><td style="width: 8.33333%; height: 70px;">7</td><td style="width: 20.4884%; height: 70px;">Web3 Fundamentals (39 class videos)</td><td style="width: 40.7566%; height: 70px;"><ul><li>Recorded class with Professor</li><li>In-person class running</li><li>Exercices</li></ul></td><td style="width: 30.4217%; height: 70px;">Done Recorded Edit Publish Classes</td></tr><tr style="height: 70px;"><td style="width: 8.33333%; height: 70px;">8</td><td style="width: 20.4884%; height: 70px;">Introduction to the Polkadot Ecosystem (8 hours)</td><td style="width: 40.7566%; height: 70px;"><ul><li>Recording of classes</li><li>In-person class</li><li>Exercices</li></ul></td><td style="width: 30.4217%; height: 70px;">Doing<ul><li>Recording (Doing)</li><li>Edit (to do)</li><li>Publish (to do)</li><li>Classes (to do)</li></ul></td></tr><tr style="height: 70px;"><td style="width: 8.33333%; height: 70px;">9</td><td style="width: 20.4884%; height: 70px;">Polkadot Infrastructure and Tools (48 hours)</td><td style="width: 40.7566%; height: 70px;"><ul><li>Recording of classes&nbsp;</li><li>In-person class</li><li>Exercices</li></ul></td><td style="width: 30.4217%; height: 70px;">&nbsp;Doing<ul><li>Recording (Doing)</li><li>Edit (to do)</li><li>Publish (to do)</li><li>Classes (to do)</li></ul></td></tr><tr style="height: 49px;"><td style="width: 8.33333%; height: 49px;">10</td><td style="width: 20.4884%; height: 49px;">Rust I (96 hours)</td><td style="width: 40.7566%; height: 49px;"><ul><li>Recording of classes&nbsp;</li><li>In-person class</li><li>Exercices</li></ul></td><td style="width: 30.4217%; height: 49px;">Doing<ul><li>Recording (Doing)</li><li>Edit (to do)</li><li>Publish (to do)</li><li>Classes (to do)</li></ul></td></tr><tr style="height: 70px;"><td style="width: 8.33333%; height: 70px;">11</td><td style="width: 20.4884%; height: 70px;">Rust II – Advanced Rust (64 hours)</td><td style="width: 40.7566%; height: 70px;"><ul><li>Recording of classes pending</li><li>In-person class</li><li>Exercices</li></ul></td><td style="width: 30.4217%; height: 70px;">To Do with Refil</td></tr><tr style="height: 70px;"><td style="width: 8.33333%; height: 70px;">12</td><td style="width: 20.4884%; height: 70px;">Substrate/Polkadot SDK I (60 hours)</td><td style="width: 40.7566%; height: 70px;"><ul><li>Recording of classes pending</li><li>In-person class</li><li>Exercices</li></ul></td><td style="width: 30.4217%; height: 70px;">To Do with Refil</td></tr><tr style="height: 21px;"><td style="width: 8.33333%; height: 21px;">13</td><td style="width: 20.4884%; height: 21px;">Substrate/Polkadot SDK II (40 hours)</td><td style="width: 40.7566%; height: 21px;"><ul><li>Recording of classes pending</li><li>In-person class</li><li>Exercices</li></ul></td><td style="width: 30.4217%; height: 21px;">To Do with Refil</td></tr><tr style="height: 21px;"><td style="width: 8.33333%; height: 21px;">14</td><td style="width: 20.4884%; height: 21px;">Final Project – Hackathon</td><td style="width: 40.7566%; height: 21px;"><ul><li>Recording of classes pending</li><li>In-person class</li><li>Exercices</li></ul></td><td style="width: 30.4217%; height: 21px;">To Do with Refil</td></tr><tr style="height: 21px;"><td style="width: 8.33333%; height: 21px;">15</td><td style="width: 20.4884%; height: 21px;">Deployment of the final project on a testnet</td><td style="width: 40.7566%; height: 21px;">Final student test</td><td style="width: 30.4217%; height: 21px;">To Do with Refil</td></tr><tr style="height: 21px;"><td style="width: 8.33333%; height: 21px;">16</td><td style="width: 20.4884%; height: 21px;">Assessment Exam</td><td style="width: 40.7566%; height: 21px;">Students' application for the polkadot academy exam</td><td style="width: 30.4217%; height: 21px;">&nbsp;</td></tr></tbody></table></div>

- **We needed to create these extra classes because many students had difficulty using Discord and operating Linux. This accelerated their understanding and entry into the programming lessons.**

**Deliverables Links**

Class: Discord: >> [Record Class Link](https://www.youtube.com/playlist?list=PLA5znOwXLxW6AEi139_kRvWcDTF8hSzqk) <<

Linux: >> [Record Class Link](https://www.youtube.com/playlist?list=PLA5znOwXLxW7FhdlAZuqli8SJITnZL8iW) <<

Programming Logic: >> [Record Class Link](https://www.youtube.com/watch?v=wUpVJtYMung&list=PLA5znOwXLxW5WIfYnrMl2CjiF1uCjSzY7&index=1&t) <<

Java Script: >> [Record Class Link](https://youtube.com/playlist?list=PLA5znOwXLxW5uVBcWpF3xaMQDv5RWcSQM&si=10UfsSu38uQccTwT) <<

Type Script: >> [Record Class link](https://www.youtube.com/watch?v=KfjyfYysguM&list=PLA5znOwXLxW5lgh3s-okZwRGU-q7WCmgZ) <<

Web3**\*** >> [Record Class Link](https://www.youtube.com/playlist?list=PLA5znOwXLxW6BMclpapZrrGfGi8nRMI5j) <<

Extra Class: >> [Record Class Link](https://www.youtube.com/watch?v=wj50f6jCaM8&list=PLA5znOwXLxW6_OiOsi_-TiiHSlhAyZ8a2) <<

\* This course is ongoing; all the lessons have already been recorded but are being released according to our schedule.

**BUDGET**

You can review our initial budget in the proposal here: [https://polkadot.polkassembly.io/referenda/568](../referenda/568)

**![](https://i.ibb.co/DLDhBnW/expenses.png)**

So far, **$47,657.25** has been spent on course administration, one month of marketing to attract students, student selection, Discord management, lesson editing, instructors recording and giving extra lessons to answer student questions, and teaching in-person classes. These efforts allowed us to deliver milestones 1 to 7. Additionally, we can complete milestones 8,9,10 (october, November and December) with the remaining funds of $20,057.75 (october, november and december), reaching 65% of the project's milestones.

The **$27,545.72** will be used to complete milestones 11 through 15 (more 3 months - end march 2025) Due to a more extensive marketing campaign than initially planned, which extended over two additional months and reached recognized institutions, the project timeline requires an adjustment from 8 to 11 months. The campaign’s success has brought in a higher number of students than anticipated, demanding a synchronous approach to content development aligned with students' learning needs. This iterative process has enabled a notable enhancement in content quality. Despite the extended timeline, the budget remains unchanged as it was designed around the deliverables. Therefore, the program will be fully delivered as per the proposal with the requested timeline adjustment.

**Wallet Beneficiary**

Wallet hash: 12WjZZxu5pDMy2ZfmTsVDFn71Xvi6LVbTefqVCt5b7ukCE9E

Código Brazuca  Academy

This proposal aims to create a collaborative strategy for Africa to increase awareness, adoption, and growth of Polkadot, a blockchain platform. The plan involves building a supportive community of agents representing Polkadot in Africa, with a focus on developers and content creators. The strategy includes educational sessions, community engagement, ecosystem representation, developer outreach, and encouraging the building of Polkadot native apps and integrations. The plan is divided into four phases: icebreaker events, Rust community activations, developer workshops, and community meetups. The team behind the proposal includes Bekka, Kratista0s, Sanchez, and Victor, who are also responsible for the Polkadot Africa X account. The requested amount for the project is $92,880, with the duration set from January to June 2025. The initiative will primarily focus on Nigeria, Kenya, Ghana, and Uganda, with a goal to eventually reach out to North and South African regions as well.

**TLDR:** Create a collaborative strategy for Africa aligning different stakeholders and the community to drive awareness, adoption and growth.

**Introduction**

In emerging markets, blockchain technology is essential and a chance to leapfrog several difficulties. Africa is one of the places where Web3 can fulfil its full adoption potential where people use the technology for daily things like remittance and cross-border payments.

**Motivation**

Polkadot has limited engagement and few project developments in Africa compared to newer platforms like Ethereum L2s, Solana, Avax, ICP Network etc

**Mission**

This proposal aims to build a supportive community of agents representing Polkadot in Africa. There are so many pieces to the puzzle when growing a diverse community. For instance, we would want developers and content creators. How do we achieve this? 

**Solutions**

-   Educational sessions.
-   Community engagement and management.
-   Ecosystem representation.
-   Developer outreach and support.
-   Encourage the building of Polkadot native apps and integrations.
-   Providing guides on utilising Polkadot native apps and products in the ecosystem.
-   Recruit mentors to help out and onboard new community members.

**Plan**

There would be different phases of development for this 6-month strategy. Please note that these 2 different phases could run in parallel too.

-   Icebreaker events (Phase 1)
-   Rust community activations (Phase 2)
-   Developer workshops (Phase 3)
-   Community meetups (Phase 4)

**The team**

-   Bekka - Developer relations lead West and East Africa
-   Kratist0s - Operations lead East Africa
-   Sanchez - Content creation and community manager
-   Victor - Business developer lead West Africa.

We are also the team behind the [Polkadot Africa X](https://x.com/AfricaPolkadot) account and collectively we've assisted to highlight activities by different community members as well as contribute in various capacities towards bringing Polkadot community together online and IRL.

**Requested amount:  $92,880**

**Duration: (Jan - Jun 2025)**

We would focus on setting up the foundations for the rest of the year and carry out initiatives properly next year. The full proposal is [here.](https://docs.google.com/document/d/10RPApEeBAzBEr9RQ5XPPoMhLj1HLF-J3u0dVvCRGHDA/edit?usp=sharing)

-   Team Compensation - $47,520
-   Events (sourced from EB) - $39,000
-   Utilities - $30,960
-   Transport (IRL events)- $11,400
-   Marketing - $3,000

Total (after EB deduction) = $92,880

**Regions/Key countries**

Our initiatives would be mostly carried out in these countries, we selected 2 countries from West and East African regions.

-   Nigeria
-   Kenya
-   Ghana
-   Uganda

**Limitations**

While our IRL activities will start with West and East Africa regions in select key cities, we still have a broader view to reach out to North and South African regions, support them online and create a website and discord community that caters to all community members from Africa

Treasury Proposal: Polkadot Africa Community Growth (West and East Africa regions) 

Token Terminal has introduced a new initiative to create comprehensive and standardized datasets and metrics for the Polkadot ecosystem. The proposal aims to improve the standardization and depth of public Polkadot datasets, which are currently insufficient. The initiative includes two major improvements: transitioning from basic to standardized metrics and increasing distribution. The standardized metrics will require significant transformation work by the research team, involving in-depth parachain-specific research and ongoing maintenance. The initiative also includes expanded distribution through the Google Web3 Marketplace, providing public access to all Polkadot data within Token Terminal's data warehouse. The total grant size for the project is $1,005,000, paid in USDT.

Approved

![](https://i.ibb.co/THCm9SL/Screenshot-2024-12-11-at-12-09-43.png)

Dear Polkadot community,

We are excited to introduce our next initiative, focused on building comprehensive and standardized datasets and metrics for the Polkadot ecosystem. Building on the success of our first project, this initiative aims to expand distribution, and enable deeper insights for analysts, developers, and investors.

Full proposal details ➡️ \[[here](https://docs.google.com/presentation/d/1A2vK2afEO9EDjEaEuBB1pkyKkRuzNbx019YjjRlZ0hk/edit?usp=sharing)\]

**1\. Executive summary**

A key challenge with current public Polkadot datasets is their insufficient level of **standardization and depth**, which limits the ability to calculate essential financial and business KPIs.

This proposal introduces two major improvements:

**i) The transition from basic to standardized metrics**. Our goal is to increase the depth, usability, and standardization of metrics, evolving from raw blockchain data to fully standardized financial and business KPIs for the leading parachains.

-   **Basic metrics** (_e.g. active addresses, gas used, and transaction counts, etc._) are programmatically derived from raw blockchain data. These metrics require less parachain-specific research or maintenance, as they are generated through automated processes and presented in their simplest form.
-   **Standardized metrics** (_e.g. TVL, fees, and active users, etc._) require significant transformation work by our research team. This process involves more in-depth parachain-specific research and ongoing maintenance to ensure the metrics are accurate, comparable, and aligned with established financial and business standards.

**ii) Increased distribution**. In addition to improving the quality and depth of metrics available on Token Terminal, this proposal also includes expanded distribution through the Google Web3 Marketplace. In practice, this means providing public access to all Polkadot data within Token Terminal’s data warehouse.

-   **Google Web3 Marketplace**: Each parachain will have its own dataset on the marketplace, covering everything from block-level data to standardized financial and business metrics.
-   **Token Terminal**: Each parachain’s project page will be populated with Standardized metrics (in addition to Basic metrics). Additionally, parachains will also gain visibility through Discover, Market sector boards, and datasets like [Trending contracts](https://tokenterminal.com/explorer/datasets/trending-contracts) for EVM-compatible chains.

The growth of the Polkadot ecosystem is driven by a sophisticated community of developers, analysts, researchers, and investors. By providing high-quality, standardized datasets and metrics, this initiative strengthens Polkadot’s institutional brand, positioning its native asset, DOT, as a natural inclusion in institutional portfolios and a potential target for the next ETF.

**2\. Background**

Since launching in 2020, Token Terminal has established itself as a trusted partner in the crypto data analytics space, known for:

-   **Institutional credibility**: First crypto data platform integrated with Bloomberg Terminal and a partner to MarketVector (VanEck subsidiary) for fundamentals-weighted crypto indexes.
-   **Technical excellence**: Running nodes across 20+ EVM and non-EVM blockchains, managing a 400TB+ serverless data warehouse on BigQuery.
-   **Proven results**: Our first initiative focused on creating a standardized listing for Polkadot and basic listings for 50 parachains. We are ahead of schedule, and already cover basic metrics for over 20 parachains. Additionally, Parity is adopting key datasets we developed into their internal data warehouse (DotLake).

**3\. Roadmap & Economics**

**Milestone 1 – Q1 ‘25**: $351K Publish basic datasets and metrics for top 20 parachains on Google Web3 Marketplace and Token Terminal’s data platform.

**Milestone 2 – Q2 ‘25**: $354K Upgrade top 20 basic datasets and metrics to standardized format across both platforms.

**Milestone 3 – Q3-Q4 ‘25**: $300K Maintain standardized datasets and metrics for top 20 parachains across both platforms.

  
Total Grant Size: **$1,005,000** (_paid in USDT_)  
  
We look forward to your feedback and suggestions on this proposal. For more details, see the full proposal and attached deck ➡️ \[[here](https://docs.google.com/presentation/d/1A2vK2afEO9EDjEaEuBB1pkyKkRuzNbx019YjjRlZ0hk/edit?usp=sharing)\].

  
Thank you,  
Token Terminal Team

Accelerate growth and adoption across the entire Polkadot ecosystem

Polkadot Hub is planning to integrate a custom Etherscan for PolkaVM/revive Smart Contracts. This $1 million Etherscan-as-a-Service integration aims to provide Web3/Solidity developers with seamless tools for deploying and interacting with PolkaVM contracts on Westend Hub and Polkadot Hub. The goal is to increase developer and user growth on Polkadot Hub in 2025-2026. Polkadot Hub is now the primary home for smart contract activities and other functions in Polkadot 2.0. The integration will allow Solidity contracts to be compiled to PolkaVM instead of EVM and interpreted by the revive-pallet on Polkadot Hub. The proposal includes a budget of $1,000,000 USDC for the Etherscan team to address and support the PolkaVM and revive custom integration fully. The integration is expected to be completed by Q2 2026.

**Summary:**  
Polkadot Hub needs a custom Etherscan integration for PolkaVM/revive Smart Contracts. The proposed $1MM Etherscan-as-a-Service integration provides Web3/Solidity developers seamless tools for deploying and interacting with PolkaVM contracts first on Westend Hub and then on Polkadot Hub, aiming for increased developer+user growth of Polkadot Hub in 2025-2026.  
**  
Problem: Polkadot Hub needs a _PolkaVM_ Block Explorer  
  
**Polkadot Hub (also known as Asset Hub or “Plaza”) is now positioned in the Polkadot 2.0 Roadmap as the primary home for user-facing and developer-facing smart contract activities as well as staking, governance and managing programmable assets.  
  
Historically, EVM contracts have been deployed in the Polkadot ecosystem in [Moonbeam](https://moonscan.io/) and [Astar](https://astar.blockscout.com/) through the “[Frontier](https://github.com/polkadot-evm/frontier)” pallet, but with key breakthrough [PolkaVM](https://forum.polkadot.network/t/announcing-polkavm-a-new-risc-v-based-vm-for-smart-contracts-and-possibly-more/3811) (a RISC-V-based virtual machine also at the heart of [Polkadot JAM](https://graypaper.com)) there is a new Polkadot Hub+Cloud roadmap:  
  
[Contracts on AssetHub Roadmap](https://forum.polkadot.network/t/contracts-on-assethub-roadmap/9513)  
[Solidity on PolkaVM](https://forum.polkadot.network/t/contracts-update-solidity-on-polkavm/6949/7)  
[Contracts on Polkadot Introducing Project Revive](https://www.youtube.com/watch?v=GPuTt10dxKI)

These are a part of numerous [Polkadot 2.0 innovations](https://x.com/alice_und_bob/status/1863979132062748954/photo/1) from [Plaza: A Batteries-Included, Scalable Polkadot System Chain](https://www.rob.tech/blog/plaza/) ([summary](https://x.com/rphmeier/status/1802809037186089243))) to CoreVMs + CorePlay JAM Services. This roadmap enables 4th generation Web3 developers to access Polkadot in both high-performance ways in “old” ways (Solidity-based Smart Contracts on Polkadot Hub) and “new” ways – enabled by Polkadot JAM Services, not with yet another EVM Chain but with PolkaVM, revive and Polkadot 2.0 innovations at its _foundations_.  
  
This proposal concerns giving Web3 developers the best blockchain service available: [Etherscan as Service](https://etherscan.io/eaas), with dominant usage in the Ethereum ecosystem (Ethereum, Base, Optimism, Arbitrum, …) in addition to Moonbeam users in the Polkadot ecosystem.  Etherscan’s feature set is comprehensive and difficult for other block explorers to match. For an overview, see [Diving deeper with EVM block explorers](https://www.youtube.com/watch?v=ve1fouiC3v0).  
  
Our key motivation is simple: **Give Users + Developers the industry-leading explorer for Polkadot Hub: Etherscan** – but _fully customized_ for PolkaVM + revive-pallet innovations.  
  
[Alex Thiessen](https://forum.polkadot.network/t/contracts-on-assethub-roadmap/9513/19) (Parity Contracts team lead, also proponent of [OpenGov #885 - Should we allow EVM compatible contracts on Asset Hub?](885)) indicates unequivocal support of Etherscan here:  
  

![image.png](https://i.ibb.co/6BM05qz/image.png)  
  
  
**Solution: Etherscan as a Service (EAAS) Custom Integration**  
  
The vast majority of Smart Contract Developers write contracts in Solidity and deploy compiled EVM byte code to an EVM chain – most commonly Ethereum and Ethereum rollups but also Polkadot rollups (Moonbeam, Astar).  With the revive pallet deployed on Polkadot Hub, these Solidity contracts will be compiled to PolkaVM instead of EVM, and interpreted by the revive-pallet on Polkadot Hub instead.  
  
Widely used REMIX tooling has already been customized for PolkaVM at [https://remix.polkadot.io/](https://remix.polkadot.io/) and enables compilation and deployment to Polkadot Hub in 2025, but is available on WestEnd Hub now: See [Deploy Your First Contract](https://contracts.polkadot.io/deploy-your-first-contract) to see how simple and familiar this is to everyday Solidity developers.  
  
In the same way, this proposal strives to have Etherscan also be simple and familiar as REMIX is to users and developers alike. This is enabled by a set of JSON-RPC methods necessary for indexers to do their work – our [tests](https://hackmd.io/FEHH1zuWR3aGPJUBWAS8Iw) indicate Westend Hub is ready for Etherscan integration in early 2025 and after all systems are fully tested, can proceed to Polkadot Hub as soon as pallet-revive is deployed in mid-2025.     
  
However, a custom integration is required to fully address PolkaVM. 

Here is a full link to the detailed proposal:

[Etherscan-as-a-Service x Polkadot Hub - PolkaVM Block Explorer (1 Mainnet, 1 Testnet)](https://docs.google.com/document/d/1SfYggOIZpTIYlpdFUiP45EAjVRr4rC4h_pI6bK3YpBg/edit?tab=t.0#heading=h.v6is2ta0txr1)

The proposal provides adequate budget ($1MM) for the Etherscan team to address + support the PolkaVM + revive custom integration fully.   Colorful Notion is taking on project management of the integration through 2025 into early 2026.  
  
**Key Benefits:**

(1) _Technical_**:** Fully functional PolkaVM-based Westend and Polkadot Hubs, supported by robust secure infrastructure from industry leader.  
(2) _Developer Impact_**:** Seamless Etherscan interface for PolkaVM/revive contracts on Polkadot Hub will attract leading Web3 teams deploying on Polkadot Hub. Tools for contract interaction and code verification match EVM.  
(3) _User Impact_**:** Dapp deployment on Polkadot Hub can support an order of magnitude growth in usage, driven by the above.  
  
  
**Budget:**  
**$1,000,000 USDC**  
  
**Services**: 

-   1 TestNet EAAS Integration: Westend Hub hosted at westend-hub.polkadot.io (or similar)  
    Expected coverage: Q2 2025 — Q1 2026 ( 1 year )
-   1 MainNet EAAS Integration: Polkadot Hub hosted at hub.polkadot.io (or similar)  
    Expected timeline: Q3 2025 — Q2 2026  ( 1 year )

**  
Merry Christmas**🎄🎅 **and Happy New Year 2025! 🍺🎉🤗   
  
_We look forward to making 2025 a great success together!_**

Etherscan-as-a-Service x Polkadot Hub - PolkaVM Block Explorer (1 Mainnet, 1 Testnet)  

dAppForge is an AI-powered plugin designed to help Polkadot developers build decentralized applications, appchains, and parachains more efficiently. The project has completed two of its four milestones, with the aim of reducing development time and making it easier for new developers to join the Polkadot ecosystem.

**Summary of Important Points:**
- A previous treasury proposal was submitted and completed.
- Milestone 2 of dAppForge V1 is now completed, with videos demonstrating the plugin's capabilities.
- The plugin is available on GitHub and can be used for code generation and autocompletion for substrate and ink!.
- The plugin provides insights into the code generated, helping developers understand substrate/ink! better and build faster.
- Two of the four milestones have been completed, with the remaining two focusing on fine-tuning the AI model, integrating Solidity, developing a monetization strategy, and creating a knowledge graph for Rust programming language.

**Overview:**
- Tagline: AI-powered plugin for Polkadot developers that reduces development time.
- Brief description: dAppForge aims to enable Polkadot developers to build better dApps, appchains, and parachains faster, lowering the entry barriers for new developers. The AI model is trained on Substrate and ink! and can be used for code generation and autocompletion.
- Motivation: Substrate and ink! can build great parachains, appchains, and dApps, attracting millions of users, which is crucial for the blockchain industry. dAppForge aims to empower existing developers and make it easier for new developers to join and build on Polkadot, including those familiar with Solidity.

**1\. Project**

**1.1 Summary of Important Points**

We submitted a previous treasury proposal, [ref 985](https://bit.ly/dappforge985), and completed all the [tasks/milestones](https://x.com/og_tracker/status/1850186240659747303).

Milestone 2 of dAppForge V1 is now completed. Here are some videos that show what you can do with the plug-in:

-   [How to install and use the plugin](https://www.loom.com/share/220816c212f14d9290328709973cd86d?sid=b0102dd8-c069-4479-8672-c39c82b2f548)
-   [Testing Substrate and ink!](https://www.loom.com/share/a747091de47d429d95b61b5ae59b6da2?sid=71ebdeb3-8712-49e2-97bf-42dba7c9acba)

Here is our GitHub: [https://github.com/dappforge](https://github.com/dappforge)

Currently, the plug-in can be used for code generation and autocompletion for substrate and ink! The plug-in does a good job of providing insights into the code generated, which helps developers increase their understanding of substrate/ink. With every fine-tuned version, developers should be able to build/code better and faster. This will lead to more applications being built on Polkadot.

We have now completed 2 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. This was completed, but the product is at a level where developers won’t see a lot of value. This is because the model needs to be further fine-tuned.
-   **Milestone 2 (completed: ref 985):** The product's beta version. It includes a fine-tuned LLM model for substrate, integrated ink!, and a chat feature.
-   **Milestone 3 ( current treasury proposal):** These are the main points ( more details in section 1.6):
    -   Fine-tune llm for substrate and ink! further. This will help developers increase their understanding of both substrate/ink!, which will lead them to code faster and reduce development time.
    -   Integrate Solidity. This will set the foundation for helping developers deploy EVM smart contracts on Asset Hub when Plazza is finished in Q2 2025. Polkadot needs more dApps, and one strategy is to make it easier for solidity developers to deploy on Asset Hub.
    -   Develop and integrate a monetization strategy to support the product's growth, focusing on a two-tier pricing structure, initial freemium experience, and scalable subscription option ($30/month). The paid tier will give developers access to enhanced AI, providing more accurate and contextually relevant code suggestions. We will also build a specialized educational subscription track focused on onboarding users to learn using Substrate and Ink!
        -   dAppForge is [open-sourced](https://github.com/dappforge/dAppForge-copilot). Anyone can clone the AI model and run it on their machines. However, you will need to set up your cloud infrastructure to run the model. If you don’t want to manage your own infrastructure, there will be a free tier for you to use.
            
    -   Develop a knowledge graph focused on the Rust programming language, capturing comprehensive insights on Rust syntax, libraries, frameworks, best practices, and common patterns. This will be crucial to expanding our reach to the wider Rust developer community. It will also create an opportunity to onboard them into the Polkadot ecosystem by demonstrating how their existing skills can be used to build blockchain applications using substrate/ink! Here are some examples:
        -   Upon starting a new project, the plug-in offers a dropdown option: "Would you like to try building a decentralized application using Ink!?" or “Would you like to explore how to build your blockchain using substrate?”
            -   Once JAM is live, we expect Rust developers to write contracts in Rust that would be compiled with PVM.  We also expect rust to be used to write different JAM services in the future. 
-   **Milestone 4 ( future treasury proposal):** These are the main points:
    -   Fine-tune current knowledge graphs.
    -   Enable Ink! and Solidity developers to deploy their smart contracts to Asset Hub. This involves making sure the contracts correctly compile to PVM. 
    -   Implement more features for the paid tiers, such as:
        -   Personalized Learning: Train the AI on your codebase for tailored suggestions.
        -   Up-to-date Knowledge Graph: Access the latest Polkadot knowledge and best practices with our regularly updated knowledge graph.

**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 AI model is currently trained on Substrate and ink!. The model can used for code generation and autocompletion for substrate and ink! It provides insights into the code generated, which helps developers increase their understanding of substrate/ink. We will now also integrate solidity to enable developers to deploy EVM smart contracts on Asset Hub when Plazza is completed in Q2 2025.

**Motivation:** Substrate and ink! can build great parachains, appchains, and dApps, attracting millions of users, which is crucial for the blockchain industry. 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. Additionally, including solidity will make it even easier for developers to deploy their smart contracts on Asset Hub.

[Here is the rest of the proposal:](https://docs.google.com/document/d/1NflNorI0JZOSrRVbUjcwB-yM2qNk2ytK6S1Zj3aEvNY/edit?usp=sharing)

dAppForge Milestone 3 

- The Assets Unlocked proposal wants to make Polkadot the best choice for turning real-world things into digital tokens.
- In the last 6 months, Polkadot worked with Unergy on solar energy, the Asian Development Bank on farming, NEITEC on helping small businesses, and Agora Labs on health data.
- They made many articles, videos, and podcasts that shared ideas and got people interested in Polkadot.
- In the next 6 months, they plan to create more content, build stronger partnerships, improve support for partners, and keep everyone informed about their progress.
- Big companies like BlackRock and JP Morgan are interested in using blockchain, which makes Polkadot important for digital tokens.
- They have a budget of USDT 127,050 to support their efforts over the next six months.

Scaling Polkadot: Driving Blockchain Innovation for Real-World Assets - Business Development Proposal

This proposal is about growing the BD team in Spain and Andorra, called IBERLABS, and expanding its work to LATAM. LATAM is a big area where many people can use Web3 technology. The team has already made 40 important connections that are becoming partners in the project.

The team has done some great things, like working with schools, companies, and governments. They have also been to important events to make Polkadot more popular. They are helping to teach more people about Web3 and have found many new projects in LATAM and Spain.

The team will have two people who work on business development and others who help with administration and following rules. They will keep finding new partners and going to events to make the project bigger.

This plan is important to make Polkadot a big and important technology around the world. You can read more about the proposal and the team's work in the links provided.

**Proposal Description:**

This proposal aims to continue the operations of the **BD team in Spain and Andorra (IBERLABS) while expanding its reach to LATAM**, a region with immense potential for Web3 technology adoption. Over the past four months, the team has generated more than 40 strategic leads, which are being converted into active builders and key ecosystem partners.

![](https://i.ibb.co/cX3wWc2/Copia-de-our-Partners.png)

The team will focus on leveraging this established pipeline while exploring new opportunities in LATAM. We plan to form strategic alliances with startups, educational institutions, local governments, and other relevant stakeholders to solidify Polkadot as the leading blockchain ecosystem in these regions.

![](https://i.ibb.co/ss00q9N/our-Partners.png)

**Key Achievements:**

-   Development of strategic partnerships with educational institutions, companies, and governments, including collaborations with Grant Thornton, the Governments of Andorra, the Generalitat of Catalonia, and various universities in Spain and LATAM.
-   Participation in key events such as the European Blockchain Convention, Merge Madrid, and LABITCONF, strengthening Polkadot's presence in strategic markets.
-   Increasing Web3 talent through educational programs, attracting developers to the ecosystem.
-   Building a robust pipeline of leads in LATAM and Spain, with projects focused on real-world asset tokenization and blockchain interoperability.

**Structure and Workflow:**

The Business Development team will consist of two Business Developers, supported by administrative and compliance resources. The workflow includes maintaining a strong pipeline, engaging with strategic partners, and participating in relevant events to expand the ecosystem's reach.

![](https://i.ibb.co/7ztkHfc/Blank-diagram-2.png)

This proposal is essential for expanding our presence, seizing opportunities in LATAM, and positioning Polkadot as a global leader in technological innovation.

You can read the full proposal [here](https://docs.google.com/document/d/1xOGF9JQM2t-k02gBzBncoNSysnF_Q4Dx7PFh-qnck3g/edit?tab=t.0).

You can read the full report of the leads generated over the past four months [here](https://docs.google.com/document/d/1brkXtENKUNjGLjDJYMoauyTpUNO_rR7uJUpopy1E8_0/edit?tab=t.0).

Continuation of Activities of the BD Team Spain & Andorra

The Polkadot Virtual Machine (PVM) Debugger is a new tool designed to help developers work with PVM implementations. It has features like breakpoints, memory inspection, and can run programs on multiple PVM clients at the same time. This tool was made because there were no good tools for debugging PVM programs before. It can help find mistakes and make sure PVM programs work the same way on different clients.

The team who made the PVM Debugger, FluffyLabs.dev, is asking for money to help them keep working on the tool. They want to make it better and add more features. The PVM Debugger is already done and can be used by anyone for free. It is on a website called GitHub, where people can see the code and help improve it.

The team has a plan to make sure people use the PVM Debugger and give them feedback. They will talk to people on the internet and make changes to the tool based on what people say. They want to make sure the PVM Debugger stays helpful as Polkadot changes and grows.

Dear Polkadot Community,

We are pleased to present our proposal for retroactive funding for the **Polkadot Virtual Machine (PVM) Debugger**, a tool designed to streamline the development and validation of PVM implementations. This open-source debugger offers key functionalities such as breakpoints, memory inspection, and parallel execution across multiple PVM clients, enabling developers to identify discrepancies and ensure alignment with formal specifications.

The PVM Debugger was created to address the lack of specialized tools for debugging and validating PVM programs. By providing detailed insights into program execution and memory states, it aims to enhance development efficiency and improve the robustness of PVM implementations across the Polkadot ecosystem.

**Full proposal text:** [**https://docs.google.com/document/d/1plq5C0kdMMuHscGNqnhvw0TebqXLZXQsIfqcbVLf-6M**](https://docs.google.com/document/d/1plq5C0kdMMuHscGNqnhvw0TebqXLZXQsIfqcbVLf-6M)

![](https://fluffylabs.dev/assets/images/pvm_screenshot.png)

**General Project Information**

**Project Category / Type:** Software development  
**Proponent:** FluffyLabs.dev  
**USDT address:** 15fGrDWmFoaApnZXEw1Zg45zuCqpkbMS9YPzczeU9dHseUUu  
**Requested allocation:** 16.000 USD  
Income taxable: 19% tax on “virtual currencies” tax in Poland: [https://www.podatki.gov.pl/en/your-e-pit/pit-38-for-2022/](https://www.podatki.gov.pl/en/your-e-pit/pit-38-for-2022/)  
**Discussion date:** 24th November 2024  
**Onchain publish date:** scheduled for 5th December 2024  
**Previous treasury proposals:** none

**Context**

The JAM (Join-Accumulate Machine) prize is a Polkadot initiative that encourages teams to develop diverse implementations of the new iteration of Polkadot network proposed by Gavin Wood. As part of the implementation of the JAM protocol, teams need to implement the Polkadot Virtual Machine (PVM) which is responsible for execution of the state transition of underlying services. This implementation diversity is essential for ensuring the Polkadot network remains flexible, secure, and resilient. However, building these various PVM implementations introduces significant technical challenges, particularly around debugging and analyzing the behavior of PVM programs across different client implementations.

Our team is one of the participants in the JAM prize, focusing on creating a robust PVM interpreter. During our work, we realized the need for a specialized tool to streamline debugging and validation processes. Standard debugging tools did not provide the level of insight required to efficiently inspect program execution, memory usage, and register interactions within the PVM.

To address this, we developed the PVM Disassembler & Debugger ([https://pvm.fluffylabs.dev)](https://pvm.fluffylabs.dev\)) specifically tailored for the JAM ecosystem. The tool includes a machine code and assembly view, allowing developers to inspect the PVM programs at a low level. After plugging in one of many possible PVM interpreter implementations, it also offers key debugging features such as step-over functionality, breakpoints, and memory inspection, giving developers a detailed view of program behavior during execution.A significant potential benefit of the debugger is its ability to validate programs simultaneously across multiple PVM implementations, helping teams participating in the JAM prize identify discrepancies and improve client interoperability.

While the tool was initially created for our own development purposes, we recognized its value for the broader Polkadot community and have decided to open-source it. This will allow other teams to use the debugger for cross-client validation and debugging, accelerating their development process and ensuring the robustness of their PVM implementations.

**Problem**

The development of diverse Polkadot Virtual Machine (PVM) implementations, as encouraged by the JAM prize, introduces significant technical challenges. Developers might struggle with debugging and validating PVM programs across different implementations, lacking tools to gain deep insights into program execution, memory states, and discrepancies between clients. This slows down development and increases the risk of bugs going undetected.

Additionally, we believe the PVM Disassembler & Debugger will serve a greater educational purpose of introducing a new wave of developers that are going to build Services on top of JAM. With references to Gray Paper definitions of instructions we strive to make it easier to understand in depth the complexity of PVM’s formal specification.

While our current main focus is creating a tool that would serve JAM implementers, with a proposal Solidity smart contracts running on top of PolkaVM on Asset Hub: [https://forum.polkadot.network/t/contracts-update-solidity-on-polkavm/6949,](https://forum.polkadot.network/t/contracts-update-solidity-on-polkavm/6949,) the PVM Disassembler & Debugger might prove itself useful much wider.

**Proposal**

We propose retroactive funding of the PVM Disassembler & Debugger aimed at supporting the implementers of Polkadot Virtual Machine (PVM) interpreters as part of the JAM prize. The tool addresses the complexities and technical challenges developers face when debugging and validating PVM programs. Our goal is to provide a robust solution that helps developers better understand program execution, identify discrepancies between multiple PVM implementations, and align with the formal specifications in the Gray Paper.

By creating this open-source debugger, we aimed to not only solve immediate development issues but also contribute to the long-term robustness of the Polkadot/JAM ecosystem by promoting client diversity, enhancing the overall quality of PVM implementations and helping the builders of programs running on top of the PVM.

Please note that the JAM prize or other funding mechanisms do not cover tooling for JAM. The JAM prize focuses on client implementations but does not cover the development of ecosystem tools such as debuggers, which benefit all participants. This is why we are submitting this proposal directly to the treasury and the Polkadot ecosystem.

**Available solutions**

While RISC-V debuggers exist, there is no dedicated debugger for PVM currently available. Even if one existed, it would probably not support running a program in parallel across multiple PVM implementations, which is crucial for identifying discrepancies in client behavior—something that traditional debugging tools cannot achieve in a standard debugging setup. This project aims to fill that gap with a PVM-specific debugger tailored to the unique requirements of the JAM ecosystem.

**Scope of work**

The PVM Debugger ([https://pvm.fluffylabs.dev)](https://pvm.fluffylabs.dev\)) initial version 1.0 has been completed, providing a basic range of functionalities to support PVM client implementations in the Polkadot ecosystem. Below is an outline of the key deliverables and functionalities. The deliverable is under Mozilla Public License (MPL-2.0) license.

**Deliverables**

1.  **TypeScript and React.js-based UI and Debugger Logic:** A responsive and intuitive user interface built with TypeScript and React.js, facilitating easy interaction with debugging features.
2.  **Example Integration with Dummy Rust PVM:** A demonstration of how the debugger integrates with a Rust-based PVM implementation using WebAssembly (Wasm) - [https://github.com/FluffyLabs/pvm-shell](https://github.com/FluffyLabs/pvm-shell)
3.  **Integration with typeberry’s PVM implementation (TypeScript)** - [https://www.npmjs.com/package/@typeberry/pvm](https://www.npmjs.com/package/@typeberry/pvm)
4.  **Integration with PolkaVM reference implementation (Rust)** - [https://github.com/tomusdrw/polkavm/tree/master/pvm-shell](https://github.com/tomusdrw/polkavm/tree/master/pvm-shell)
5.  **Integration with Gosamer’s team PVM implementation (Go)**
6.  **Open Source Code:** The full codebase is publicly available on GitHub ([https://github.com/FluffyLabs/pvm-debugger),](https://github.com/FluffyLabs/pvm-debugger\),) allowing other developers to use and extend the tool.

**Key Functionalities**

1.  **Step-Over & Breakpoints:** Developers can control program flow, setting breakpoints and stepping over instructions.
2.  **Memory & Register Inspector:** View memory and register states in real-time during program execution.
3.  **Machine Code / Assembly View:** Offers a side-by-side display of machine code and assembly to help trace execution flow.
4.  **Parallel Execution of Multiple PVM Clients:** Run PVM programs across various implementations to detect discrepancies.
5.  **Integrated Assembler:** A built-in assembler that allows for easy assembly-level debugging and execution.
6.  **Hex/Dec Mode:** Switch between hexadecimal and decimal representations of data for easier inspection and analysis.
7.  **Import JAM Test Vectors:** Support for importing JAM test vectors to test and validate PVM implementations.
8.  **Pre-Built Examples:** Includes sample programs like the Fibonacci sequence, add instruction, and branch instruction to help developers understand core functionality.
9.  **Glossary of PVM Operations:** Integrated glossary referencing PVM specifications from the Gray Paper, helping developers quickly understand PVM operations and their implementations.
10.  This set of functionalities makes the PVM Debugger a comprehensive and essential tool for anyone developing or validating Polkadot Virtual Machine implementations. The project is now publicly available for the community on GitHub ([https://github.com/FluffyLabs/pvm-debugger).](https://github.com/FluffyLabs/pvm-debugger\).)

**Ensuring Adoption and Onboarding Support for the PVM Debugger**

For information on Adoption and Onboarding, please refer to “[Detailed proposal: Scope of work > Ensuring Adoption and Onboarding Support for the PVM Debugger](https://docs.google.com/document/d/1plq5C0kdMMuHscGNqnhvw0TebqXLZXQsIfqcbVLf-6M/edit?tab=t.0#heading=h.udmjxfg5wn6d)”

**Timeline**

For timeline details, please refer to “[Detailed proposal: Timeline](https://docs.google.com/document/d/1plq5C0kdMMuHscGNqnhvw0TebqXLZXQsIfqcbVLf-6M/edit?tab=t.0#heading=h.ayjdw8f5oyqn)”

**Budget**

**Total Budget  
**Developer Hours: 140 hours × $100/hour = $14,000  
Product Management Hours: 20 hours × $100/hour = $2,000  
Total: **$16,000 (16,000 USDT)**

This budget represents the full scope of work required to develop and deliver the open-source PVM Debugger, which is now available for the Polkadot and JAM communities.

For full budget breakdown, please refer to “[Detailed proposal: Budget](https://docs.google.com/document/d/1plq5C0kdMMuHscGNqnhvw0TebqXLZXQsIfqcbVLf-6M/edit?tab=t.0#heading=h.1euxov8bcor6)”

**Payment condition**

For payment conditions details, please refer to “[Detailed proposal: Payment Conditions](https://docs.google.com/document/d/1plq5C0kdMMuHscGNqnhvw0TebqXLZXQsIfqcbVLf-6M/edit?tab=t.0#heading=h.xcl04avenoqr)”

**Key deliverables**

**1\. Software**

-   **Open-source PVM Debugger:** Fully functional debugging tool with core features such as step-over, breakpoints, memory and register inspection, machine code/assembly view, integrated assembler, and support for parallel execution across multiple PVM implementations.
-   **TypeScript and React.js UI:** User interface allowing easy interaction with PVM programs.
-   **Wasm Integration:** Example integration with a dummy Rust PVM via WebAssembly.
-   **Glossary of PVM Operations:** A built-in reference guide aligned with the PVM specifications in the JAM Gray Paper.
-   **Integration of three PVM implementations**

> typeberry’s PVM implementation (TypeScript)  
> PolkaVM reference implementation (Rust)  
> Gosamer’s team PVM implementation (Go)

**2\. Code Repository**

GitHub Repository: The complete source code for the debugger has been made available in a public repository ([https://github.com/FluffyLabs/pvm-debugger),](https://github.com/FluffyLabs/pvm-debugger\),) providing full transparency and allowing further community development.

**Objectives / Success criteria**

The success of the PVM Debugger project will be measured based on several key criteria focused on its adoption and utility within the Polkadot and JAM communities. These criteria will help determine if the project has met its objectives and if the final deliverable is satisfactory:

**1\. Adoption by Other JAM Teams**

-   Objective: The debugger will be used by other JAM prize participants to debug and validate their PVM implementations.
-   Success Criteria: At least three different PVM implementations are integrated into the PVM Debugger

**2\. Community Feedback**

-   Objective: Gain positive feedback from the Polkadot and JAM communities regarding the debugger’s utility and ease of use.
-   Success Criteria: Positive feedback from at least two JAM prize teams, with discussions in Polkadot forums or developer channels highlighting the debugger's value.

These success criteria will confirm that the PVM Debugger is an effective tool that serves its intended purpose of improving PVM implementation and debugging within the Polkadot ecosystem.

**Known constraints**

As we continue to expand the PVM Debugger by integrating additional PVM implementations, there are some known constraints that may affect future efforts:

1.  Integration Complexity: Further integration of PVMs, may require additional development time and resources. Managing the technical complexity of supporting new implementations could influence the timeline for integrating new PVMs.
2.  Coordination with Other JAM Teams: Future integrations may depend on testing and feedback from other JAM prize teams. Delays in receiving feedback or coordinating external testing could affect the speed of further integrations.
3.  No Prior Funding: The project has not been previously funded, ensuring no conflict of interest with other proposals or ongoing projects.

These constraints will be considered when expanding the debugger to support additional PVM implementations.

**Reporting**

Since the PVM Debugger project is already completed and this proposal seeks retroactive funding, there is no need for ongoing reporting related to the development process. However, the history of commits and progress can be fully tracked and reviewed on GitHub, providing full transparency on the project's timeline and milestones.

Should any future updates or enhancements be made, relevant information will be shared through appropriate channels, such as GitHub or Polkadot community forums.

**Communication strategy**

1.  For the PVM Debugger, ongoing communication with the community will primarily be managed through GitHub and other Polkadot-related channels. The following outlines how the team will present information, engage with the community, and handle feedback.
2.  Channels for Communication:

-   GitHub Issues: For bug reports, feature requests, and general issues, community members can create and track issues via GitHub Issues. This will be the primary channel for technical discussions and development tracking.
-   Polkassembly: Updates, feedback, and larger announcements will be shared with the Polkadot community via Polkassembly posts.
-   Element: For real-time communication, the project team will participate in relevant JAM-related Element channels to engage with users, answer questions, and provide updates.

Contact Information:  
Team Member: Piotr Zwolinski  
Email: [piotr@fluffylabs.dev](mailto:piotr@fluffylabs.dev)  
Element: @tomusdrw:matrix.org

**Team**

The PVM Debugger was built by the FluffyLabs team, a group involved in the development of decentralized tools for the Polkadot ecosystem:

1.  Tomasz Drwięga
2.  Piotr Zwolinski
3.  Wojciech Kwiatek
4.  Krystian Fras
5.  Mateusz Sikora

For full team members details, please refer to “[Detailed proposal: Team](https://docs.google.com/document/d/1plq5C0kdMMuHscGNqnhvw0TebqXLZXQsIfqcbVLf-6M/edit?tab=t.0#heading=h.ye9gseu5wxn2)”

**Why Polkadot**

The Polkadot ecosystem is a cutting-edge of blockchain innovation that builds trustless, privacy-preserving solutions, which are the foundations of Web3.0. JAM, as an important next step for Polkadot development, stands as a crucial initiative to make that vision happen. Our values are fully aligned and we are seeing an opportunity to build the development tooling for JAM as early as possible to make sure we are ready to get wider developer adoption of the protocol.

**Comments, Qs&As**

**How does the PVM Debugger benefit teams beyond the JAM prize?** Since the PVM is going to be an execution bedrock of future JAM services, we hope that the PVM Debugger (and its future iterations) will help not only the JAM implementers, but also the developers building services on top of JAM. Moreover, given the proposal to have Solidity Smart Contracts on PVM running on Asset Hub ([https://forum.polkadot.network/t/contracts-update-solidity-on-polkavm/6949)](https://forum.polkadot.network/t/contracts-update-solidity-on-polkavm/6949\)) we are considering to support more specialized debugging primitives for such contracts (like supporting debug symbols or the required host calls - cross contract calls, storage, etc).

**Why are you requesting retroactive funding instead of building this under the JAM prize?** The JAM prize focuses on client implementations but does not cover the development of ecosystem tools like e.g. debuggers, which benefit all participants. We developed the PVM Debugger to solve problems that arose during our own implementation and are now making it available to the entire community. Retroactive funding allows us to recover the costs of building this tool and ensures that it remains freely available and open-source.

**Will there be further development of the PVM Debugger?** While this proposal is specifically for retroactive funding, we are going to continue developing the PVM Debugger to add more features and integrations in the future. However, these future developments are independent from the current funding request.

**How will you ensure that the debugger remains relevant as Polkadot evolves?** The PVM Debugger is built to be flexible, allowing integration with new PVM implementations as they emerge. By keeping the tool open-source, we also invite contributions from the wider developer community to help ensure it remains relevant and aligned with Polkadot’s ongoing development.

**Your feedback**

We welcome feedback and suggestions from the Polkadot community to ensure the PVM Debugger meets the needs of developers and contributes effectively to the ecosystem. Your insights will help us refine the tool, prioritize future features, and maximize its impact. Please share your thoughts on Polkassembly or reach out to us directly through the provided channels. We look forward to collaborating with you to strengthen the Polkadot ecosystem together!

Treasury Proposal: Retroactive Funding for PVM Debugger

- An attacker stole over 312,185 DOT and 126,837 USDT from a parachain.
- The attacker gained control by upgrading the runtime with malicious code.
- They moved most of the stolen funds to exchanges and sold them for XMR.
- The attacker still has control over the parachain, putting more DOT at risk.
- A runtime upgrade is needed to stop further losses and secure user funds.
- The upgrade will restore control and remove the attacker's privileges.
- Efforts are being made to recover stolen funds and improve security.
- The community is being kept informed and encouraged to provide feedback.

root

Critical Runtime Upgrade to Prevent Further Exploitation

This is a ReferendumV2 post. It can only be edited by the proposer of the post .

- The proposal is for organizing 5 investor events by Prestel and Partners, not a large budget like a previous failed proposal.
- They wanted to apply for an Events Bounty, but it was rejected because of a past failure.
- The events will focus on educating people about Polkadot's technology, not selling investments.
- Anyone can speak on behalf of Polkadot at the events if they reach out via email.
- The five summits will be held in Riyadh, Dubai, Singapore, Istanbul, and London between February and July 2025.
- Prestel and Partners were chosen because they are experts in organizing investor conferences.
- HIC is leading this effort to help traditional investors understand Polkadot, and they are not making any money from it.
- The treasury should fund this to attract new money for Polkadot projects and help raise the value of DOT.

Prestel & Partners: Family Office & Investor Conference Series for Polkadot

- The referendum proposes to re-assign a curator for the Moderation Team bounty.
- The bounty was not extended before it expired, and someone unassigned the curator.
- The curator account is a pure proxy controlled by a 2/3 multisig account.
- The curator account remains the same: `12GkpkHocU4y1vFV2CpnA2AhkjzGGRtwucHFY77A5yyiQKp5`.
- The multisig account is: `12PztChx7WS5dSzJ6KcT1TdXTrUwEkMGYiakX6QXGa7myTpM`.
- The signatories are Abdulbee, Grizz, and Michalis.
- The bounty's details can be found on the [bounty's page](https://polkadot.subsquare.io/treasury/bounties/24).

Re-propose curator for the Moderation team bounty

This page is about a request for funding to continue the development of ReactiveDOT and DOTConnect. ReactiveDOT is a library for React and Vue, and DOTConnect is a wallet connector UI library. The goal is to release their first stable versions. The plan includes incorporating community feedback, finalizing public APIs, achieving 65% test coverage, providing detailed documentation, creating tutorials, and releasing version 1. The funding request is for 67,600 USDC from December 2024 to March 2025, for 3 months, 65 workdays, and 520 hours of work.

Building on the success and traction of proposals [#812](812) and [#948](948), which delivered:

-   **ReactiveDOT**: A PAPI FE library for React and Vue
    
    -   [Documentation](https://reactivedot.dev/)
        
    -   [GitHub](https://github.com/tien/reactive-dot)
        
-   **DOTConnect**: A wallet connector UI library
    
    -   [Documentation](https://dotconnect.dev/)
        
    -   [GitHub](https://github.com/tien/dot-connect)
        
-   **DOTConsole**: A Substrate developer console
    
    -   [Website](https://dotconsole.app/)
        
    -   [GitHub](https://github.com/tien/dot-console)
        

I am requesting funding to continue the development of ReactiveDOT and DOTConnect, with the goal of releasing their first stable versions.

## Goals

-   Incorporate community feedback and feature requests
-   Finalize public-facing APIs
-   Achieve at least 65% test coverage
-   Provide detailed API documentation and sample usage
-   Create improved tutorials
-   Release version 1

## Funding Request

-   **Period**: December 2024 to March 2025
-   **Duration**: 3 months / 65 workdays / 520 hours
-   **Requested Amount**: 67,600 USDC (@ 130 USDC/hour)

ReactiveDOT: funding request for the first stable version

staking_admin

treasurer

lease_admin

fellowship_admin

general_admin

auction_admin

referendum_canceller

referendum_killer

big_tipper

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