candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

Postmortem: Polkadot 2.0.1 Release

Kian Paimani

Polkadot 2.0 &amp; Hub migration celebration thread :partying_face:

Alexander Mitrovich

Polkadot 2.0 & Hub migration celebration thread 🥳

Does Kusama Asset Hub actively accept anything other than Kusama?

The Forum serves as a digital town square to co-create the future of Polkadot by the ecosystem, for the ecosystem. Suggestions on how to improve the Forum live here.

The Forum serves as a digital town square to co-create the future of Polkadot by the ecosystem, for the ecosystem. Suggestions on how to improve the Forum live here.

Polkadot Forum Meta

Welcome to the Polkadot Forum :waving_hand:

Rajesh Shirsagar

Welcome to the Polkadot Forum 👋

Getting started: Read this first

Polkadot Forum Super Admin

Why is Polkadot officially recommending Fearless Wallet despite zero support, zero response to theft, and confirmed app vulnerability?

If you’re looking for discussion or discourse for anything and all things Tech related, then this is the place for you. .

Tech Talk

[Revive] Solidity contracts using a polkadot signer

Victor Oliva

Select * from polkadot;

Parity Data

Runtime release notification for v2.0.1 [06.11.2025]

Anaelle LTD

Whether you’re new to Polkadot’s Governance or an OpenGov OG, this is the place for you to get involved and join the discussion.

Governance

Treasury Guardianship

Marketing Bounty Deep Dive

Transparency in DN Validator Selection — Community Concerns

Polkadot Global

If you’re looking for discussion or discourse for anything and all things Ecosystem, then this is the place for you. .

Ecosystem

Encrypted Mempools: Turning Polkadot&rsquo;s MEV Leak into Treasury Revenue

SO/DA zone

Encrypted Mempools: Turning Polkadot's MEV Leak into Treasury Revenue

Asset Hub Migration 2025

Joyce Siqueira

Polkadot Digest 07 November 2025

Radhakrishna Dasari

If you’re looking for discussion or discourse for anything and all things Ambassador related, then this is the place for you. .

Ambassador Programme

Polkadot Ambassador Fellowship (PAF) Governance: Critical Questions Before On-Chain Implementation

Luke

Transition to the On-Chain Collective: Next Steps for the Ambassador Fellowship

Official statement of the Advisory Board of the Polkadot Ambassador Fellowship

If you’re looking for a resource, FAQ or guide, then this is the place to be. We urge all users of the forum to try and use this category when needed.

Resources & FAQs

How to P&lt;&gt;K bridge USDT or USDC

Alain Brenzikofer

How to P<>K bridge USDT or USDC

Asset Hub Migration - XCM FAQ

Remy Le Berre

Asset Hub Migration - Balances FAQ

Yeah I fully agree, this stuff should not happen, even if it is part of a big PR that is hard to review (which was the case here). SRLabs integrated semgrep after this incident for such kind of testing. I think even a custom clippy rule can do it.

Thank you, I understand the need, hopefully with POP reputation will play a role in my feedback here.

Gabriel

<aside class="quote no-group" data-username="burdges" data-post="2" data-topic="15817">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/burdges/48/172_2.png" class="avatar"> burdges:</div>
<blockquote>
As collator sets are small, you’ll still have multi-block sandwiching sometimes, although maybe cryptographic shuffles help ala Whisk. Anyways, you’ll always have single-block sandwiching for smart contracts, but this merely says you should never have smart contracts on DeFi chains or visa versa.
</blockquote>
</aside>
That’s right, e.g. on Hydration single block sandwiches are not possible by design. But the very design prevents potentially useful/interesting features like flash loans. IMO flash loans are a mind blowing advantage over TradFi… probably it can be implemented in a safe way.

Is it just me, or is this bounty basically a tribute to the late Giottodf?
Everybody sing <img src="https://emoji.discourse-cdn.com/twitter/clap.png?v=15" title=":clap:" class="emoji" alt=":clap:" loading="lazy" width="20" height="20">
<blockquote>
We pay our friends more, yeah that’s on me 
We boost our own cuts, pure “market” fee 
We burn all the cash on nonsense you see 
And still tank the results, on a rampage of glee
</blockquote>

hey, this is a known issue and the <a href="https://github.com/polkadot-fellows/runtimes/pull/998">fix</a> will soon be deployed on Polkadot

<a class="mention" href="/u/mcornholio">@mcornholio</a>
Yes, indeed. But when you’re building it, you’re faced with the question… what is an arbitrarily large number? So sometimes it’s easier to just make the runtime call to get the value and pass it along.
But in a more user-facing application, I think you should also use this to either let the user know how much will it need to deposit before you actually send the transaction. Or you could also allow the user to set a maximum limit as part of their settings or something and then use that throughout the interactions.
By the way, I’m taking this chance to update something about the original post - We added solidity contracts support in PAPI and in the ink-sdk shortly after, and it works great <img src="https://emoji.discourse-cdn.com/twitter/rocket.png?v=15" title=":rocket:" class="emoji" alt=":rocket:" loading="lazy" width="20" height="20">

Yuri Volkov

<h2><a name="p-35002-polkadot-news-1" class="anchor" href="#p-35002-polkadot-news-1"></a>Polkadot News</h2>
Polkadot People Initiative: Incentives for Mass Polkadot Activation Campaign is now up for voting <a href="https://polkadot.subsquare.io/referenda/1783" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1783</a>
A fix has been implemented to correct the staking rewards on Polkadot, which will be included in the next runtime upgrade <a href="https://github.com/polkadot-fellows/runtimes/pull/998" class="inline-onebox" rel="noopener nofollow ugc">Fix AH Inflation back to what RC was by kianenigma · Pull Request #998 · polkadot-fellows/runtimes · GitHub</a>
The referendum to upgrade Polkadot Asset Hub and Relay to v2.0.1, which includes post-migration and security fixes, has executed successfully <a href="https://polkadot.subsquare.io/referenda/1782" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1782</a>
Referendum requesting infrastructure funding for Polkadot Asset Hub - maintenance &amp; continuation of the public good, Polkadot NFT marketplace is in the confirmation period <a href="https://polkadot.subsquare.io/referenda/1768" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1768</a>
Check out Road to Sub0 Polkadot Builder Party meetups in Canada, Ecuador, and Peru this weekend <a href="https://luma.com/user/Polkadot" class="inline-onebox" rel="noopener nofollow ugc">Polkadot · Luma</a>
<h2><a name="p-35002-kusama-news-2" class="anchor" href="#p-35002-kusama-news-2"></a>Kusama News</h2>
The referendum to refund early OpenGov submission deposits is in the decision period and is passing <a href="https://kusama.subsquare.io/referenda/609" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/609</a>.

Too early to celebrate - I have 2 issues now.
<ol>
<li>Free balance on the relay has turned into 0 (even if Subscan shows available balance, the wallets don’t). This is critical and going to Parity with it. 
2. Metadata updates are required several times per day. This is just annoying.</li>
</ol>

<h2><a name="p-34997-the-situation-1" class="anchor" href="#p-34997-the-situation-1"></a>the situation</h2>
we have multiple massive catalysts that haven’t broken through the noise:
<ul>
<li>
Polkadot 2.0 is fully live with all three pillars (Async Backing, Agile Coretime, Elastic Scaling)
</li>
<li>
tokenomics overhaul with supply cap and inflation halving every 2 years starting Pi Day 2026
</li>
<li>
Asset Hub just migrated 1.6B DOT with zero failures—one of the most ambitious blockchain upgrades ever executed
</li>
<li>
smart contracts launching on Asset Hub in december, making it Polkadot’s EVM-compatible hub
</li>
</ul>
these are legitimately huge. but they’re getting drowned out because crypto moves fast and attention is scattered. we need a single moment that brings everything together into one sharp narrative that the community rallies around and the wider crypto world can’t ignore.
<h2><a name="p-34997-what-worked-before-2" class="anchor" href="#p-34997-what-worked-before-2"></a>what worked before</h2>
the spammening in 2024 was our most successful community event. period.
what made it work:
<ul>
<li>
community galvanization – everyone united around a single touchpoint. Gavin got involved. the community showed up. social media engagement went through the roof. the event lives on forever on-chain.
</li>
<li>
technical flex with substance – we hit 143,343 TPS on Kusama (23% capacity) in a live mainnet stress test. real economic value. real validators. real conditions. not some fake testnet benchmark.
</li>
<li>
it crossed ecosystems – people outside Polkadot paid attention because it was audacious and backed by actual data. we still reference the spammening constantly when showing what Polkadot can do.
</li>
<li>
fun factor – it wasn’t just technical. 1,933 people manually spammed the network through an interface. it was participatory, chaotic, and entertaining.
</li>
</ul>
the spammening was the last time Polkadot truly broke through the noise. when something works, you do it again.
<h2><a name="p-34997-the-proposal-3" class="anchor" href="#p-34997-the-proposal-3"></a>the proposal</h2>
make Asset Hub’s smart contract launch the main event by hosting spammening v2.
here’s why this works:
v2 has natural upgrades over v1:
<ul>
<li>
first spammening was Kusama. this is Polkadot—bigger, more validators, beefier hardware, higher stakes.
</li>
<li>
Asset Hub is brand new infrastructure fresh off a historic migration. this becomes its baptism by fire.
</li>
<li>
smart contracts make it Polkadot’s EVM-compatible hub. launching with a massive public stress test proves it works at scale from day one.
</li>
<li>
we can integrate games/apps as spam vehicles. FlappyWUD edition? something else? the key is making participation more engaging than just clicking “spam.”
</li>
</ul>
the narrative writes itself:
Asset Hub just got EVM compatibility. now the community gets to prove what it can actually do. can we beat Kusama’s 143K TPS on Polkadot’s infrastructure? can Asset Hub handle real Web2-scale traffic with smart contracts live? let’s find out publicly—and set records while we’re at it.
that’s a story. that’s a moment. that’s something people rally around and talk about.
<h2><a name="p-34997-the-strategy-4" class="anchor" href="#p-34997-the-strategy-4"></a>the strategy</h2>
this isn’t just about TPS numbers. it’s about:
<ol>
<li>
culture formation – the spammening becomes Polkadot’s signature move. the thing we do when major upgrades ship. a tradition that builds identity and brings the community together repeatedly.
</li>
<li>
killing multiple birds – one event that:
<ul>
<li>
proves Asset Hub can handle serious load with smart contracts live
</li>
<li>
generates data for post-event PR and marketing (just like we still reference v1)
</li>
<li>
creates a community moment that galvanizes participation
</li>
<li>
gives developers confidence in the infrastructure as they start building
</li>
<li>
positions Polkadot as the network that stress-tests in public, not in labs
</li>
</ul>
</li>
<li>
breaking through noise – scattered announcements get lost. a single high-energy community festival with measurable outcomes cuts through. when the community is genuinely excited and participating, that energy spreads.
</li>
<li>
Gavin interview leverage – perfect timing for Gavin to do interview rounds where he can speak to both the spammening results (the technical achievement, what the numbers mean) AND the tokenomics overhaul (economic sustainability story). both together paint the “Polkadot 2.0 delivered” narrative with substance.
</li>
<li>
making it repeatable – if this works, spammening becomes a periodic tradition tied to major milestones. JAM launch? spammening v3. next major upgrade? another one. it becomes part of Polkadot’s identity.
</li>
</ol>
<h2><a name="p-34997-what-this-requires-5" class="anchor" href="#p-34997-what-this-requires-5"></a>what this requires</h2>
execution details i’m leaving to the teams (Parity, Technical Fellowship, ecosystem participants), but the core components:
<ul>
<li>
games/apps as spam vehicles at minimum, one highly polished game/app that makes participation fun. FlappyWUD is the obvious candidate since it already exists and has community recognition. could expand to multiple apps/games if capacity allows. the goal: make spamming engaging, not just functional.
</li>
<li>
incentives the first spammening proved participation matters. incentives drive participation. ballpark: 50K-100K DOT reward pool for most active wallets/participants during the event. this isn’t optional if we want mass engagement.
</li>
<li>
timing coordinate with smart contract launch (december 2025 target). the event can happen at launch or immediately after—key is riding the launch momentum, not pre-launch anticipation.
</li>
<li>
infrastructure live dashboard (like v1 had at <a href="http://migration.paritytech.io" rel="noopener nofollow ugc">migration.paritytech.io</a>). real-time TPS tracking. public monitoring so everyone can watch records get set or broken.
</li>
<li>
PR/marketing coordination pre-event hype, live coverage during, post-event data analysis and amplification. this is where the “breaking through noise” happens—before, during, and after. Gavin interview scheduling around this window to maximize impact.
</li>
</ul>
<h2><a name="p-34997-what-success-looks-like-6" class="anchor" href="#p-34997-what-success-looks-like-6"></a>what success looks like</h2>
clear metrics matter:
<ul>
<li>
participation: more wallets active than v1’s 1,933 participants
</li>
<li>
performance: match or exceed Kusama’s 143K TPS—on Polkadot infrastructure with more capacity
</li>
<li>
social reach: trending on crypto twitter during the event, coverage from major crypto media
</li>
<li>
new user acquisition: measurable spike in new wallet activations
</li>
<li>
narrative win: “Asset Hub launched with massive community stress test proving Web2-scale performance” becomes a talking point we (and others) use for months. but beyond that, this also announces to the world that Polkadot now has smart contracts and is performant as hell
</li>
</ul>
<h2><a name="p-34997-the-ask-7" class="anchor" href="#p-34997-the-ask-7"></a>the ask</h2>
this proposal is presenting the idea and strategic case. we need:
<ul>
<li>
Parity/Technical Fellowship to coordinate technical execution
</li>
<li>
treasury funding for incentives and coordination costs
</li>
<li>
ecosystem teams to build/adapt games/apps for participation
</li>
<li>
community management to drive hype and participation
</li>
</ul>
the spammening worked once because it was bold, fun, technically impressive, and brought everyone together. all those conditions still apply. Asset Hub’s launch is the perfect moment to do it again—and make it even bigger.
this is a starting point, not a final plan. if you see ways to improve this—better timing, different games, additional components, smarter execution—build on it. the goal is to create something the whole community can rally around. let’s make it happen together.

gbaci

Proposal: spammening v2 – make Polkadot great again

We’re thrilled to announce that Snowbridge V2 has officially launched!
This release marks a major milestone in the evolution of Snowbridge (the trustless Ethereum ↔ Polkadot bridge) enabling new interoperability capabilities, drastically lower fees and expanded developer possibilities.
The upgrade was enacted through two on-chain referenda:
<ul>
<li><a href="https://polkadot.polkassembly.io/referenda/1763" rel="noopener nofollow ugc">Ref #1763 – Upgrade Snowbridge Gateway Contract</a></li>
<li><a href="https://polkadot.polkassembly.io/referenda/1756" rel="noopener nofollow ugc">Ref #1756 – Runtime Upgrade for Snowbridge V2</a></li>
</ul>
<h2><a name="p-34994-new-bridge-features-improvements-1" class="anchor" href="#p-34994-new-bridge-features-improvements-1"></a>New Bridge Features &amp; Improvements</h2>
<h3><a name="p-34994-new-possibilities-2" class="anchor" href="#p-34994-new-possibilities-2"></a>New Possibilities</h3>
Snowbridge V2 introduces arbitrary contract support on both sides of the bridge. 
This means:
<ul>
<li>XCM Messages from Ethereum to Polkadot: dApps can now send XCM messages from Ethereum to Polkadot AssetHub, and onward to any parachain.</li>
<li>Execute Ethereum contracts from Polkadot: Users and parachains can initiate Ethereum contract calls directly from Polkadot, opening the door to cross-chain applications to reach Ethereum Layer 2 networks.</li>
</ul>
During our <a href="https://www.youtube.com/@polkadotbuilders" rel="noopener nofollow ugc">Polkadot Builder Party </a> presentation, we demonstrated this new capability by executing Optimism contract execution across the Paseo → Sepolia → Optimism Sepolia network path. 
The demo PR showcasing this feature is available here: <a href="https://github.com/Snowfork/snowbridge/pull/1609" rel="noopener nofollow ugc">Snowbridge PR #1609</a>.
Our team is now focused on productizing this capability and expanding support for Ethereum L2 ecosystems.
<h3><a name="p-34994-cheaper-bridging-3" class="anchor" href="#p-34994-cheaper-bridging-3"></a>Cheaper Bridging</h3>
Snowbridge V2 delivers significant fee reductions in both directions of the bridge. 
While fees vary based on Ethereum gas prices, here’s a snapshot comparison:
<div class="md-table">
<table>
<thead>
<tr>
<th>Direction</th>
<th>Snowbridge V1</th>
<th>Snowbridge V2</th>
</tr>
</thead>
<tbody>
<tr>
<td>Ethereum → Polkadot</td>
<td>~$1.00</td>
<td>~$0.50</td>
</tr>
<tr>
<td>Polkadot → Ethereum</td>
<td>~$4.00</td>
<td>~$1.00</td>
</tr>
</tbody>
</table>
</div>These cost savings make Snowbridge one of the most affordable trustless bridges available - now competitive even with multisig-based solutions.
<blockquote>
<img src="https://emoji.discourse-cdn.com/twitter/warning.png?v=15" title=":warning:" class="emoji" alt=":warning:" loading="lazy" width="20" height="20"> Note: The full potential of Snowbridge V2 cheaper transactions will only be realized once parachains integrate with it.
</blockquote>
<h4><a name="p-34994-why-fees-are-lower-in-v2-4" class="anchor" href="#p-34994-why-fees-are-lower-in-v2-4"></a>Why Fees Are Lower in V2</h4>
The reduction in fees is the result of both architectural and design improvements:
<ol>
<li>Off-chain Fee Estimation: 
Snowbridge V2 moves fee estimation off-chain, allowing relayers to estimate fees with much higher accuracy. In contrast, Snowbridge V1 relies on an on-chain ETH/DOT exchange rate, which was rigid and unable to reflect real-time market fluctuations. When Polkadot fee estimation improved after Snowbridge V1 was released, we were able to improve fee handling in V2.</li>
<li>Unordered Message Execution: 
Snowbridge V1 used ordered message execution, meaning that if one message failed due to insufficient fees, all subsequent messages were blocked until it was resolved. 
V2 introduces unordered message processing, allowing low-fee or failing messages to be skipped - keeping the queue flowing efficiently and reducing congestion-related costs.</li>
</ol>
These improvements were enabled and built on new features on Polkadot that were introduced in the last year - fee estimation APIs and dry-running transactions before sending it, ensuring any problems are caught before the user even sends the message.
<h3><a name="p-34994-faster-polkadot-ethereum-transfers-5" class="anchor" href="#p-34994-faster-polkadot-ethereum-transfers-5"></a>Faster Polkadot → Ethereum Transfers</h3>
Beyond Snowbridge V2, we’ve also rolled out a major off-chain performance improvement that cuts delivery time for Polkadot → Ethereum transfers from roughly 1 hour down to 35 minutes. This optimization, called <a href="https://github.com/Snowfork/snowbridge/pull/1598" rel="noopener nofollow ugc">Beefy Pipelining</a>, allows multiple proofs to be processed in parallel, greatly reducing confirmation latency without any on-chain changes.
In addition, we’re developing a premium “fast-lane” feature that further accelerates transfers to just 1–2 minutes. You can follow progress on this feature here: <a href="https://github.com/Snowfork/snowbridge/pull/1462" rel="noopener nofollow ugc">PR #1462</a>. It will be offered as an optional usage, with higher fees ($10-$20) - ideal for users transferring large amounts who value speed and near-immediate finality.
<h2><a name="p-34994-v2-integration-6" class="anchor" href="#p-34994-v2-integration-6"></a>V2 Integration</h2>
<h3><a name="p-34994-parachain-requirements-7" class="anchor" href="#p-34994-parachain-requirements-7"></a>Parachain Requirements</h3>
To integrate with Snowbridge V2, parachains must support XCM V5. 
A detailed compatibility checklist is available in our <a href="https://docs.snowbridge.network/developer-docs/snowbridge-v2/parachain-integration#general-parachain-requirements" rel="noopener nofollow ugc">documentation</a>.
Parachains play a key role in unlocking Snowbridge V2’s full power. Features like contract calls, composable XCM messages, and low-cost bridging become available when a parachain’s runtime upgrades to support V2. Therefore, supporting parachains to upgrade to V2 is a key focus area for our team, and we encourage teams to reach out to us regarding this.
<h3><a name="p-34994-documentation-integration-8" class="anchor" href="#p-34994-documentation-integration-8"></a>Documentation &amp; Integration</h3>
Comprehensive developer documentation is available at: 
<a href="https://docs.snowbridge.network/developer-docs/snowbridge-v2" rel="noopener nofollow ugc">https://docs.snowbridge.network/developer-docs/snowbridge-v2 </a>
Snowbridge V2 is now live on:
<ul>
<li>Mainnets: Polkadot ↔ Ethereum</li>
<li>Testnets: Westend ↔ Sepolia and Paseo ↔S epolia</li>
</ul>
<h3><a name="p-34994-builder-support-9" class="anchor" href="#p-34994-builder-support-9"></a>Builder Support</h3>
We actively support builders and parachains integrating with Snowbridge. 
Join our Telegram group Snowbridge Builder Help to connect with our technical team for guidance and troubleshooting.
<hr>
Snowbridge V2 represents a new era of trustless interoperability. We can’t wait to see what you build.

Clara van Staden

:rocket: Snowbridge V2 Is Live!

🚀 Snowbridge V2 Is Live!

<aside class="quote" data-post="1" data-topic="15835">
 <div class="title">
 <div class="quote-controls"></div>
 <img alt="" width="24" height="24" src="https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/bobby-axelrod/48/5919_2.png" class="avatar">
 <div class="quote-title__text-content">
 <a href="https://forum.polkadot.network/t/topic/15835">Диверсификация риска экосистемы и децентрализация её валидаторов!</a> <a class="badge-category__wrapper " href="/c/ecosystem/24"><span data-category-id="24" style="--category-badge-color: #F1592A; --category-badge-text-color: #FFFFFF;" data-drop-close="true" class="badge-category --style-square " title="If you’re looking for discussion or discourse for anything and all things Ecosystem, then this is the place for you. .">Ecosystem</a>
 </div>
 </div>
 <blockquote>
 Из-за последних событий 10\10, предлагаю создать референдум о запрете владения и создания валидаторов в Polkadot экосистеме владельцами и их аффилированным лицами имеющими более 5% DOT от общего их количества. Для децентрализации, снижения рисков и устойчивости экосистемы. Предлагаю всем это обсудить.
 </blockquote>
</aside>

Не согласен, так как в текущих реалиях это приводит к огромным рискам и нарушению децентрализации <a href="https://forum.polkadot.network/t/topic/15835" class="inline-onebox">Диверсификация риска экосистемы и децентрализация её валидаторов!</a>

Proof of stake is what will kill Polkadot

I’m not aware of what happened specifically the 10th of October, but this seems to go in the right direction towards a resilient economic security for Polkadot.
I wouldn’t call it “diversification” but “distribution”. It could be considered diversification from the point of view of the protocol network, but it is distribution from the point of view of tokenomics.

Diego

Fundamental risks of the ecosystem, distribution, and decentralization of validators!

<h3><a name="p-34978-dotglobal-ecosystem-talent-collaboration-network-1" class="anchor" href="#p-34978-dotglobal-ecosystem-talent-collaboration-network-1"></a>DOTGlobal: Ecosystem Talent &amp; Collaboration Network</h3>
Tagline
No One is left behind.
<hr>
<h2><a name="p-34978-h-1-problem-statement-2" class="anchor" href="#p-34978-h-1-problem-statement-2"></a>1. Problem Statement</h2>
While Polkadot has world-class initiatives like Developer Heroes, PBA-X, and Contentful’s Developer Heroes network, these programs primarily focus on recognition and skill development.
However, the next step after training or recognition remains a major gap:
<ul>
<li>
Many developers and creatives have no structured pathway to apply their skills in active Polkadot projects.
</li>
<li>
Founders and teams struggle to find collaborators or co-founders within the ecosystem.
</li>
<li>
Regional communities (especially in Africa and the Global South) remain dormant, with limited visibility or engagement opportunities after bootcamps.
</li>
</ul>
The result: 
<img src="https://emoji.discourse-cdn.com/twitter/small_orange_diamond.png?v=15" title=":small_orange_diamond:" class="emoji" alt=":small_orange_diamond:" loading="lazy" width="20" height="20"> Graduates from PBA-X lose momentum. 
<img src="https://emoji.discourse-cdn.com/twitter/small_orange_diamond.png?v=15" title=":small_orange_diamond:" class="emoji" alt=":small_orange_diamond:" loading="lazy" width="20" height="20"> Creators and designers drift into other ecosystems. 
<img src="https://emoji.discourse-cdn.com/twitter/small_orange_diamond.png?v=15" title=":small_orange_diamond:" class="emoji" alt=":small_orange_diamond:" loading="lazy" width="20" height="20"> Projects struggle to find verified, active contributors.
<hr>
<h2><a name="p-34978-h-2-solution-what-dotglobal-does-3" class="anchor" href="#p-34978-h-2-solution-what-dotglobal-does-3"></a>2. Solution — What DOTGlobal Does</h2>
DOTGlobal is an open, ecosystem-aligned network designed to connect builders, creatives, founders, and communities into one collaboration layer that sits on top of existing Polkadot initiatives — not beside them.
Think of it as a participation graph for the Polkadot ecosystem, where every contributor’s activity, reputation, and collaboration can be tracked, visualized, and connected to ongoing projects and bounties.
<h3><a name="p-34978-core-functions-4" class="anchor" href="#p-34978-core-functions-4"></a>Core Functions</h3>
<ol>
<li>
Ecosystem Talent Graph
<ul>
<li>
On-chain contributor identity and profile verification (via Substrate).
</li>
<li>
Activity-based scoring that reflects actual engagement and project impact.
</li>
</ul>
</li>
<li>
Collaboration Hub
<ul>
<li>
A space where projects can list open bounties, short-term gigs, or collaboration calls.
</li>
<li>
Founders and teams can find builders, designers, writers, and other contributors within the ecosystem.
</li>
</ul>
</li>
<li>
Reputation &amp; Recognition Layer
<ul>
<li>
Public contributor metrics integrated with the Polkadot ecosystem.
</li>
<li>
Allows the Web3 Foundation and ecosystem teams to identify committed, proven builders across geographies.
</li>
</ul>
</li>
<li>
Community Activation Tooling
<ul>
<li>Local communities (starting in Nigeria: Kaduna &amp; Abuja) can run talent programs, track participation, and onboard contributors directly into the global DOTGlobal system.</li>
</ul>
</li>
</ol>
<hr>
<h2><a name="p-34978-h-3-why-dotglobal-is-different-5" class="anchor" href="#p-34978-h-3-why-dotglobal-is-different-5"></a>3. Why DOTGlobal Is Different</h2>
DOTGlobal is not a centralized hiring platform. 
It’s a decentralized ecosystem network — built with the same principles that power Polkadot itself: openness, interoperability, and transparency.
Here’s how DOTGlobal differs from other initiatives:
<div class="md-table">
<table>
<thead>
<tr>
<th>Initiative</th>
<th>Focus</th>
<th>DOTGlobal’s Complementary Role</th>
</tr>
</thead>
<tbody>
<tr>
<td>Developer Heroes / Contentful</td>
<td>Recognition &amp; storytelling for developers</td>
<td>DOTGlobal connects those recognized talents with real ecosystem projects and bounties.</td>
</tr>
<tr>
<td>Gitcoin-style platforms</td>
<td>Open funding across multiple ecosystems</td>
<td>DOTGlobal keeps contributions Polkadot-native — tracking and rewarding ecosystem-specific work.</td>
</tr>
<tr>
<td>Polimec</td>
<td>Project fundraising &amp; incubation</td>
<td>DOTGlobal feeds verified contributors and teams into the Polimec pipeline.</td>
</tr>
<tr>
<td>Regional Bootcamps (e.g. PBA-X)</td>
<td>Education and training</td>
<td>DOTGlobal provides the “next step” — practice, collaboration, and contribution.</td>
</tr>
</tbody>
</table>
</div>DOTGlobal doesn’t duplicate — it integrates. 
It acts as the ecosystem’s connective tissue, helping W3F and parachains clearly see who is building what, and where.
<hr>
<h2><a name="p-34978-h-4-why-this-matters-6" class="anchor" href="#p-34978-h-4-why-this-matters-6"></a>4. Why This Matters</h2>
<ul>
<li>
It ensures the foundation can identify its most active, credible contributors, globally and locally.
</li>
<li>
It converts passive alumni and enthusiasts into active builders.
</li>
<li>
It strengthens ecosystem retention, ensuring that talent trained under Polkadot initiatives remains within the network instead of migrating elsewhere.
</li>
</ul>
In short, DOTGlobal turns recognition into contribution.
<hr>
<h2><a name="p-34978-h-5-technical-implementation-7" class="anchor" href="#p-34978-h-5-technical-implementation-7"></a>5. Technical Implementation</h2>
Stack Overview:
<ul>
<li>
Frontend: React (Next.js) + TailwindCSS
</li>
<li>
Backend: Rust / Node.js API
</li>
<li>
Blockchain Layer: Substrate module for contributor identity and activity proofs
</li>
<li>
Database: PostgreSQL + IPFS for storing off-chain metadata
</li>
<li>
Wallet Integration: Polkadot.js for login and activity signatures
</li>
<li>
Deployment: Docker containers and GitHub Actions for CI/CD
</li>
</ul>
Core Modules:
<ol>
<li>
Identity &amp; Verification Pallet (on-chain)
</li>
<li>
Contribution Registry
</li>
<li>
Reward and Scoring System
</li>
<li>
Open Collaboration Feed
</li>
<li>
Analytics Dashboard for Ecosystem Insights
</li>
</ol>
Open-Source License: MIT
<hr>
<h3><a name="p-34978-roadmap-8" class="anchor" href="#p-34978-roadmap-8"></a>Roadmap</h3>
<h4><a name="p-34978-phase-1-foundation-03-months-9" class="anchor" href="#p-34978-phase-1-foundation-03-months-9"></a>Phase 1 – Foundation (0–3 months)</h4>
Laying the groundwork for DOTGlobal’s infrastructure and first local activations. 
Objectives:
<ul>
<li>
Design System &amp; Data Architecture: Create the contributor data model and visual design system.
</li>
<li>
MVP Development: Build the initial contributor registry and project listing system.
</li>
<li>
Substrate Integration: Deploy an identity-tracking Substrate module to authenticate contributor activities.
</li>
<li>
Onboarding Pilot: Launch first physical onboarding and awareness events across Kaduna, Kano, Katsina, Abuja, and other parts of Northern Nigeria, onboarding developers, creators, and early community members into the Polkadot ecosystem.
</li>
</ul>
<hr>
<h4><a name="p-34978-phase-2-expansion-36-months-10" class="anchor" href="#p-34978-phase-2-expansion-36-months-10"></a>Phase 2 – Expansion (3–6 months)</h4>
Scaling DOTGlobal into a nationwide movement and deepening engagement mechanisms. 
Objectives:
<ul>
<li>
Reward &amp; Reputation System: Implement contributor reputation, on-chain verification, and bounty tracking.
</li>
<li>
Regional Expansion: Begin physical onboarding programs in Eastern, Western, and Southern Nigeria, each region led by a local ambassador responsible for growth, outreach, and community support.
</li>
<li>
Bootcamps &amp; Training: Launch in-person Polkadot bootcamps and community hack sessions in major cities, focusing on hands-on learning and contribution readiness.
</li>
<li>
Community Growth: Strengthen social and online presence to connect remote contributors across Africa.
</li>
</ul>
<hr>
<h4><a name="p-34978-phase-3-acceleration-612-months-11" class="anchor" href="#p-34978-phase-3-acceleration-612-months-11"></a>Phase 3 – Acceleration (6–12 months)</h4>
Evolving DOTGlobal from onboarding to ecosystem empowerment — creating a sustainable contributor economy. 
Objectives:
<ul>
<li>
Founder Incubation Program: Launch incubation training for early-stage founders building within the Polkadot ecosystem.
</li>
<li>
DOTGlobal Submissions: Establish a structured process for project submissions, mentorship, and resource matching.
</li>
<li>
Hackathons &amp; Bounties: Organize thematic hackathons and community bounty challenges to foster collaboration and innovation.
</li>
<li>
Weekly Community Calls: Host open community calls to discuss progress, opportunities, and success stories — reinforcing a sense of belonging and shared mission.
</li>
<li>
Ecosystem Analytics Dashboard: Introduce transparent dashboards to track contributions, rewards, and regional impact metrics.
</li>
</ul>
<h2><a name="p-34978-h-7-budget-phase-1-and-2-12" class="anchor" href="#p-34978-h-7-budget-phase-1-and-2-12"></a>7. Budget (Phase 1 and 2)</h2>
<div class="md-table">
<table>
<thead>
<tr>
<th>Category</th>
<th>Description</th>
<th>Cost (USD)</th>
</tr>
</thead>
<tbody>
<tr>
<td>Personnel</td>
<td>Full-stack + Substrate developer (0.5 FTE, 3 months)</td>
<td>$4,000</td>
</tr>
<tr>
<td>Design &amp; UX</td>
<td>Branding, UI/UX, contributor dashboard</td>
<td>$2,000</td>
</tr>
<tr>
<td>Bootcamps</td>
<td>Physical events (Kaduna, Abuja, Kano, Katsina)</td>
<td>$5,000</td>
</tr>
<tr>
<td>Community Growth</td>
<td>Ambassador setup, outreach, online platform tools</td>
<td>$3,000</td>
</tr>
<tr>
<td>Equipment &amp; Hosting</td>
<td>Server setup, testing, Docker/IPFS infrastructure</td>
<td>$1,000</td>
</tr>
<tr>
<td>Total (Phase 1)</td>
<td></td>
<td>$15,000 USD (equivalent in DOT)</td>
</tr>
</tbody>
</table>
</div><h2><a name="p-34978-h-8-ecosystem-fit-13" class="anchor" href="#p-34978-h-8-ecosystem-fit-13"></a>8. Ecosystem Fit</h2>
DOTGlobal provides measurable value to Polkadot’s talent infrastructure:
<ul>
<li>
Makes contributions visible and quantifiable.
</li>
<li>
Helps parachains discover talent inside the ecosystem.
</li>
<li>
Encourages collaboration over competition among regional communities.
</li>
<li>
Builds Polkadot’s human capital database transparently on-chain.
</li>
</ul>
This is not just a platform — it’s the ecosystem lens for understanding who is active, reliable, and contributing.
<hr>
<h2><a name="p-34978-h-9-future-vision-14" class="anchor" href="#p-34978-h-9-future-vision-14"></a>9. Future Vision</h2>
Our vision is to:
<ul>
<li>
Build a network of verified contributors who collaborate, earn, and grow within Polkadot.
</li>
<li>
Create local-to-global pipelines connecting regional builders to global projects.
</li>
<li>
Be the ecosystem’s heartbeat — where ideas become teams, teams become projects, and projects strengthen Polkadot’s network effect.
</li>
</ul>
Through continuous onboarding, open collaboration, and transparent contribution tracking, DOTGlobal will ensure no one is left behind in Polkadot’s mission to build a decentralized future.
<hr>
<h2><a name="p-34978-h-10-closing-statement-15" class="anchor" href="#p-34978-h-10-closing-statement-15"></a>10. Closing Statement</h2>
<blockquote>
DOTGlobal’s mission is simple: to make sure no one is left behind in the Polkadot ecosystem — whether you’re a developer, founder, designer, or creative.
</blockquote>
By turning skills and passion into measurable contributions, DOTGlobal will help the Web3 Foundation identify its true builders, empower new regions, and create a living, evolving network of collaboration that keeps Polkadot growing — from the inside out.

Stephanie Nwankwo

DOTGlobal: Ecosystem Talent &amp; Collaboration Network

DOTGlobal: Ecosystem Talent & Collaboration Network

Thanks for the calculation <a class="mention" href="/u/paulormart">@paulormart</a>! If the validator community is inclined to do so, will support a proposal to refund them. Although, the values might be small enough that validators might be okay to write it off as a one-off incident, as over the course of an annual payout, it will be a tiny fraction.

paulo // turboflakes.io

PSA: Disruption To Kusama Validators&rsquo; Self-Stake and Rewards

PSA: Disruption To Kusama Validators' Self-Stake and Rewards

Runtime release notification
Hello,
This is to advise you that the Polkadot community is currently voting to upgrade the <a href="https://polkadot.subsquare.io/referenda/1782" rel="noopener nofollow ugc">Polkadot system</a> to the <a href="https://github.com/polkadot-fellows/runtimes/releases/tag/v2.0.1" rel="noopener nofollow ugc">v2.0.1 release</a>.
<img src="https://emoji.discourse-cdn.com/twitter/construction.png?v=15" title=":construction:" class="emoji" alt=":construction:" loading="lazy" width="20" height="20"> Important note for Polkadot Relay validators and Asset Hub collators: <img src="https://emoji.discourse-cdn.com/twitter/construction.png?v=15" title=":construction:" class="emoji" alt=":construction:" loading="lazy" width="20" height="20"> 
As the Polkadot Asset Hub Migration is complete, you can now remove the <code>db-cache 8000</code> CLI flag.
Many thanks.

Yeah, Kusama could definitely be a direction to consider. I like the cyberpunk vibe it has. The proposal you’re linking to is very interesting for funding a social layer / adoption focused direction for Kusama. I´d really like web3 to be part of the everyday users experience.
Either way, i’m looking for some form of validation that the idea’s in the document are worth pursuing. Anyone here who can chime in with feedback is greatly appreciated.
In terms of prior web3 development, we did build a p2p matching algorithm in one of our first proof of concepts, called Atomic Loops. The platform solved the “Coincidence-of-wants-problem¨ and effectively offers an alternative to money. This was the goal back then, because I firmly believed that money is the source of a lot of problems in the world. We tested it in practice and learned a lot from that experiment. Even won a blockchain hackathon; <a href="https://www.youtube.com/watch?v=UUkp11iFAFk" rel="noopener nofollow ugc">https://www.youtube.com/watch?v=UUkp11iFAFk</a>
The technical paper in the first post proposes trust infrastructure. It builds upon the premise that everyone of us has people we trust and who may “lean” on us. If you expand that trust circle one hop, you get access to a lot more resources and skills that are currently under-utilized and undervalued. There is a very big social component to all of this, which is appreciation by others for the value you bring to others. This is why the proposed solution isn´t necessary a tech problem, but an societal problem. To change the current paradigm of scarcity and self-interest, we need both the tech and a way to change peoples behavior. 
Which is why we have a anthropologist and a filmmaker in the team.
Anway, if this in any way resonates with the community, please let me know.

Michiel | Socialtec

Eric ~Distractive.xyz

Socially grounded individuality

Thank you for your comments and generous offer, <a class="mention" href="/u/vikk">@Vikk</a>. Your <a href="https://forum.polkadot.network/t/status-update-on-the-development-of-a-notion-based-voting-tool-for-emerging-communities-and-smaller-daos-active-in-opengov/13469/8">OpenGov voting browser extension </a>looks amazing!
I am not so much trying to set up a DAO as to understand why there is a gap in Polkadot DAO tooling and whether there is a need to fill it.
Here is my “zero to DAO” spectrum <img src="https://emoji.discourse-cdn.com/twitter/slight_smile.png?v=15" title=":slight_smile:" class="emoji" alt=":slight_smile:" loading="lazy" width="20" height="20">
Zero 
• group chat, bank account and DAO-in-a-box – it’s the off-chain things that matter the most! 
• group chat and a multisig 
• lightweight, versatile DAO-tooling with at least token-based voting – EVM <img src="https://emoji.discourse-cdn.com/twitter/white_check_mark.png?v=15" title=":white_check_mark:" class="emoji" alt=":white_check_mark:" loading="lazy" width="20" height="20">, Polkadot <img src="https://emoji.discourse-cdn.com/twitter/cross_mark.png?v=15" title=":cross_mark:" class="emoji" alt=":cross_mark:" loading="lazy" width="20" height="20"> (the gap I am interested in) 
• OpenGov – powerful but complicated 
DAO
As someone who recently spent some hours grappling with delegations, proxy and locks, I am not sure I would wish OpenGov on new users!
If mass adoption of DAOs is coming, do we want to leave that to EVM eco tools?

DAO tooling for project teams

We adapted our Kusama timeline slightly and are preparing the release for November, both with the PVM and EVM backend.
Both backends will be available at the hackathon as well.

Torsten

Daan van der Plas

Smart Contracts on Polkadot Hub: Progress Update

<h2><a name="p-34947-polkadot-news-1" class="anchor" href="#p-34947-polkadot-news-1"></a>Polkadot News</h2>
“Where did my DOT go?” - Given the Polkadot Asset Hub migration of accounts and balances, check your DOT balance in your account here <a href="https://assethub-polkadot.subscan.io/" rel="noopener nofollow ugc">https://assethub-polkadot.subscan.io/</a> <a href="https://x.com/subscan_io/status/1986018841252757545" rel="noopener nofollow ugc">https://x.com/subscan_io/status/1986018841252757545</a>
If you are a user facing issues with accessing account balance, staking, governance, or other features, reach out to <a href="https://support.polkadot.network/support/home" class="inline-onebox" rel="noopener nofollow ugc">Polkadot Support</a>
A fix is in progress for staking rewards on the Polkadot Asset Hub. Until this fix is deployed, the staking rewards are expected to be about 60% less than before. <a href="https://github.com/polkadot-fellows/runtimes/pull/998" class="inline-onebox" rel="noopener nofollow ugc">Fix AH Inflation back to what RC was by kianenigma · Pull Request #998 · polkadot-fellows/runtimes · GitHub</a> Reimbursement for the missed rewards is in the works
The referendum to upgrade Polkadot Asset Hub and Relay to v2.0.1, which includes post-migration and security fixes, is passing unanimously <a href="https://polkadot.subsquare.io/referenda/1782" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1782</a>
<h2><a name="p-34947-kusama-news-2" class="anchor" href="#p-34947-kusama-news-2"></a>Kusama News</h2>
The referendum to upgrade Kusama Asset Hub to v2.0.1 has executed successfully <a href="https://kusama.subsquare.io/referenda/611" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/611</a>
The referendum to refund early OpenGov submission deposits is up for voting and is passing <a href="https://kusama.subsquare.io/referenda/609" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/609</a>

Polkadot Digest 06 November 2025

Hey <a class="mention" href="/u/polkadotlatino">@PolkadotLatino</a>
Maybe we can help with this one. Token Terminal is in the final stages of making <a href="https://tokenterminal.com/explorer/studio/dashboards/b098b738-0a30-433f-a63a-bc0d4a4ebac5" rel="noopener nofollow ugc">Polkadot data</a> available publicly in BigQuery (Google Web3 Marketplace) - each onboarded parachain will have its own dataset on the marketplace, covering everything from block-level data to standardized financial and business metrics. We’ll inform the community as soon as that’s available.

PolkadotLatino

That’s a really good addition — I completely agree.
Recovering code and development output from inactive projects could be just as valuable as reclaiming unused funds. There’s no reason for good work to disappear simply because a project went inactive.
The Recovery Group (or whatever we end up calling it) could include a “code and resource preservation” process as part of its responsibilities. For example:
<ul>
<li>
Collecting open-source repositories from inactive or abandoned projects.
</li>
<li>
Hosting them in a central community-maintained archive — maybe under the Polkadot GitHub organization or an independent repo like polkadot-recovery-lab.
</li>
<li>
Tagging and categorizing projects (e.g. treasury-funded, parachain, dApp, tooling) so developers can easily find reusable code.
</li>
<li>
Potentially rewarding contributors who document or repurpose this code for new projects.
</li>
</ul>
This would prevent waste, foster reuse, and give future builders a solid foundation to build from.
The example of <a href="https://bountymanager.io/" rel="noopener nofollow ugc">bountymanager.io</a> is a great case — the funds were lost, but the code might still help future bounty dashboards or analysis tools.
So yes, I think this idea could become a dual recovery effort:
<ul>
<li>
Financial recovery (returning or redistributing funds), and
</li>
<li>
Code recovery (preserving useful work for future builders).
</li>
</ul>
Both contribute to the same goal — keeping the Polkadot ecosystem transparent, efficient, and self-sustaining. <img src="https://emoji.discourse-cdn.com/twitter/raising_hands.png?v=15" title=":raising_hands:" class="emoji" alt=":raising_hands:" loading="lazy" width="20" height="20">

We shall meet in the place where there is no darkness

Establishing a Governance-Backed Recovery Group for Inactive or “Dead” Projects

Hello fellow travelers <img src="https://emoji.discourse-cdn.com/twitter/waving_hand.png?v=15" title=":waving_hand:" class="emoji" alt=":waving_hand:" loading="lazy" width="20" height="20">
With the community’s ongoing discussions around pUSD, a governance- and community-owned tokenized version of USD on Polkadot, I wanted to open up a related conversation about extending this idea to other key assets — namely BTC and ETH.
<hr>
<h3><a name="p-34939-overview-1" class="anchor" href="#p-34939-overview-1"></a><img src="https://emoji.discourse-cdn.com/twitter/compass.png?v=15" title=":compass:" class="emoji" alt=":compass:" loading="lazy" width="20" height="20"> Overview</h3>
Just like pUSD aims to create a stable, Polkadot-native asset that’s transparently governed by the community, having governance-owned and community-managed versions of BTC and ETH (and more) could unlock a wide range of benefits for the ecosystem.
The long-term vision could even evolve into a governance-owned financial corechain, serving as Polkadot’s native liquidity, lending, and staking hub — fully owned and operated by the community.
<hr>
<h3><a name="p-34939-why-governance-owned-tokenized-btc-and-eth-2" class="anchor" href="#p-34939-why-governance-owned-tokenized-btc-and-eth-2"></a><img src="https://emoji.discourse-cdn.com/twitter/light_bulb.png?v=15" title=":light_bulb:" class="emoji" alt=":light_bulb:" loading="lazy" width="20" height="20"> Why Governance-Owned Tokenized BTC and ETH?</h3>
<h4><a name="p-34939-h-1-boosting-defi-tvl-and-adoption-3" class="anchor" href="#p-34939-h-1-boosting-defi-tvl-and-adoption-3"></a>1. Boosting DeFi TVL and Adoption</h4>
<ul>
<li>
BTC and ETH remain the most widely held and recognized crypto assets.
</li>
<li>
Tokenized, native versions of these assets (e.g., pBTC and pETH) could significantly increase on-chain liquidity and attract more users, liquidity providers, and developers to Polkadot’s DeFi ecosystem.
</li>
</ul>
<h4><a name="p-34939-h-2-diversified-treasury-and-payment-flexibility-4" class="anchor" href="#p-34939-h-2-diversified-treasury-and-payment-flexibility-4"></a>2. Diversified Treasury and Payment Flexibility</h4>
<ul>
<li>
Governance proposals, bounties, and grants could be paid out in BTC or ETH, depending on the project or contributor preference.
</li>
<li>
This would diversify treasury holdings and improve Polkadot’s appeal to a broader contributor base.
</li>
</ul>
<h4><a name="p-34939-h-3-treasury-yield-and-passive-income-5" class="anchor" href="#p-34939-h-3-treasury-yield-and-passive-income-5"></a>3. Treasury Yield and Passive Income</h4>
<ul>
<li>
The Treasury could generate passive income by lending, staking, or liquidity pooling these tokenized assets.
</li>
<li>
This creates sustainable revenue streams for ecosystem funding, reducing reliance on DOT emissions or one-off treasury expenditures.
</li>
</ul>
<h4><a name="p-34939-h-4-cross-ecosystem-interoperability-6" class="anchor" href="#p-34939-h-4-cross-ecosystem-interoperability-6"></a>4. Cross-Ecosystem Interoperability</h4>
<ul>
<li>Tokenized BTC and ETH would enhance interoperability between Polkadot and other major ecosystems, positioning Polkadot as the most open and connected multichain network.</li>
</ul>
<h4><a name="p-34939-h-5-governance-owned-financial-infrastructure-7" class="anchor" href="#p-34939-h-5-governance-owned-financial-infrastructure-7"></a>5. Governance-Owned Financial Infrastructure</h4>
<ul>
<li>
With multiple governance-owned tokenized assets (pBTC, pETH, pUSD, and potentially others), Polkadot could evolve toward a governance-owned corechain that acts as:
<ul>
<li>
a liquidity provider,
</li>
<li>
a lending and borrowing protocol,
</li>
<li>
a staking and yield platform, and
</li>
<li>
a cross-chain liquidity hub for the ecosystem.
</li>
</ul>
</li>
<li>
This would create a self-sustaining, community-managed DeFi foundation, fully aligned with Polkadot’s ethos of decentralization and transparency.
</li>
</ul>
<h4><a name="p-34939-h-6-alignment-with-paritys-renewed-focus-8" class="anchor" href="#p-34939-h-6-alignment-with-paritys-renewed-focus-8"></a>6. Alignment With Parity’s Renewed Focus</h4>
<ul>
<li>Given that Parity has signaled it will start developing directly on Polkadot, this initiative could fit naturally into that vision — serving as one of the strategic focuses for ecosystem development in the coming era.</li>
</ul>
<hr>
<h3><a name="p-34939-implementation-pathways-9" class="anchor" href="#p-34939-implementation-pathways-9"></a><img src="https://emoji.discourse-cdn.com/twitter/puzzle_piece.png?v=15" title=":puzzle_piece:" class="emoji" alt=":puzzle_piece:" loading="lazy" width="20" height="20"> Implementation Pathways</h3>
There are multiple potential routes to realize governance-owned tokenized assets on Polkadot:
<ul>
<li>
Bridge-based approach – Using existing or new trust-minimized bridges (e.g., Snowbridge, Hyperbridge) to mint governance-controlled wrapped assets.
</li>
<li>
Synthetic model – Issuing governance-backed synthetic BTC/ETH collateralized by DOT, pUSD, or other on-chain assets.
</li>
<li>
Hybrid model – Combining external bridging for liquidity with synthetic issuance for governance control.
</li>
</ul>
Each model offers different trade-offs between decentralization, liquidity, and technical complexity. The community could begin with a minimal viable implementation, then expand through governance experimentation.
<hr>
<h3><a name="p-34939-governance-structure-10" class="anchor" href="#p-34939-governance-structure-10"></a><img src="https://emoji.discourse-cdn.com/twitter/hammer_and_wrench.png?v=15" title=":hammer_and_wrench:" class="emoji" alt=":hammer_and_wrench:" loading="lazy" width="20" height="20"> Governance Structure</h3>
To ensure transparency and long-term sustainability:
<ul>
<li>
Governance could elect a multisig or fellowship-like committee to oversee liquidity and treasury interactions.
</li>
<li>
Parameters such as minting caps, collateral ratios, and yield strategies could be set through on-chain referenda.
</li>
<li>
A public dashboard could display asset backing, utilization, and performance metrics — ensuring total visibility into the system.
</li>
</ul>
<hr>
<h3><a name="p-34939-treasury-integration-and-sustainability-11" class="anchor" href="#p-34939-treasury-integration-and-sustainability-11"></a><img src="https://emoji.discourse-cdn.com/twitter/money_with_wings.png?v=15" title=":money_with_wings:" class="emoji" alt=":money_with_wings:" loading="lazy" width="20" height="20"> Treasury Integration and Sustainability</h3>
By integrating pBTC and pETH into treasury operations:
<ul>
<li>
Polkadot could deploy staking, lending, or liquidity farming strategies through governance-approved protocols.
</li>
<li>
A percentage of the generated yield could flow back into the Treasury, fund ecosystem development, or bootstrap new DeFi initiatives.
</li>
<li>
Over time, this could evolve into a self-reinforcing economic loop, where governance-owned assets continuously fund Polkadot’s growth.
</li>
</ul>
<hr>
<h3><a name="p-34939-expanding-the-tokenized-asset-suite-12" class="anchor" href="#p-34939-expanding-the-tokenized-asset-suite-12"></a><img src="https://emoji.discourse-cdn.com/twitter/coin.png?v=15" title=":coin:" class="emoji" alt=":coin:" loading="lazy" width="20" height="20"> Expanding the Tokenized Asset Suite</h3>
Beyond BTC, ETH, and USD, governance could explore a broader tokenized asset suite, including:
<ul>
<li>pGOLD (and/or pSILVER) – a tokenized, governance-owned version of gold for stability and diversification.</li>
<li>pSTOCKS – synthetic “stonks,” representing exposure to traditional markets via decentralized oracles.</li>
<li>pBONDs – governance-issued bonds or fixed-yield instruments that could provide stable, predictable returns for the treasury and participants.</li>
</ul>
This would form the basis for a multi-asset DeFi economy fully owned by Polkadot governance.
<hr>
<h3><a name="p-34939-risk-and-security-considerations-13" class="anchor" href="#p-34939-risk-and-security-considerations-13"></a><img src="https://emoji.discourse-cdn.com/twitter/brain.png?v=15" title=":brain:" class="emoji" alt=":brain:" loading="lazy" width="20" height="20"> Risk and Security Considerations</h3>
Issuing and managing governance-owned assets introduces new risks:
<ul>
<li>
Smart contract vulnerabilities
</li>
<li>
Collateral volatility
</li>
<li>
Liquidity imbalances or oracle dependencies
</li>
</ul>
To mitigate these, early implementations should:
<ul>
<li>
Begin with limited supply caps and audited codebases
</li>
<li>
Adopt progressive decentralization in governance oversight
</li>
<li>
Conduct continuous monitoring and community reporting
</li>
</ul>
Acknowledging these risks upfront builds confidence and credibility within the ecosystem.
<hr>
<h3><a name="p-34939-working-group-and-collaboration-14" class="anchor" href="#p-34939-working-group-and-collaboration-14"></a><img src="https://emoji.discourse-cdn.com/twitter/handshake.png?v=15" title=":handshake:" class="emoji" alt=":handshake:" loading="lazy" width="20" height="20"> Working Group and Collaboration</h3>
To move this concept forward, it might make sense to form a working group or research collective — possibly alongside the pUSD initiative — to explore:
<ul>
<li>
Technical architectures and collateral models
</li>
<li>
Governance and treasury integration
</li>
<li>
Risk and audit frameworks
</li>
<li>
Cross-parachain liquidity strategies
</li>
</ul>
Collaboration between Parity, the Fellowship, DeFi parachains, and Treasury representatives could accelerate experimentation and ensure cross-ecosystem alignment from the start.
<hr>
<h3><a name="p-34939-a-vision-for-a-community-owned-financial-future-15" class="anchor" href="#p-34939-a-vision-for-a-community-owned-financial-future-15"></a><img src="https://emoji.discourse-cdn.com/twitter/globe_showing_europe_africa.png?v=15" title=":globe_showing_europe_africa:" class="emoji" alt=":globe_showing_europe_africa:" loading="lazy" width="20" height="20"> A Vision for a Community-Owned Financial Future</h3>
Polkadot has always been about building systems that belong to everyone. 
Governance-owned tokenized assets could be the foundation for the first truly community-owned financial infrastructure — a self-governing, self-funding, and self-sustaining economy that empowers users, developers, and contributors alike.
This isn’t just about DeFi — it’s about creating a governance-owned economy, where the community collectively manages assets, liquidity, and value flows across the entire network.
<hr>
<h3><a name="p-34939-personal-note-open-questions-16" class="anchor" href="#p-34939-personal-note-open-questions-16"></a><img src="https://emoji.discourse-cdn.com/twitter/speech_balloon.png?v=15" title=":speech_balloon:" class="emoji" alt=":speech_balloon:" loading="lazy" width="20" height="20"> Personal Note &amp; Open Questions</h3>
I’m personally not yet deeply familiar with the governance system — so I’m not entirely sure how to move forward if this discussion gains momentum. 
If this thread were received overwhelmingly positively, I’d love to understand how to make a formal “Wish for Change” proposal or any other governance motion that could move this idea toward research and experimentation.
<hr>
<h3><a name="p-34939-next-steps-if-theres-interest-17" class="anchor" href="#p-34939-next-steps-if-theres-interest-17"></a><img src="https://emoji.discourse-cdn.com/twitter/ringed_planet.png?v=15" title=":ringed_planet:" class="emoji" alt=":ringed_planet:" loading="lazy" width="20" height="20"> Next Steps (If There’s Interest)</h3>
<ol>
<li>
Form a small working group aligned with the pUSD team and Treasury members.
</li>
<li>
Draft a technical concept note exploring collateral, yield, and security models.
</li>
<li>
Submit a “Wish for Change” proposal or similar governance motion to request research funding.
</li>
</ol>

Expanding Polkadot’s Tokenized Ecosystem: Governance-Owned BTC and ETH Assets

I was pleased to come across two posts that reinforce the point of this question I shared with the community several weeks ago.
The first was a tweet from <a class="mention" href="/u/bill_w3f">@bill_w3f</a> about his important participation in an event organized by UNDP. <a href="https://x.com/BillLaboon/status/1985599760095379799" rel="noopener nofollow ugc">Reference</a> 
<div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/1/11bdf23f7c3ad2044e7b221020e9051b3a0c1d5d.jpeg" data-download-href="/uploads/short-url/2wX4EpkFuZ9grZGkIJe3V1p2rfL.jpeg?dl=1" title="image" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/1/11bdf23f7c3ad2044e7b221020e9051b3a0c1d5d_2_523x500.jpeg" alt="image" data-base62-sha1="2wX4EpkFuZ9grZGkIJe3V1p2rfL" width="523" height="500" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/1/11bdf23f7c3ad2044e7b221020e9051b3a0c1d5d_2_523x500.jpeg, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/1/11bdf23f7c3ad2044e7b221020e9051b3a0c1d5d.jpeg 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/1/11bdf23f7c3ad2044e7b221020e9051b3a0c1d5d.jpeg 2x" data-dominant-color="4C4839"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg>image677×646 81.6 KB<svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div>
The second was from UNDP’s LinkedIn official account about the event that brought together important participants from the global blockchain ecosystem. <a href="https://www.linkedin.com/posts/undp-altfinlab_sdgblockchainaccelerator-activity-7391526234159128576-6AW2" rel="noopener nofollow ugc">Reference</a>
<div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/e/ec99bd8bfca6bb985918afc12b551be96562526d.png" data-download-href="/uploads/short-url/xL44mqAhoWD1HEijgLJhbGliuSx.png?dl=1" title="image" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/e/ec99bd8bfca6bb985918afc12b551be96562526d_2_519x500.png" alt="image" data-base62-sha1="xL44mqAhoWD1HEijgLJhbGliuSx" width="519" height="500" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/e/ec99bd8bfca6bb985918afc12b551be96562526d_2_519x500.png, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/e/ec99bd8bfca6bb985918afc12b551be96562526d_2_778x750.png 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/e/ec99bd8bfca6bb985918afc12b551be96562526d_2_1038x1000.png 2x" data-dominant-color="EDEDEE"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg>image1339×1288 170 KB<svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div>
<div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/a/adf19785db7bd2d4c020ddaf532dc302acabece4.jpeg" data-download-href="/uploads/short-url/oOMd3BSxAR5jiDe9of0K5nAA8Go.jpeg?dl=1" title="image" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/a/adf19785db7bd2d4c020ddaf532dc302acabece4_2_690x358.jpeg" alt="image" data-base62-sha1="oOMd3BSxAR5jiDe9of0K5nAA8Go" width="690" height="358" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/a/adf19785db7bd2d4c020ddaf532dc302acabece4_2_690x358.jpeg, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/a/adf19785db7bd2d4c020ddaf532dc302acabece4_2_1035x537.jpeg 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/a/adf19785db7bd2d4c020ddaf532dc302acabece4.jpeg 2x" data-dominant-color="63564C"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg>image1165×605 199 KB<svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div>
I again invite the entire community to share their comments and observations on the possibility of establishing an official collaboration channel between Polkadot and UNDP. This effort has already involved several activities and collaborations from Venezuela over the past few months, and as you can see, it aligns with the activities at UNDP’s Copenhagen headquarters.

Simón León

Inquiry about official PUND-Polkadot collaboration

root

whitelisted_caller

wish_for_change

staking_admin

treasurer

lease_admin

fellowship_admin

general_admin

auction_admin

referendum_canceller

referendum_killer

small_tipper

big_tipper

small_spender

medium_spender

big_spender

Unlock Winning Strategies with Playzone

Encointer Outlook for Q4'25 and Onwards

Sol-XCM | A typed interface for interoperability from Solidity

Implement a Kusama Forum MVP (Content Pallet v2)

Discovering the Dynamic Features of JLJL99

Implement pallet_content

Milestone-Based Payouts at Scale: Treasury Guardian Tool for Efficient Polkadot Treasury Spending

Subscan 2025 Q1-Q2 Funding Proposal: Basic service fee for the Kusama Relaychain and Kusama public parachain (AssetHub, Coretime, BridgeHub, People)

Anonymous OpenGov

Acuity Index: omni-indexer

THE RIGHT TO DISAPPEAR

Deciding

Garbage

Executed

Runtime upgrade 2.0.1 for Kusama Relay and Asset Hub

- Kusama was a sponsor at the Dark Prague event.
- A community member was asked to help fill the Kusama space at the last minute.
- Some Kusama community members attended, but the event was not very successful for Kusama.
- There were no new updates or products to show people, which made it hard to attract builders.
- Privacy is becoming important in web3, and Kusama should be at these events with better materials.
- The request is for 55 KSM to cover travel and stay costs.
- The person is not asking for food, taxis, or payment for their time.

[Small Spender] Tip for Dark Prague Oct 3-5 2025

- Some people want their money back for early proposals on Kusama.
- They paid 100 KSM to submit ideas, but now it only costs 0.0333 KSM.
- Their ideas were not approved, so they lost their money.
- The money is stuck and can't be returned normally.
- This happened because the rules were new and being tested.
- The only way to give the money back is through the community treasury.
- This helps make things fair for those who tried early.

Refund of Early OpenGov Submission Deposits

Preparing

- Kusama is now a peer network to Polkadot, not just a test network.
- Polkadot wants to manage identity for Kusama through its own system.
- Kusama should have its own identity system to stay independent.
- Relying on Polkadot could let them change or stop Kusama’s identity rules.
- Having separate systems makes both networks stronger and safer.
- Kusama can build its own identity tools and try new ideas.
- Voting "AYE" means Kusama controls its own identity.
- Voting "NAY" means Polkadot controls Kusama’s identity.

Wish for Change: Deploy Native Proof of Personhood Pallets on Kusama Infrastructure

[Whitelisted Caller] Upgrade Kusama AH to v2.0.1

Delay Demo #2 Treasury Guardian

- The referendum is about testing a new tool called Treasury Guardian.  
- It includes a payment to Mr. Bill Laboon, which might be delayed or canceled.  
- The tool helps with milestone-based payments to improve treasury efficiency.  
- The goal is to get more people involved in Kusama and Polkadot OpenGov.  
- Follow [TreasuryEff on X](https://x.com/TreasuryEff) for updates.

Kusama

referenda5

fellowship2

treasury29

discussions1393