- An interview was held which gained popularity in late 2024.
- Gavin's first podcast was organized on Blockworks, a big platform for crypto news.
- The podcast was cohosted by Yano from Blockworks and Santiago R Santos, an important investor.
- The podcast is available to listen to online.
- A request for a tip was made for the work done since September 2024 for both projects.

[Big Tipper] Referendum #1519

- Polkadot plans to launch a new smart contract platform called Polkadot Hub in 2025.
- OpenZeppelin is helping Polkadot by providing tools and support for developers.
- OpenZeppelin's contracts are very popular, with a large amount of money transferred using them.
- They have a 19% share of all transactions across different networks.
- OpenZeppelin's contracts are used by all top 50 DeFi protocols.
- They are involved in many projects that improve security and privacy.
- The collaboration between OpenZeppelin and Polkadot has already begun to prepare for the new platform.

Polkadot&rsquo;s strategy in 2025 is driven by the release of a new EVM-compatible smart contract platform in Polkadot Hub as well as the continued evolution of Polkadot Cloud. As a follow on to the four OpenGov proposals OpenZeppelin completed in 2024 (<a href="https://polkadot.subsquare.io/referenda/105" target="_blank" rel="noopener">1</a>, <a href="https://polkadot.subsquare.io/referenda/442" target="_blank" rel="noopener">2</a>, <a href="https://polkadot.subsquare.io/referenda/892" target="_blank" rel="noopener">3</a>, <a href="https://polkadot.subsquare.io/referenda/1290" target="_blank" rel="noopener">4</a>), OpenZeppelin has been collaborating Parity to support the launch of Polkadot Hub in 2025 with developer enablement (Solidity contract libraries and tooling) and to continue to support Polkadot Cloud with iterative updates.
OpenZeppelin brings a wealth of experience in developer enablement to the ecosystem, especially as Polkadot moves to target native Solidity developers and widely-used DeFi protocols for Polkadot Hub launch. Not only has OpenZeppelin has been the &ldquo;point of entry&rdquo; for many developers who are first learning smart contracts, who study OpenZeppelin&rsquo;s contract libraries, such as the ERC20, ERC721, upgradeable, and so on, but OpenZeppelin contracts are the standard contracts that almost all protocols build upon:
<ul>
<li><a href="https://dune.com/openzeppelin/openzeppelin-contracts-metrics" target="_blank" rel="noopener">$20 Trillion USD</a> of total value has been transferred across OpenZeppelin contracts</li>
<li>Market Share of ~19% of all transactions on all chains</li>
<li>100% penetration for OpenZeppelin contracts across top 50 DeFi protocols</li>
</ul>
OpenZeppelin is on the leading edge of a number of cross-ecosystem initiatives, including interop, privacy/ZK, and standards creation. Most recently, OpenZeppelin wrote and audited the flagship feature of Uniswap v4, the <a href="https://blog.openzeppelin.com/introducing-openzeppelin-contracts-library-for-uniswap-v4-enhancing-security-and-innovation-with-hooks" target="_blank" rel="noopener">Hooks library</a>, and is currently developing a <a href="https://www.prnewswire.com/news-releases/taiko-and-openzeppelin-partner-to-develop-next-generation-based-rollup-stack-302359509.html" target="_blank" rel="noopener">based rollup stack</a> with Taiko.
With this experience, OpenZeppelin can be a strong strategic partner to Parity and the broader Polkadot Ecosystem in their mission to launch a new platform and attract a new generation of developers with Polkadot Hub.
The collaboration has already started, and OpenZeppelin is currently working with Parity following the completion of the last treasury proposal. This proposal provides a context for the official working relationship over the next year.
Please see the full proposal <a href="https://docs.google.com/document/d/1UmbQhXxlK7yLwqw1zj45PfC4Hf1OcbkSUEXMTOotRwM/edit?usp=sharing" target="_blank" rel="noopener">here</a>.

OpenZeppelin Support for Polkadot Hub and Polkadot Cloud in 2025

- This proposal asks for money to keep working on ReactiveDOT and its related projects like DOTConsole and DOTConnect.
- ReactiveDOT helps developers create applications for the Polkadot network more easily and quickly.
- Previous goals included improving the library's reliability, creating better documentation, and making tutorials easier to follow.
- Some achievements include better support for wallets and more efficient ways to manage data loading.
- Future goals include making it easier to support contracts, improving how data is loaded and displayed, and increasing testing coverage.
- The project is asking for funding from March 2025 to June 2025, for a total of 688 hours of work.
- They want to grow the developer community and make it simpler to create applications on the Polkadot network.

Funding for ReactiveDOT & related developments

Polkadot Next.js Starter

- A tool for developers to quickly create apps for Polkadot.
- It helps people get started faster, especially during hackathons.
- Features include wallet connections, integration with Polkadot's blockchain, and a stylish design using Tailwind CSS.
- The project has gained attention on Twitter with many views and likes.
- Future plans involve adding more features and fixing some issues.
- Funding is requested to support the development of this project.
- A demo and more information can be found on its GitHub page.

[Big Tipper] Polkadot Next.js Starter Frontend Template

- Subscan is asking for $249,250 to improve its services for tracking data in the Polkadot blockchain.
- They want to create better tools for both developers and users to access and interact with PolkaVM smart contracts.
- This project will include a new open-source explorer and contract verification tool, making it easier to check and use contracts.
- Subscan has been successful in the past and provides important insights for many blockchain users.
- The proposal aims to combine data from different networks into one easy-to-use platform to help everyone use blockchain better.
- The improvements will also support both new and existing networks without extra costs.
- Community feedback will be taken seriously to make sure the tools meet everyone's needs.

Subscan-PVM Integration: Building a Unified Explorer for the Polkadot Ecosystem

- Otar and Raul from JUST Ventures GmbH are asking for more money from the Polkadot Treasury for their work planned from April to December 2024.
- They have already received money for their previous work from December 2022 to March 2024.
- Their tasks include helping with updates, community projects, and providing technical support.
- They want to get paid in Stablecoins to make things easier and safer.
- They have a document that anyone can check to make sure their proposal is real.
- This request shows that the community thinks their work is important and wants them to keep going.

We, Otar and Raul of JUST Ventures GmbH, are submitting a second retroactive funding proposal to the Polkadot Treasury, following the approval of our first request covering 01.12.2022 &ndash; 31.03.2024. This new proposal seeks funding for our contributions from 01.04.2024 &ndash; 31.12.2024.
Over this period, our work has included supporting and executing runtime upgrades, facilitating OpenGov implementation, guiding treasury proposals, providing technical assistance, managing governance discussions, supervising bounties, and engaging in key ecosystem initiatives. We have also been involved in projects like the Polkadot Ecosystem Map and the Polkadot Community Foundation advisory process among others.
The requested funding will allow us to compensate for the work done and continue our work within the Polkadot ecosystem, focusing on governance, technical support, and community initiatives. By maintaining a retroactive funding model, we ensure that contributions are compensated based on actual work completed rather than estimated upfront. To further simplify financial planning, minimise volatility, and align with community standards, this time around, we are requesting compensation in Stablecoins.
Beyond financial reimbursement, the approval of this proposal also signals the community&rsquo;s intent for us to continue our work under these same retroactive terms.
We have generated a hash of the document associated with this proposal for verifiability. Anyone can confirm that the document has not been altered by downloading it as a PDF from Google Docs and computing its hash. If the resulting hash matches the value: 0x93aa396d605cb910d3448ae64cee1df47de699f46689b5b5cb9ea6158ab362cc the document is verified as authentic. Discussion Post:&nbsp;<a href="https://../post/2823"> https://polkadot.polkassembly.io/post/2823</a> Proposal: <a href="https://docs.google.com/document/d/1I15Vru9Q5bH7TFhWtEzvOS9Uz08D8WeFMH7dnQ0vYsM/edit?usp=sharing">HERE.</a>

JUST 2.0 Retroactive Compensation for Contributions to the Polkadot Ecosystem

- Polkassembly is a place where people can help make decisions for Polkadot and Kusama.
- They want money from the Polkadot Treasury to improve and keep Polkassembly running well in 2025.
- Key focus areas include making the site easier to use, preventing spam, and fixing identity issues.
- They plan to add support for more wallets and improve how users create proposals.
- Technical updates will use new technology for better performance and security.
- Polkassembly has many users, with over 145,000 visits in the last month and lots of comments and discussions.
- They have a budget of $530,671 for maintenance and development.

Polkassembly serves as Polkadot and Kusama's primary governance hub, enabling participation in on-chain governance, delegation, proposal discussions, and community voting.
This proposal seeks funding from the Polkadot Treasury to support Polkassembly's 2025 maintenance and key improvements in stability, user experience, and core features. It focuses on essential upgrades such as better UX/navigation, enhanced identity management, technical stability, and spam prevention &ndash; that will strengthen the platform&rsquo;s reliability and usability for the community
What&rsquo;s our focus with this proposal?
The primary focus for improvement is summarized as below:
<ol>
<li>Identity -
<ol>
<li>Increase stability in core flow.</li>
<li>Simplify things for multisig account identity setup and fix issues.</li>
<li>Add support for proxy-identity setup.</li>
<li>RPC connectivity issues to be resolved on priority.</li>
</ol>
</li>
<li>Comments AI summary &amp; load speed improvement.</li>
<li>Comments for Proxy and Multisig accounts revamp.</li>
<li>Proposal creation
<ol>
<li>Improve support for multi-asset proposals.</li>
<li>Improve the proposal creation process for different tracks and scenarios.</li>
<li>Add support for proposal creation through proxy and add support for multisig proposal creation.</li>
</ol>
</li>
<li>Add support for more wallets including Nova, Mimir, Polkagate Snap, Signet.</li>
<li>Improve hardware wallet connectivity and functionality across all features.</li>
<li>Redo the landing page to improve discovery and site navigation.</li>
<li>Improve the proposal&rsquo;s detailed view layout to make information more accessible</li>
<li>Site-idle connectivity issues and data loading.</li>
<li>Reduce steps in proposal creation &amp; bundle decision deposit.</li>
<li>Create a proxy management dashboard and explorer Improve UX and platform navigation.</li>
<li>Add product walkthroughs for new user onboarding.</li>
<li>Add support for OpenGov Nomination Pool wallet voting for all wallet types.</li>
<li>Add comment filtering (DV, Proposer, Verified Accounts, Wallet linked).</li>
<li>Improved Preimage management and add option to convert pre-image into proposal directly through all wallet types.</li>
</ol>
Technical Improvements
<ol>
<li>Upgraded to Next.js 15 with Turbopack support for improved development experience</li>
<li>Node 20 support (compared to Node 18 in v1)</li>
<li>Revamped Editor</li>
<li>Better organized component architecture. Overhauled state management with Jotai Atoms.</li>
<li>New design system Integration along with shadcn/ui component system.</li>
<li>Overhauled project configuration with focus on security for easier open-source contribution.</li>
<li>The API architecture has been overhauled to improve data organization and facilitate easier integration for community members.</li>
<li>The API now offers expanded content delivery capabilities, enabling the return of data in markdown, block and HTML formats.</li>
<li>The authentication mechanism has been updated to utilize HTTP cookies for session management, replacing the previous implementation that relied on local storage and JWT.</li>
</ol>
Other technical improvements and details can be found within the <a href="https://docs.google.com/document/d/17ueaWqQcWpYmskJhrg3s3PPsFGEyzc4qea4XI4aBerw/edit?usp=sharing">proposal document</a>.&nbsp;
Proposal 2024
Here&rsquo;s the <a href="https://app.ogtracker.io/bigSpender/483">OG tracker ref link</a> for our 2024 proposal and a <a href="https://docs.google.com/document/d/1iKgCOzIAMwFvIiYHl3PrBIQkxv5_pCdhdmRMIhFSvaA/edit?usp=sharing">detailed self report</a> with features and product updates from last year&rsquo;s proposal. We worked with some amazing video designers to create a Polkassembly 2024 roundup. Users can watch the video <a href="https://x.com/polk_gov/status/1874341508716933141/video/1">here</a>.
<video controls="controls" width="500" height="250">
<source src="https://firebasestorage.googleapis.com/v0/b/polkassembly-backend.appspot.com/o/ssstwitter.com_1738241513795.mp4?alt=media&amp;token=d2f86d97-4c99-4e21-baf6-1a408714c552" /></video>
Implementation Gallery&nbsp;
Several UI/UX enhancements are actively being developed to refine navigation, improve usability, and ensure a better governance experience.
<img src="https://i.ibb.co/Zz98ssJH/1.png" alt="Revamped Proposal Listing View" width="640" height="588" />
Revamped Proposal Listing View
<img src="https://i.ibb.co/whBV3c05/2.png" alt="Revamped Proposal Detail view" width="640" height="881" />
Revamped Proposal Detail view
<img src="https://i.ibb.co/G4dNzHpk/3.png" alt="Revamped Profile Page" width="640" height="1169" />
Revamped Profile Page
<img src="https://i.ibb.co/Pz3y70hb/4.png" alt="Spam Proposal Detailed View" width="639" height="542" />
Spam Proposal Detailed View
<img src="https://i.ibb.co/hJ5ZH6JR/5.png" alt="Spam comments" width="640" height="385" />
Spam Comments
<img src="https://i.ibb.co/wZdw3wYF/6.png" alt="Delegation Dashboard &amp; Chat with delegates" width="639" height="405" />
Delegation Dashboard &amp; Chat with delegates
<img src="https://i.ibb.co/dsMbsKH0/7.png" alt="Bounty Dashboard" width="640" height="391" />
Bounty Dashboard
<img src="https://i.ibb.co/kgzCVJyb/8.png" alt="Batch Voting" width="640" height="403" />
Batch Voting
<img src="https://i.ibb.co/tTbt7pMS/9.png" alt="Proxy Dashboard" width="640" height="519" />
Proxy Dashboard
<img src="https://i.ibb.co/V0MspcgC/10.png" alt="Analytics Dashboard" width="640" height="716" />
Analytics Dashboard
&nbsp;
Our stats reflect our continued dominance in the ecosystem
Theme Product Metric Engagement on Polkassembly
Number of users
<ul>
<li>Last 30 days visits - 145K&nbsp;</li>
<li>Total API Requests - 92M/month (Source: Cloudflare)</li>
<li>MAU - 97k (Source: Google analytics)</li>
</ul>
Number of comments
<ul>
<li>Total Number of Comments on Polkassembly - 13695</li>
<li>Total Percentage of comments in governance on Polkadot - 82.66% (6288/7607)</li>
<li>Total Percentage of comments in governance on Kusama - 68.2% (502/736)</li>
</ul>
Number of disucussions
<ul>
<li>Total Number of Discussions on Polkassembly &mdash; 2206</li>
<li>Total Percentage of discussions in governance on Polkadot - 93.69% (698/745)</li>
<li>Total Percentage of discussions in governance on Kusama - 76.19% (32/42)</li>
</ul>
Number of Proposals
<ul>
<li>Total Percentage of proposals in governance on Polkadot - 39%+</li>
<li>Total Percentage of proposals in governance on Kusama - 20%</li>
</ul>
Source: Polkassembly Firebase
Views
Total Views last 4 months: 750K+ (Polkadot + Kusama)
Source: Polkassembly Firebase
Identity Verification
Number of Judgements provided
Total Percentage of judgements Polkadot - 52.22% (1216/2327)
<table style="border-collapse:collapse; width:52.9907%; height:30px;" border="0.5" cellspacing="0.1">
<tbody>
<tr>
<td style="width:50.085%; height:84px;">
Category&nbsp;
</td>
<td style="width:49.9163%; height:84px;">
Amount (US$)&nbsp;
</td>
</tr>
<tr>
<td style="width:50.085%; height:49px;">
Infrastructure &amp; Maintenance (12 months)
</td>
<td style="width:49.9163%; height:49px;">
$203,659
</td>
</tr>
<tr>
<td style="width:50.085%; height:49px;">
Development Budget
</td>
<td style="width:49.9163%; height:49px;">
$327,012
</td>
</tr>
<tr>
<td style="width:50.085%; height:10px;">
Total
</td>
<td style="width:49.9163%; height:10px;">
$530,671
</td>
</tr>
</tbody>
</table>
The budget calculations can be found <a href="https://docs.google.com/spreadsheets/d/1gQeTVOccQofkIcxJDqafQ657P_cSMmTiFK6Gck3xfeA/edit?usp=sharing">here</a>.&nbsp;
Refer to the full proposal document <a href="https://docs.google.com/document/d/17ueaWqQcWpYmskJhrg3s3PPsFGEyzc4qea4XI4aBerw/edit?usp=sharing">here</a>.&nbsp;

Polkassembly Social Contract 2025

- Polkadot-API is a set of tools for making apps that work on a blockchain.
- The team is improving the tools to help developers create better apps.
- They have added new features and shared tech demos to show what the tools can do.
- The team is asking for money to keep working on Polkadot-API from February to December 2025.
- They have a plan to follow if they get the money, including signing agreements and invoicing.
- There is a budget set aside for legal costs, and any leftover money will go back to a special fund.
- You can read more details in their proposal linked in the message.

Hi everyone,
As many of you may already know, <a href="https://github.com/polkadot-api/polkadot-api">Polkadot-API</a> was envisioned to provide a robust and flexible suite of libraries that prioritize composability, modularity, and a light-client-first approach. Our goal remains to equip dApp developers with powerful tools that simplify the creation of truly decentralized applications while continuously refining the developer experience.
Over the past development cycles, we have introduced new features and enhancements to Polkadot-API, along with additional libraries that complement and expand its capabilities. We've also released a series of tech demos that are valuable in their own right, while also showcasing the potential of these libraries. A detailed breakdown of our recent progress can be found in our <a href="https://forum.polkadot.network/t/polkadot-api-2025-q1-update/11906">latest update on the Polkadot forum</a>.
We are seeking funding for ongoing development and maintenance through the <a href="https://wiki.polkadot.network/docs/polkadot-community-foundation">Polkadot Community Foundation</a>, for the months from February 2025 to December 2025. As outlined in their documentation, the beneficiary is their address in AssetHub.
You can review all the details of the proposal in the following Google Doc: <a href="https://docs.google.com/document/d/1fZedk7Q0yEkJ9cAtl_IaAgQLr3vjSWdPjvhjC4UN5Oc">https://docs.google.com/document/d/1fZedk7Q0yEkJ9cAtl_IaAgQLr3vjSWdPjvhjC4UN5Oc</a>
Once the referendum is approved, the PCF and Polkadot-API team will go through the following process:
<ul>
<li>Create and sign a contractual agreement.</li>
<li>Complete the KYC/KYB process.</li>
<li>The Polkadot-API team will invoice the PCF for the 2025 development of Polkadot-API.</li>
<li>The PCF will transfer the proposal amount in USDC to our address in AssetHub (12R1XCdgkHysv8Y4ntiXguo4eUYHXjQTmfRjL8FbmezsG71j) in a single transfer at the beginning.</li>
</ul>
We have allocated a buffer of $7,000 for PCF legal and operational costs. After the process is complete, the PCF will refund the remaining amount back to the Polkadot Treasury.
Thank you for your support.
Polkadot-API Dev Team (@Josep, @carlosala, and @voliva)

Polkadot-API 2025 Development Funding through Polkadot Community Foundation

- A new proposal is being made to improve how users can move assets from Ethereum to Polkadot using Snowbridge.
- Many users are frustrated because they can't use their assets once they bridge them, mainly due to not enough liquidity (availability of money) in the system.
- The proposal asks for about $2,000 in DOT tokens to help create a better system for users to pay fees.
- This money will be used to increase the available liquidity for users, making it easier for them to swap assets.
- The goal is to have users enjoy a better experience and help them use their assets throughout the Polkadot ecosystem.
- The funds will be managed by two trusted people to ensure everything is done correctly.
- Overall, this will help more people use Polkadot and make it a better place for everyone.

Provision of Snowbridge ETH Liquidity to Facilitate Fee Swaps

Peer3 is developing an open-source Software Development Kit (SDK) that allows users to execute smart contracts directly with one another, bypassing the need to route each interaction through the blockchain. This project aims to improve the user experience of Polkadot by providing a real-time execution environment without any transaction fees. The SDK enables real-time, seamless interactions, inherits security from distributed ledgers, and eliminates unnecessary transaction fees. The has project successfully delivered all milestones for a Level 3 Grant from the Web3 Foundation.

The goal of this proposal is to seek treasury funding for a production version of the SDK. The team is asking for 350k USDT upfront and a delayed payment after 6 months for 250k USDT and 30k DOT. The funds will be used to hire more top talent to work on the SDK full time and cover operational costs. The DOT portion of the payment will be used for reserves to pay bonuses/incorporate into the compensation structure of the team and align their long-term financial interests with the Polkadot ecosystem.

The Peer3 SDK has the potential to unlock new possibilities for Web3 adoption and transform industries by providing real-time, decentralized solutions that redefine blockchain technology.

Peer3 SDK - real time peer-to-peer smart contracts 

- This proposal aims to improve how users can transfer USDT and USDC, which are stablecoins, to the Polkadot system.
- Many users face difficulties because there's not enough liquidity to use these stablecoins once they arrive in Polkadot.
- The proposal asks for funds to create liquidity pools so users can swap their stablecoins for DOT tokens, which they need to pay fees.
- The plan includes converting the stablecoins to wrapped versions and creating pairs with DOT on Polkadot Asset Hub.
- Fixing these issues will help more people use the Polkadot ecosystem, as it currently makes onboarding hard for new users.
- The funds will be managed by a two-person multisignature team to ensure safety.
- The aim is to provide a better user experience and encourage more people to use Polkadot's tools.

Provision of Snowbridge-Wrapped USDT & USDC Liquidity to Facilitate Fee Swaps

Statescan is a tool for exploring certain blockchain networks. Here are some key points about it:

- It started in 2021 and helps people track Polkadot, Kusama, and other related chains.
- Statescan is open source, which means anyone can see and use its code for free.
- It is used by many different blockchain projects, including Nexus, Litentry, and Crust.
- The tool needs servers and a domain to work properly, costing around €3,051 in total for 18 months.
- Maintenance work involves keeping the servers running smoothly and fixing any issues that arise.
- There are plans for new features, which would cost $6,400 to develop.
- The total estimated cost for everything is around $67,051.

[Statescan](https://github.com/opensquare-network/statescan-v2) is an explorer solution for substrate based chains. We have been serving polkadot/kusama and related chains since 2021. Compared to explorers like subscan, it provides a 100% open source and low cost candidate for ecosystem projects.

Besides polkadot system chains, followings chains has adopted statescan as their explores:  Hyperbridge([Nexus](https://nexus.statescan.io/), [gargantua](https://gargantua.statescan.io/)), [Heima(Litentry)](https://heima.statescan.io/), [Invarch](https://invarch.statescan.io/), [Polimec](https://polimec.statescan.io/), [Laos](https://laos.statescan.io/),, [Crust](https://crust.statescan.io/), [Shadow](https://shadow.statescan.io/), [Tangle](https://tangle.statescan.io/), [Tanssi testnet](https://stagelight.statescan.io/), [Argon](https://argon.statescan.io/). There are also projects who deployed statescan by theirselves like [Subsocial](https://explorer.subsocial.network) and [Edgeware](https://edgscan.ink).


## Infrastructure

| Items      | Details                       | per month | Months | Total  |
|--------------|-------------------------------|-----------|--------|--------|
| Servers | 8 servers + 1.3TB volume | €157.12     | 18      | €2828 |
| Domain | 1 io domain |-     | 18      | $89.78 |
| Total |  | -    | 18      | $3051 |


## Maintenance

The maintenance work mainly includes:

- Server deployment maintenance: daily server monitor, upgrading products versions, emergency handling, etc.
- Codebase maintenance: code refactor, bug fixes, UI tweaks, dependency upgrading, etc.

Please check the [changelog](https://github.com/opensquare-network/statescan-v2/blob/main/CHANGELOG.md) and [commits](https://github.com/opensquare-network/statescan-v2/commits/main/) for more details. We will request 5 FTE days equivalent work per month.

## Common features development

| Item        | Workload            | Cost   |
|-------------|-------------------|--------|
| Support EVM transactions indexing and fronted page, check [issue #974](https://github.com/opensquare-network/statescan-v2/issues/974) | 1 FTE * 1 week, 40 hrs | $3,200 |
| More system chains support, check [issue #987](https://github.com/opensquare-network/statescan-v2/issues/987) | 1 FTE * 1 week, 40 hrs | $3,200 |
| Total | 80 hrs | $6,400 |

## Total cost

| Item        | Workload            | Cost   |
|-------------|-------------------|--------|
| Infrastructures | servers and domains | $3051 |
| Maintenance | Code refactor, UI tweaks and polish, bug fixes, etc; | 57,600 |
| Common features development | Please check the development section | $6,400 |
| Total | - | 67,051 |

Statescan maintenance proposal from 2023.10 to 2025.03

- A group called Bifrost and Hyperbridge is asking for 795,000 DOT.
- They want to help make it easier for people to use DOT in different places.
- They noticed that not many people or money can get into Polkadot, which slows down its growth.
- Their plan is to give rewards for providing DOT liquidity in other networks like Arbitrum and Ethereum.
- The aim is to make DOT more popular and used widely in the web3 space.
- This will help developers and users join the Polkadot ecosystem better.
- The idea started as a group project but had to be split into smaller parts.

Polkadot DeFi Singularity

Brave x Polkadot Wallet Integration Proposal

- Brave is planning to add Polkadot features to its wallet to help its many users access more cryptocurrencies.
- The proposal includes making the wallet secure and easy to use for over 80 million active users.
- Brave will spend $3 million to ensure everything works well over 12 months and keep it updated for 2 more years.
- Users will be able to manage Polkadot and Kusama accounts directly from the Brave Wallet.
- This integration will allow people to quickly send cryptocurrencies and participate in Polkadot governance.
- All the code for this project will be shared publicly to help other developers.
- This new feature is expected to attract even more users to the Polkadot community.

<h1>Brave x Polkadot Wallet Integration Proposal</h1>
Updated: 2/20/25
<h2>Summary of Changes Made</h2>
<ul>
<li>Clarified Smoldot integration, SCALE codec, and Substrate transaction handling in the milestones.</li>
<li>Expanded User Interface and Experience section to highlight how Polkadot and Kusama will be integrated into Brave Wallet.</li>
<li>Emphasized Brave&rsquo;s C++ security model, including process isolation for vulnerable components.</li>
<li>Strengthened investment justification by detailing why Brave must port JavaScript-based functionalities into C++.</li>
<li>Updated open-source commitment to confirm that Brave will release all Polkadot-related code.</li>
<li>Added Brave&rsquo;s $100K ad credit to Polkadot upon proposal approval.</li>
</ul>
<h2>Executive Summary</h2>
This proposal outlines the native integration of Polkadot functionality into Brave&rsquo;s self-custody wallet, granting Brave&rsquo;s 80M+ monthly active users direct access to the Polkadot and Kusama ecosystems. This integration will be implemented natively in Brave&rsquo;s core C++ architecture over 12 months, ensuring maximum security, privacy, and performance, while also committing to a 24-month maintenance period for ongoing updates and optimizations.
<h2>Market Opportunity &amp; Impact</h2>
Brave's extensive user base provides a significant opportunity for Polkadot adoption:
<ul>
<li>80M monthly active users</li>
<li>34.71M daily active users</li>
<li>20.8M potential developers (25% of the user base)</li>
<li>Strong crypto adoption (60% involved in staking, 20% own NFTs)</li>
</ul>
By integrating Polkadot natively, Brave Wallet will streamline user access to Web3, facilitating secure XCM-based cross-chain transfers, governance participation, and direct dApp interactions.
<hr />
<h2>Value Proposition &amp; Investment Request</h2>
<ul>
<li>Total Investment: $3,000,000 USDC</li>
<li>Development Timeline: 12 months</li>
<li>Maintenance Period: 24 months</li>
<li>Total Commitment: 36 months</li>
</ul>
<h3>Development Milestones &amp; Deliverables</h3>
<h4>Milestone 1: Research &amp; Polkadot HD Keyring&nbsp;</h4>
<ul>
<li>Polkadot BraveWallet integration UX research.</li>
<li>Polkadot HD Keyring support.</li>
<li>Polkadot\Kusama account creation, ss58 address space support.</li>
<li>BraveWallet architecture adoption to support parachain network layer abstraction.</li>
<li>Security audit.</li>
</ul>
<h4>Milestone 2: Relay chains support&nbsp;</h4>
<ul>
<li>Smoldot integration\implementation over Chromium network stack. Own implementation may be required.</li>
<li>SCALE codec integration\implementation. Own implementation may be required.</li>
<li>Substrate transaction creation and signing implementation.</li>
<li>Balance pallet integration.</li>
<li>Relay chain native tokens support: balance resolution, transaction creation, fee calculation, recipient validation, transaction signing&amp;posting flow, transaction status subscription, blockexplorer integration.</li>
<li>Security audit.</li>
<li>QA.</li>
</ul>
<h4>Milestone 3: Network &amp; Parachains support&nbsp;</h4>
<ul>
<li>Parachains metadata fetching, parsing and compatibility verification.</li>
<li>Substrate Parachains integration into the wallet flow(top 5-10 parachains): supported parachains list, account details page, settings, portfolio, send screen, transaction details, recipient list integration.</li>
<li>Most used pallets support - assets, balances, nfts.</li>
<li>Security audit.</li>
<li>QA.</li>
</ul>
<h4>Milestone 4: Assets support</h4>
<ul>
<li>EVM based parachains integration based on existing BraveWallet codebase.</li>
<li>Cross-chain tokens support - cross-chain transactions.</li>
<li>Implement native support of bridges between Brave Wallet supported blockchains and Polkadot.</li>
<li>Security audit.</li>
<li>QA.</li>
</ul>
<h4>Milestone 5: Ecosystem Integration &amp; Deployment&nbsp;</h4>
<ul>
<li>dApps connection support using native C++ implementation of window.polkadot.</li>
<li>Ledger support - import account, sign transactions.</li>
<li>Security audit.</li>
<li>QA.</li>
</ul>
<hr />
<h2>Technical Architecture Overview</h2>
<h3>Core Implementation Strategy</h3>
<ul>
<li>Native C++ integration in Brave&rsquo;s core (No JavaScript dependencies)</li>
<li>Custom Polkadot HD Keyring implementation.</li>
<li>Custom transaction creation and signing component.</li>
<li>Dynamic metadata retrieval to support Polkadot&rsquo;s runtime upgrade model</li>
<li>Smoldot-based RPC connectivity over Chromium network stack for decentralized network access</li>
<li>Process isolation for potential vulnerable parts of code</li>
</ul>
<h3>Polkadot-Specific Integration</h3>
<ul>
<li>EVM and Substrate based parachains integration.</li>
<li>Support for Polkadot and Kusama parachain assets &amp; XCM transactions</li>
<li>Automated runtime metadata updates for compatibility with evolving networks</li>
<li>Secure <code>window.polkadot</code> provider in C++ for efficient dApp connectivity</li>
</ul>
<hr />
<h3>User Interface and Experience</h3>
The screenshots below illustrate the current state of Brave Wallet&rsquo;s account creation, hardware wallet import, and network selection interfaces. These images provide insight into how Polkadot will be incorporated into Brave Wallet&rsquo;s multi-chain experience.
<ol>
<li>Account Creation &amp; Import: Users can create and manage accounts for various blockchains, including Ethereum, Solana, Bitcoin, and Filecoin. With this integration, Polkadot and Kusama will be added to this interface, allowing users to create and manage DOT and KSM accounts directly within Brave Wallet.</li>
<li>Hardware Wallet Support: Brave Wallet enables users to connect hardware wallets to manage their crypto securely. Polkadot Ledger support will be introduced, allowing users to store and transact with DOT and parachain assets securely.</li>
<li>Network Selection: Users currently choose from a variety of networks, such as Ethereum, Solana, and Bitcoin. Polkadot and Kusama will be integrated as primary networks, ensuring that users can interact with the Polkadot ecosystem natively without needing external extensions.</li>
</ol>
<h3>Where Polkadot Will Be Featured</h3>
<ul>
<li>Polkadot and Kusama will be available in the &ldquo;Create Account&rdquo; and &ldquo;Import from Hardware Wallet&rdquo; sections of Brave Wallet.</li>
<li>DOT and KSM will be added to the &ldquo;Select Networks&rdquo; menu, allowing users to toggle between multiple blockchain ecosystems.</li>
<li>XCM-based cross-chain functionality will be incorporated, enabling users to move assets between Polkadot parachains directly through Brave Wallet.</li>
<li>Polkadot governance and staking will be integrated, allowing users to participate in Polkadot&rsquo;s decentralized governance directly from Brave.</li>
</ul>
These updates ensure that Brave Wallet becomes a true multi-chain platform, where Polkadot users can interact with the ecosystem.
<h2><img src="https://i.ibb.co/C59XrJHN/Screenshot-2025-02-20-at-9-57-00-AM.png" alt /></h2>
<h2><img src="https://i.ibb.co/p6XHfRxd/Screenshot-2025-02-20-at-9-57-14-AM.png" alt /></h2>
<h2><img src="https://i.ibb.co/VcJGyg2m/Screenshot-2025-02-20-at-9-58-06-AM.png" alt width="640" height="288" /></h2>
<h2>Success Metrics &amp; Justification for $3M Investment</h2>
<h3>Technical KPIs</h3>
<ul>
<li>99.9% wallet uptime</li>
<li>&lt;3 second transaction processing</li>
<li>Zero critical security incidents</li>
<li>100% parachain compatibility</li>
<li>Cross-chain transaction success rate exceeding 99%</li>
</ul>
<h3>Investment Justification</h3>
<ul>
<li>Brave&rsquo;s security model requires all network interactions, signing, and chain logic to be implemented in C++ instead of JavaScript-based solutions.</li>
<li>Comprehensive security reviews and dependency audits increase development costs.</li>
<li>Brave must port key functionalities from JavaScript libraries into C++ to meet privacy and security requirements.</li>
<li>The code must be integrated into the Chromium and Brave Wallet codebases, considering their limitations and established patterns.</li>
<li>A long-term commitment (24 months of maintenance) ensures continuous support, updates, and ecosystem stability.</li>
</ul>
<hr />
<h2>Open Source &amp; Long-Term Commitment</h2>
<ul>
<li>Brave will open-source all code related to the Polkadot integration.</li>
<li>24-month maintenance commitment includes security patches, feature updates, and long-term support.</li>
<li>Brave Ads will be leveraged to drive awareness and adoption of Polkadot&rsquo;s integration. Upon approval of this proposal, Brave wll grant a $100k ad credit to Polkadot and its ecosystem.</li>
</ul>
<hr />
<h2>Conclusion</h2>
This integration represents a significant milestone for Polkadot adoption, onboarding millions of new users through Brave's privacy-first, security-focused browser environment. By implementing a fully native, high-performance C++ integration, Brave Wallet will serve as a gateway to Web3, enabling cross-parachain transactions, and dApp interactions&mdash;all without requiring third-party extensions. Brave Wallet supports multiple blockchains, including ETH, BTC, SOL, ZEC, and FIL, enabling seamless native cross-integration with the Polkadot ecosystem.
This proposal ensures long-term ecosystem growth, open-source contributions, and measurable adoption metrics, making it a strategic win for both Brave and Polkadot.
<h1>About us</h1>
<a href="https://brave.com/">Brave</a> is a privacy-focused browser and search engine committed to empowering users with control over their online data and experiences. Our integrated <a href="https://brave.com/wallet/">Brave Wallet</a> provides a seamless way to access Web3 with support for Ethereum, EVM chains, Solana, Bitcoin, and NFTs - no extensions required. Brave Rewards, our privacy-preserving ad platform, has the most crypto-centric audience available today.
Founded by JavaScript creator <a href="https://x.com/BrendanEich">Brendan Eich</a>, Brave is an open-source project fostering innovation through transparency and collaboration. The key team members involved in this proposal are:
<ul>
<li>Carlos Acevedo &mdash;&nbsp; Senior Director, Business Development &mdash; <a href="https://x.com/_CarlosAce_">X</a>, <a href="https://www.linkedin.com/in/clacevedo/">LinkedIn</a></li>
<li>James Mudgett &mdash; VP, iOS, Web 3 &mdash; <a href="https://x.com/jamesmudgett">X</a>, <a href="https://www.linkedin.com/in/jamesmudgett/">LinkedIn</a></li>
<li>Oleg Isupov &mdash; Brave Wallet &mdash; X, <a href="https://www.linkedin.com/in/oleg-i-02845894/">LinkedIn</a></li>
<li>Luke Mulks &mdash;&nbsp; VP, Business Operations &mdash; <a href="https://x.com/lukemulks">X</a>, <a href="https://www.linkedin.com/in/pureproductions/">LinkedIn</a></li>
<li>Angelina Kraminkina &mdash;&nbsp; Senior Client Success Manager, Enterprise &mdash; <a href="https://x.com/lina_kram">X</a>, <a href="https://www.linkedin.com/in/angelina-kraminkina/">LinkedIn</a></li>
</ul>
Major brands across industries have trusted our advertising platforms, including Verizon, Ford, Lufthansa, Crocs, Venom, Mayfair, eToro, Crypto.com, Solana, Upland, Near, and Nexo.
With privacy at its core, Brave aims to improve the way we interact with both Web 2.0 and Web3.

Polkadot + Brave Wallet: Driving Adoption Through Native Integration

- Subsquid Labs is asking for $264,838.09 to help with the costs of running data archives for Polkadot and Kusama.
- Archives provide important historical data for different projects in the Polkadot ecosystem, allowing them to access and explore on-chain data.
- In Q2 2024, there was a huge increase in the demand for archival data, going from 110.6 GiB to about 3,095.17 GiB.
- They launched the SQD mainnet, which helps make the Polkadot network more decentralized and secure.
- Subsquid Labs improved their tools for developers, like adding new features for data queries and access control.
- During Q2 2024, they served a large amount of data, cutting across different public chains while handling many archive requests.
- The team upgraded their Cloud API to better support Polkadot's growth and make it easier for developers to build applications.

Summary 
Proponent: <a href="https://polkadot.subscan.io/account/13bfKSQXoBn3AMLtZaW6BKv797fqZzsD3PYF6xpJDir3tdoE">Subsquid Lab Official</a> - 13bfKSQXoBn3AMLtZaW6BKv797fqZzsD3PYF6xpJDir3tdoE Beneficiary: <a href="https://polkadot.subscan.io/account/13bfKSQXoBn3AMLtZaW6BKv797fqZzsD3PYF6xpJDir3tdoE">Subsquid Lab Official </a>- 13bfKSQXoBn3AMLtZaW6BKv797fqZzsD3PYF6xpJDir3tdoE
Contact Details:
Subsquid Labs GmbH
6300 Zug, Switzerland
Short description: Ongoing development and maintenance costs for public SQD Archives
Archive raw data: <a href="https://docs.google.com/spreadsheets/d/1qTLup1JU9XPsklciZDeHVbd-EtP1AvdP4zzI5rm4bSU/edit?gid=1549354589#gid=1549354589">Archive Infrastructure Metrics</a> - April, May, June
Requested: $264,838.09
Previous proposals: <a href="referenda/1193">https://polkadot.polkassembly.io/referenda/1193</a>
Motivation
A) Archives
Archives are an important piece of Polkadot and Kusama data infrastructure provided by SQD (formerly Subsquid). They provide access to on-chain data for public chains in the Polkadot ecosystem. They are being used as a data source for Squids and for efficient data exploration and ad-hoc queries.
The Archives, as performant data sources of historical on-chain data, are critical to the operation of backend APIs run by major projects in the Polkadot ecosystem (the list is not exhaustive): 
<ul>
<li>Tanssi Network</li>
<li>Talisman Wallet</li>
<li>Polimec</li>
<li>Polkassembly</li>
<li>Apillon</li>
<li>Hydration</li>
<li>Giant Squid API (maintained by LimeChain, see details below)</li>
<li>SubWallet</li>
<li>FiDi</li>
<li>KodaDot</li>
<li>RMRK</li>
<li>ChainSafe (in particular the Multix multi-sig, as well as other projects)</li>
<li>Phala Network</li>
<li>Stellaswap</li>
<li>Polkascan</li>
</ul>
Since the first quarter of 2024, SQD has transitioned to a paid model for supporting parachains. However, public chains continue to be available for free use. Throughout the second quarter of 2024, we provided a free public data indexing service for Substrate blockchains, allowing interested parties to access indexed data on Substrate Events, Extrinsics, Storage Items, and EVM logs. Below is a list of the public chains we currently support at no cost:
<ul>
<li>polkadot</li>
<li>kusama</li>
<li>asset-hub-kusama</li>
<li>asset-hub-polkadot</li>
<li>bridge-hub-polkadot</li>
<li>collectives-polkadot</li>
<li>rococo</li>
<li>westend-collectives</li>
</ul>
As of Q1 2024, SQD has sunsetted support for Giant Squid, with LimeChain taking over its further development, detailed in the proposal at <a href="treasury/758">https://polkadot.polkassembly.io/treasury/758</a>
B) Contribution
During Q2&rsquo;2024, we made significant contributions to support ink! v5 and address actual use cases that were highly demanded by the community:
<ul>
<li>We provided support for manual finality confirmation in the subsquid/substrate-processor for cases where a chain does not expose finalization details</li>
</ul>
Achievements
Increase in Archival Data Demand and Infrastructure Scaling
During Q2, archival data demand increased approximately ~28,1 times, from 110,6 GiB to 3.095,17 GiB. We addressed the increasing demand for archival data by enhancing our infrastructure's throughput and redundancy through deploying archives to OVHCloud in addition to GCE, while also empowering our maintenance and engineering teams to support the expanded infrastructure effectively.
Mainnet Launch and Decentralization of the SQD Network Enhancing the Polkadot Ecosystem:
In Q2&rsquo;24, we successfully launched the SQD mainnet, a pivotal advancement that significantly strengthens the Polkadot ecosystem's decentralization and resilience. By the end of the quarter, the SQD network comprised 726 Worker Nodes online, securely storing 529 TB of data and serving ~ 9 TB of data a day. This decentralized infrastructure enhances data processing and storage capabilities, ensuring higher security, fault tolerance, and scalability for the Polkadot network.
Advancements in Squid SDK Empowering Polkadot Developers:
<ul>
<li>Manual Finality Confirmation Configuration: Enabled manual configuration of finality confirmation for subsquid/substrate-processor in cases where a parachain does not expose finalization information</li>
</ul>
Cloud API Upgrades:
We upgraded our Cloud API to offer enhanced capabilities that support the growth of the Polkadot ecosystem:
<ul>
<li>Multiple API Tokens Support: Allows for more granular access control and better management of development workflows.</li>
<li>Hasura Integration: Enables more efficient and powerful data querying and manipulation, facilitating the creation of responsive and data-driven applications.</li>
<li>Chain ID and SS58 Prefix support: Enhanced network identification and management for seamless interoperability across Polkadot parachains</li>
</ul>
&nbsp;
<img src="https://i.ibb.co/fzqcqvCf/Screenshot-2025-02-17-120923.png" alt="" width="591" height="369" />
Over the course of Q2 2024:
<ul>
<li>Served a total of 3,505,904,767,634 (~3.19 TiB) of data from the substrate based archives in Q2 2024</li>
<li>Served 301 069 archive requests from substrate based archives in Q2 2024</li>
<li>The highest daily total data transfer recorded for Substrate was 161.646 GiB within a single 24-hour period.</li>
</ul>
Costing
This proposal encompasses the combined costs for running Archives for Polkadot, Kusama, and other public chains, along with the development contributions, amounting to a total of $264,838.09. <a href="https://docs.google.com/spreadsheets/d/1qTLup1JU9XPsklciZDeHVbd-EtP1AvdP4zzI5rm4bSU/edit?gid=1549354589#gid=1549354589">Raw data for Archives can be seen here</a>.
<img src="https://i.ibb.co/9m5K9cKW/Screenshot-2025-02-17-120945.png" alt="" />
<img src="https://i.ibb.co/B2LMJWqw/Screenshot-2025-02-17-120932.png" alt="" />

SQD (fka Subsquid) - Public data indexing Infrastructure for Polkadot and Kusama (Q2 2024)

- LimeChain is now in charge of GiantSquid, a tool that helps find data in the Polkadot system.
- They created a report about their work and talked to users to gather feedback.
- Based on this feedback, they have a new plan called "Phase 2 for Giant Squid."
- Phase 2 includes new features like making it easier to find cross-chain transfers and track staking and voting.
- They will also make a new table to show all account events at once, which will be easier to use.
- They are asking for **169,520 USDC** to help pay for the new features and other costs.
- Feedback from the community is very welcome, and they hope to turn it into a treasury proposal.

With <a href="618">Referendum #618</a>, LimeChain took over the development and maintanance of GiantSquid (fka as Subsquid), which is an indexing tool in the Polkadot ecosystem, providing access to on-chain data in the form of GraphQL gateways. Since then, we have delivered on the treasury proposal, proactively talked to users and ecosystem members, and published a detailed delivery report. More details on community feedback can be found in the progress report of <a href="618">Referendum #618</a> .
Based on user feedback, we&rsquo;ve scoped out a list of upgrades in a new proposal which we&rsquo;re calling a &ldquo;Phase 2 for Giant Squid&rdquo;.The full proposal document for Giant Squid Phase 2 can be read <a href="https://docs.google.com/document/d/1FkQY0erT2LsLbK03-AnJ9RrRnFDVtPxI/edit?usp=sharing&amp;ouid=113946912904115479410&amp;rtpof=true&amp;sd=true">here in google docs</a>.
TLDR:
In Phase 2 we plan to implement XCM transaction indexing, making cross-chain transfers easily searchable. By indexing nomination pools and conviction voting, we enable detailed tracking of staking and governance participation. A new &ldquo;History Elements&rdquo; table will consolidate all account-related events into a single dataset, simplifying queries for wallets and applications. Staking analytics will be improved with APR calculations and validator selection insights. NFT indexing will allow users to retrieve owned assets, while a feasibility study will explore cross-chain NFT tracking. Additionally, we will research real-time mempool indexing to provide better transaction visibility before finalization. Giant Squid will also boast a new homepage that greatly improves usability. These upgrades will make Giant Squid a more powerful and user-friendly indexer for the ecosystem.
The total treasury request for this proposal is 169,520 USDC, of which 94,520 are development costs and 75,000 are estimated infrastructure costs from March 2025 till December 2025 inclusive. The infrastructure estimation is based on historical infrastructure expenses (currently at about $7.5k a month)&nbsp; + an usage growth assumption from the delivery of Phase 2 onwards. The infrastructure up until now is being covered with remaining funds from <a href="618">Referendum #618</a>.
Any additional feedback or ideas for the upgrade of GiantSquid are greatly appreciated. We would love to hear the community feedback on this and potentially move it to a treasury proposal.

Giant Squid Phase 2

- The RegionX parachain is creating a new marketplace for something called Coretime, making it easy and safe for people to buy and sell.
- They want to use DOT, a special kind of money used on Polkadot, to help manage the parachain and make decisions.
- Right now, Coretime is very cheap, but many projects still need it, and there could be more demand later.
- They believe Polkadot is the best place for these projects and want to attract more teams to join.
- The marketplace will help projects get Coretime even after the main sale is over.
- They don't want RegionX to be a system chain because they believe it’s better to have a focused team to take care of it.
- They are seeking funding to launch this project and improve its design.

RegionX - Coretime Marketplace Production Deployment Phase 1

- FluffyLabs is proposing to improve the Gray Paper Reader, a tool that helps everyone understand the Gray Paper for JAM, which is about Polkadot Cloud.
- The Gray Paper Reader allows users to share, annotate, and track changes in the document easily.
- They are asking for $21,000 to continue this work and have already started developing the tool.
- The Gray Paper is very detailed but can be hard to read and keep updated.
- The Reader has features like switching between versions, sharing links, and attaching notes.
- It is open-source, meaning anyone can use and improve it.
- The team working on this has prior experience with retroactive funding for another tool called the PVM Debugger.

Treasury Spends