candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

Polkadot Treasury operational update

bill_w3f

Brave Wallet - Status updates

Kyle Den Hartog

Bohemia Fam keeps pushing

Hydrated Daniel

<strong>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.</strong>

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:

hantoniu (no dm)

Welcome to the Polkadot Forum 👋

Getting started: Read this first

Arwen Smit

Introducing Birdbrain — a shared memory for the Kusama flock

birdbrain

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

Tech Talk

Metanode: early thinking on consolidating node services

Polkadot Technical Fellowship — OpenDev Call · Proceedings · 15 September 2026

Emiel Sebastiaan | JAMdot Technologies

Incentives for compounding staking rewards

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

Green Polkadot Validator Initiative — Verifiable Renewable Energy &amp; Ecosystem Incentives

Saibbo4

Green Polkadot Validator Initiative — Verifiable Renewable Energy & Ecosystem Incentives

US$104M a year of Bolivian mining revenue, settled on Polkadot — 10M+ transactions a year

A Proposal for a Kusama Future on JAM Prime

Mike

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

Ecosystem

Polkadot Socials Daily Digest: 2026-09-18

OpenShore

Polkadot Socials Daily Digest: 2026-09-17

Recurring Payments Using Stable Coins on Polkadot

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

Good reads on proof-of-personhood

Asset Hub Migration - XCM FAQ

Remy Le Berre

<p><strong>Community Idea for Discussion</strong></p>
<p>I am sharing this purely as an <strong>idea for discussion within the Polkadot community</strong>.</p>
<p>I am <strong>not requesting Treasury funding</strong>, and I am not proposing myself as the technical implementer, project manager, or fund recipient.</p>
<p>My intention is simply to bring this idea to the community. If validators, developers, researchers, or other ecosystem participants find it interesting, they are welcome to improve, modify, research, or develop it further.</p>
<p><strong>The Idea</strong></p>
<p>Polkadot validators rely on physical infrastructure: servers, networking equipment, data centers, and electricity.</p>
<p>Could Polkadot create a voluntary system allowing validators to <strong>prove that their infrastructure is powered by renewable energy</strong>?</p>
<p>Validators meeting independently verified requirements could receive a voluntary <strong>Green Validator</strong> status.</p>
<p>For example:</p>
<ul>
<li><strong>Green 80</strong> — at least 80% verified renewable energy</li>
<li><strong>Green 95</strong> — at least 95%</li>
<li><strong>Green 100</strong> — 100%</li>
</ul>
<p>These thresholds are only examples for discussion.</p>
<p>The main question is whether renewable-energy usage can be measured and verified reliably.</p>
<p><strong>How Could It Be Verified?</strong></p>
<p>Self-declaration should not be enough.</p>
<p>Possible evidence could include:</p>
<ul>
<li>electricity-provider data;</li>
<li>data-center energy attestations;</li>
<li>smart-meter measurements;</li>
<li>recognized renewable-energy certificates;</li>
<li>independent audits;</li>
<li>energy-data oracles.</li>
</ul>
<p>In the future, privacy-preserving cryptographic proofs could potentially allow a validator to prove that a certain percentage of its electricity came from approved renewable sources without revealing sensitive operational information.</p>
<p>The principle would be simple:</p>
<p><strong>Don’t trust the green claim. Verify it.</strong></p>
<p><strong>Preventing Greenwashing</strong></p>
<p>A credible system could include:</p>
<ul>
<li>periodic verification;</li>
<li>certification expiry;</li>
<li>independent attestations;</li>
<li>random audits;</li>
<li>protection against double counting;</li>
<li>different confidence levels depending on the quality of the evidence.</li>
</ul>
<p>It could also distinguish between directly measured renewable electricity and separately purchased renewable-energy certificates.</p>
<p><strong>Possible Incentives</strong></p>
<p>If reliable verification proved technically possible, the community could later discuss whether verified Green Validators should receive a <strong>small additional incentive</strong>.</p>
<p>Security, validator performance, reliability and decentralization should always remain more important than Green status.</p>
<p>A Green certificate should never compensate for poor validator performance.</p>
<p><strong>Green Nominators</strong></p>
<p>DOT holders could also voluntarily choose to support verified Green Validators.</p>
<p>If the community eventually introduced Green incentives, it could discuss whether nominators supporting verified Green Validators should also receive some form of additional incentive.</p>
<p>Participation should remain voluntary.</p>
<p><strong>Growth Validators</strong></p>
<p>A second concept could recognize validators that voluntarily reinvest part of their validator income into the Polkadot ecosystem.</p>
<p>Examples could include:</p>
<ul>
<li>applications;</li>
<li>developer tools;</li>
<li>security;</li>
<li>privacy technology;</li>
<li>decentralized identity;</li>
<li>infrastructure;</li>
<li>open-source development;</li>
<li>research.</li>
</ul>
<p>Where possible, these contributions could be publicly verifiable.</p>
<p>A validator could therefore potentially have a voluntary status such as:</p>
<p><strong>Green Validator</strong></p>
<p><strong>Growth Validator</strong></p>
<p><strong>Green + Growth Validator</strong></p>
<p><strong>Public Green Validator Registry</strong></p>
<p>If technically feasible, a public registry could show information such as:</p>
<ul>
<li>validator identity;</li>
<li>verified renewable-energy percentage;</li>
<li>verification confidence;</li>
<li>last verification date;</li>
<li>Green status;</li>
<li>Growth contribution status.</li>
</ul>
<p>Wallets and staking interfaces could eventually choose to display this information so nominators could consider sustainability alongside other validator characteristics.</p>
<p><strong>Start Small</strong></p>
<p>I am <strong>not suggesting an immediate change to Polkadot staking economics</strong>.</p>
<p>If the community believes the concept is worth exploring, interested contributors could first investigate a small voluntary proof of concept involving a limited number of validators.</p>
<p>The first objective would simply be to answer:</p>
<p><strong>Can validator energy provenance be verified reliably, privately, and at a reasonable cost?</strong></p>
<p>If the answer is no, the experiment could stop.</p>
<p>If the answer is yes, the community could then discuss whether incentives make sense.</p>
<p><strong>Future Compatibility With JAM</strong></p>
<p>This idea concerns <strong>Polkadot’s current validator infrastructure</strong>.</p>
<p>JAM is not required for this concept.</p>
<p>If JAM becomes part of Polkadot’s future production architecture, the community could later investigate whether similar renewable-energy verification mechanisms could be adapted to that infrastructure.</p>
<p>That is only a possible future research direction.</p>
<p><strong>Questions for the Community</strong></p>
<p>I would be interested in hearing opinions on:</p>
<ol>
<li>Is reliable renewable-energy verification for validators technically realistic?</li>
<li>Which verification methods would be credible?</li>
<li>How could greenwashing and double counting be prevented?</li>
<li>Would a voluntary Green Validator Registry be useful?</li>
<li>If verification worked, should Green Validators receive any additional incentive?</li>
<li>Should nominators supporting verified Green Validators also be considered?</li>
<li>Is the Growth Validator concept worth exploring?</li>
<li>Could this create unintended effects on validator decentralization?</li>
<li>Are validators, developers, researchers or energy specialists interested in exploring this concept further?</li>
</ol>
<p><strong>Conclusion</strong></p>
<p>This is <strong>not a funding request and not a finished technical proposal</strong>.</p>
<p>I am simply bringing an idea to the Polkadot community.</p>
<p>If the community believes the concept has merit, people with the appropriate technical, economic and energy-sector expertise are welcome to take it further.</p>
<p><strong>My goal is simply to put the idea on the table and start the discussion.</strong></p>

<p>I think moving everything to the validators would be too much of an overload for them, don’t you think? I’m proposing this; perhaps we could add RPC to the collators, but I’m not sure.</p>
<aside class="quote quote-modified" data-post="1" data-topic="18453">
  <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/ultracoconut/48/5932_2.png" class="avatar">
    <div class="quote-title__text-content">
      <a href="https://forum.polkadot.network/t/proposal-unified-collator-pool-for-system-chains-64-slots/18453">Proposal: Unified Collator Pool for System Chains (64 Slots)</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 "><span class="badge-category__name">Ecosystem</span></span></a>
    </div>
  </div>
  <blockquote>
    <a name="p-40654-short-description-1" class="anchor" href="#p-40654-short-description-1" aria-label="Heading link"></a>Short Description
I propose unifying the collator infrastructure of Polkadot’s System Chains — Polkadot Hub, Bridge Hub, People, Collectives, etc. — into a single shared pool of 64 active operators. 
Instead of maintaining separate collator sets for each System Chain, all operators would be capable of supporting the entire System Chain ecosystem. The protocol could then dynamically assign block production responsibilities across the pool. 
The goal is to reduce infrastructure fragmentation, impr…
  </blockquote>
</aside>


<p>We have had emails about this proposal off the forum. We would rather answer here. The money is public, so the questions and the answers should be public too — ask in the thread and it gets answered in the thread.</p>
<p>What does the treasury spend its marketing budget on? Users. That is what advertising, events and content are for — getting real people onto the chain. Roughly US$6.8 million over the last four quarters, against about 80,300 monthly active addresses. Call it US$85 per active address per year.</p>
<p>This proposal asks US$190,000 and brings 861,292 people. Twenty-two cents each.</p>
<p>There is no adoption funnel. A per-capita payment lands in each resident’s own self-custodied account every month and they spend it. Receiving is a transaction, spending is several more. Active addresses equal the enrolled population by construction. The only variable is the rollout: [ENROLLED] enrolled today across the 53 communities of the TIOC Nor Lípez in closed beta, scaling with the plant to the whole department. And they do not churn — a user bought with advertising leaves when the campaign stops; these are people receiving money they live on, under a contract, for forty-five years.</p>
<p>The balance sheet says the same. There is US$67.46m of stablecoin on Polkadot in total. This holds about US$15m resting, roughly 22% of that, and settles around US$104m a year at steady state — US$4.4 billion over the 45-year life of the project. It is not yield-seeking capital: it exists because a mine produced lithium and a contract obliges the operator to pay Potosí. It does not leave in a drawdown.</p>
<p>Why the treasury and not the operator — the fair question above. The mine is capitalised; the rail is not. An operator buys the cheapest thing that discharges its obligation, closed, on whatever chain is cheapest. Open source, and on Polkadot, are worth nothing to them. That is the only reason this is here.</p>
<p>The account name was a typo at registration; it is fixed.</p>
<p>What I want from this forum, and why this went up before any preimage: is REVM on Polkadot Hub the right target for a payout system of this shape, or would you route it differently?</p>
<p>Heitaria Swiss AG, Buochs</p>

<p>Sometimes you need the courage to make hard decisions. Sometimes you need to admit mistakes and take responsibility for them.</p>
<p>Continuing to spend time and money on Kusama makes no sense. It would be better to give the Devs one less thing to maintain and fix.</p>
<p>At this point, Kusama feels like a dead body we keep trying to resuscitate.</p>
<p>Instead of coming up with increasingly disconnected solutions and visions, maybe the most logical thing to do is simply shut Kusama down.</p>

<p>How many validators does JAM need per core?</p>
<p>On the other hand, regarding what you’re talking about 3 ZK proofs, it’s not JAM; there’s nothing that says that, nor is it in their specifications.</p>
<p>Furthermore, 3 proofs/core ≠ 3 core</p>

Bastian Köcher

The Road to JAM

<p>Bumping this thread to gather a bit more community eyes before taking this on-chain.</p>
<p>A quick question for frequent OpenGov voters and analysts: when auditing treasury or proposal history, what is the <em>single most frustrating data point</em> to track down right now? I want to make sure PolkAudit’s Phase 2 roadmap targets the biggest pain point. All feedback on the $10k scope is welcome!</p>

[Pre-Proposal Discussion] PolkAudit — Open-Source Governance Audit Dashboard

<h2><a name="p-41019-technical-1" class="anchor" href="#p-41019-technical-1" aria-label="Heading link"></a>Technical</h2>
<ul>
<li>A microcontroller verified Polkadot Devnet state via light client, with no RPC provider. Door-access control is next (via <a href="https://x.com/OliverTaleYazdi/status/2100490940939173953" rel="noopener nofollow ugc">OliverTaleYazdi</a>).</li>
<li>Asset Conversion is Asset Hub’s <code>assetConversion</code> pallet, not an EVM-style DEX. Anyone can create a pool for a token pair (via <a href="https://x.com/LeemoXD/status/2100573739914043872" rel="noopener nofollow ugc">LeemoXD</a>).</li>
</ul>
<h2><a name="p-41019-ecosystem-applications-2" class="anchor" href="#p-41019-ecosystem-applications-2" aria-label="Heading link"></a>Ecosystem &amp; Applications</h2>
<ul>
<li>Dotify added native payments with automatic splits via Polkadot Products, for paid tracks and direct artist support. CASH wrapping and proof-of-personhood access are next (via <a href="https://x.com/Thoth_Nzeng/status/2100538843128586649" rel="noopener nofollow ugc">Thoth_Nzeng</a>).</li>
<li>Subsquare lets proposers filter referendum comments. Defaults hide spam, 0-DOT, and no-identity accounts, but all comments stay accessible (via <a href="https://x.com/BillLaboon/status/2100469589062648061" rel="noopener nofollow ugc">BillLaboon</a>).</li>
</ul>
<hr>
<h2><a name="p-41019-processing-log-3" class="anchor" href="#p-41019-processing-log-3" aria-label="Heading link"></a>PROCESSING LOG</h2>
<ul>
<li><strong>Report Generated:</strong> 2026-09-18 10:04:10</li>
<li><strong>Total X posts curated:</strong> 664</li>
<li><strong>Posts Filtered and Analysed:</strong> 641</li>
<li><strong>Data Source:</strong> X (Twitter)</li>
</ul>
<hr>
<p><sup>This report is auto-generated and provided for informational purposes only by OpenShore, a Pala Labs initiative. The content is based on posts from X and may contain inaccuracies. We do not guarantee its completeness or correctness.</sup></p>

<p>These calls should continue. I personally like this format.</p>

<p>We published our follow-up to this discussion in a position paper: <a href="https://forum.polkadot.network/t/a-proposal-for-a-kusama-future-on-jam-prime/18683" class="inline-onebox">A Proposal for a Kusama Future on JAM Prime</a></p>
<p>We encourage further discussion to take place is the new forum post.</p>

Kusama Futures in the JAM Era

<p>Thanks for the link.</p>
<p>In that case, however, we really ought to ask why a figure of $5,000 USD is being proposed.</p>
<p>We all know that running a validator incurs almost no cost.</p>
<p>Can, do we want to, and should we afford this selling pressure?</p>

<p>I have a solution for that:</p>
<aside class="quote quote-modified" data-post="1" data-topic="18453">
  <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/ultracoconut/48/5932_2.png" class="avatar">
    <div class="quote-title__text-content">
      <a href="https://forum.polkadot.network/t/proposal-unified-collator-pool-for-system-chains-64-slots/18453">Proposal: Unified Collator Pool for System Chains (64 Slots)</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 "><span class="badge-category__name">Ecosystem</span></span></a>
    </div>
  </div>
  <blockquote>
    <a name="p-40654-short-description-1" class="anchor" href="#p-40654-short-description-1" aria-label="Heading link"></a>Short Description
I propose unifying the collator infrastructure of Polkadot’s System Chains — Polkadot Hub, Bridge Hub, People, Collectives, etc. — into a single shared pool of 64 active operators. 
Instead of maintaining separate collator sets for each System Chain, all operators would be capable of supporting the entire System Chain ecosystem. The protocol could then dynamically assign block production responsibilities across the pool. 
The goal is to reduce infrastructure fragmentation, impr…
  </blockquote>
</aside>


System Chains: The Same Bad Actors Again

<h2><a name="p-40996-technical-1" class="anchor" href="#p-40996-technical-1" aria-label="Heading link"></a>Technical</h2>
<ul>
<li>KusamaShield reported nearly <strong>3 TB of data</strong> served through its Kusama RPC over the past month, pointing to continued infrastructure usage on Kusama (via <a href="https://x.com/KusamaShield/status/2100262655877656727" rel="noopener nofollow ugc">KusamaShield</a>).</li>
<li>ComputeFlux said it is building an <strong>agent-native Polkadot stack</strong>, positioning itself as an intelligence and compute layer for AI agents operating onchain (via <a href="https://x.com/computefluxAI/status/2100266314048913554" rel="noopener nofollow ugc">computefluxAI</a>).</li>
</ul>
<h2><a name="p-40996-ecosystem-2" class="anchor" href="#p-40996-ecosystem-2" aria-label="Heading link"></a>Ecosystem</h2>
<ul>
<li><strong>Polkadot Vibe Check <span class="hashtag-raw">#24</span></strong> covered the Road to JAM, Kusama’s role in the JAM era, and examples of using AI with Polkadot (via <a href="https://x.com/RepublikLabs/status/2100218374018187662" rel="noopener nofollow ugc">RepublikLabs</a>, <a href="https://x.com/jslusser/status/2100295369284350229" rel="noopener nofollow ugc">jslusser</a>).</li>
<li>Polytope Labs co-founder Seun Lanlege is set to speak at <strong>Africa Blockfest Nairobi</strong>, with Hyperbridge, HyperFX and Polkadot-Cosmos cross-chain infrastructure among the highlighted themes (via <a href="https://x.com/africablockfest/status/2100172491339522146" rel="noopener nofollow ugc">africablockfest</a>).</li>
<li>Acurast’s decentralized compute network was spotlighted for using smartphones across <strong>175+ countries</strong> to perform verifiable work via TEEs (via <a href="https://x.com/cas_abbe/status/2100135965276950644" rel="noopener nofollow ugc">cas_abbe</a>).</li>
</ul>
<hr>
<h2><a name="p-40996-processing-log-3" class="anchor" href="#p-40996-processing-log-3" aria-label="Heading link"></a>PROCESSING LOG</h2>
<ul>
<li><strong>Report Generated:</strong> 2026-09-17 10:04:00</li>
<li><strong>Total X posts curated:</strong> 682</li>
<li><strong>Posts Filtered and Analysed:</strong> 651</li>
<li><strong>Data Source:</strong> X (Twitter)</li>
</ul>
<hr>
<p><sup>This report is auto-generated and provided for informational purposes only by OpenShore, a Pala Labs initiative. The content is based on posts from X and may contain inaccuracies. We do not guarantee its completeness or correctness.</sup></p>

<p>For people who build SaaS or run node/RPC services: do you see a need for recurring payments in stablecoins, or crypto in general?</p>
<p>The other day I was thinking about building a single place for managing all my subscriptions, but I don’t see why many companies would use that, unless the purpose was accepting crypto.</p>
<p>That would be possible to build on Polkadot, but I’m not sure if it would actually be useful. I assume most of you are billing with credit cards today, has a anyone ever asked to pay in crypto instead?</p>

<h2><a name="p-40983-treasury-1" class="anchor" href="#p-40983-treasury-1" aria-label="Heading link"></a>Treasury</h2>
<ul>
<li>Polkadot Treasury stablecoin inflows continued, with another 130,000 USDC/USDT added today and reported weekly inflows reaching 1.05M (via <a href="https://x.com/BillLaboon/status/2099851763138355324" rel="noopener nofollow ugc">BillLaboon</a>).</li>
</ul>
<h2><a name="p-40983-technical-2" class="anchor" href="#p-40983-technical-2" aria-label="Heading link"></a>Technical</h2>
<ul>
<li>Polkadot SDK 1.24.2 <code>stable2606-2</code> was released as a patch for the latest stable branch (via <a href="https://x.com/BillLaboon/status/2099798339805999281" rel="noopener nofollow ugc">BillLaboon</a>).</li>
<li>JAM implementation work continued, with posts noting migration of parachain functionality toward a JAM service and production targeted for 2027 (via <a href="https://x.com/BeeCrypto10/status/2099865380244095327" rel="noopener nofollow ugc">BeeCrypto10</a>, <a href="https://x.com/iiam_Akshay/status/2099912913591079201" rel="noopener nofollow ugc">iiam_Akshay</a>).</li>
<li>Updated Polkadot app documentation now outlines a builder path covering local development, on-chain deployment, <code>.dot</code> domain registration and app listing (via <a href="https://x.com/cryptowolfN/status/2099867820112703919" rel="noopener nofollow ugc">cryptowolfN</a>).</li>
</ul>
<h2><a name="p-40983-ecosystem-3" class="anchor" href="#p-40983-ecosystem-3" aria-label="Heading link"></a>Ecosystem</h2>
<ul>
<li>Karim Jedda of Parity discussed online content verification in an AI-generated media environment, with Polkadot Products positioning authenticity, identity and privacy as key design problems for a more human internet (via <a href="https://x.com/OpenShorex/status/2099927323386716622" rel="noopener nofollow ugc">OpenShorex</a>, <a href="https://x.com/DaBlockDAO/status/2099927857367515157" rel="noopener nofollow ugc">DaBlockDAO</a>).</li>
<li>Weekly institutional flow data showed roughly $663K of net inflows into DOT products (via <a href="https://x.com/iiam_Akshay/status/2099848534690505105" rel="noopener nofollow ugc">iiam_Akshay</a>).</li>
</ul>
<hr>
<h2><a name="p-40983-processing-log-4" class="anchor" href="#p-40983-processing-log-4" aria-label="Heading link"></a>PROCESSING LOG</h2>
<ul>
<li><strong>Report Generated:</strong> 2026-09-16 10:05:22</li>
<li><strong>Total X posts curated:</strong> 669</li>
<li><strong>Posts Filtered and Analysed:</strong> 639</li>
<li><strong>Data Source:</strong> X (Twitter)</li>
</ul>
<hr>
<p><sup>This report is auto-generated and provided for informational purposes only by OpenShore, a Pala Labs initiative. The content is based on posts from X and may contain inaccuracies. We do not guarantee its completeness or correctness.</sup></p>

Polkadot Socials Daily Digest: 2026-09-16

<p>After an initial investigation, the total xcDOT supply in Moonbeam’s terminal state is 233,451.672748423 xcDOT.</p>
<p>Because no complete backup node is available, we reconstructed a candidate holder set using multiple public RPCs, blockchain explorers, and indexed data sources. We ultimately identified 11,785 non-zero addresses, with a combined balance of 233,450.6800114108 xcDOT. 0.9927370122 xcDOT remains unattributed.</p>
<p>The current results are public here:</p><aside class="onebox allowlistedgeneric" data-onebox-src="https://libingjiang47.github.io/xcdot-recovery-kit/">
  <header class="source">

      <a href="https://libingjiang47.github.io/xcdot-recovery-kit/" target="_blank" rel="noopener nofollow ugc">libingjiang47.github.io</a>
  </header>

  <article class="onebox-body">
    

<h3><a href="https://libingjiang47.github.io/xcdot-recovery-kit/" target="_blank" rel="noopener nofollow ugc">xcDOT Terminal Snapshot</a></h3>

  <p>A static reader for the frozen xcDOT terminal state evidence.</p>


  </article>

  <div class="onebox-metadata">
    
    
  </div>

  <div style="clear: both"></div>
</aside>

<p>Every published balance includes a corresponding Substrate state proof and can be independently verified against Moonbeam’s terminal state root. This means the balance data does not require trusting any particular RPC, explorer, or indexing service.</p>
<p>These addresses likely include different account types such as EOAs, contracts, multisigs, and AA / smart accounts. For ordinary private-key-controlled addresses, control may be proven by signature, while contracts and smart accounts may require different recovery paths.</p>
<p>This is still only a preliminary recovery dataset. It does not represent a final determination of ownership, claim eligibility, or a recovery plan, and there may still be issues I have missed.</p>
<p>The full dataset, proofs, and verification tools are public, and I have also posted the results on X for wider community review:</p>
<aside class="onebox githubrepo" data-onebox-src="https://github.com/libingjiang47/xcdot-recovery-kit">
  <header class="source">

      <a href="https://github.com/libingjiang47/xcdot-recovery-kit" target="_blank" rel="noopener nofollow ugc">github.com</a>
  </header>

  <article class="onebox-body">
    <div class="github-row" data-github-private-repo="false">
  <img width="690" height="344" src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/d/d0b0ad4079ad9adeab00a1636056f3f11282586a_2_690x344.png" class="thumbnail" data-dominant-color="F2F0EE">

  <h3><a href="https://github.com/libingjiang47/xcdot-recovery-kit" target="_blank" rel="noopener nofollow ugc">GitHub - libingjiang47/xcdot-recovery-kit</a></h3>

    <p><span class="github-repo-description">Contribute to libingjiang47/xcdot-recovery-kit development by creating an account on GitHub.</span></p>
</div>

  </article>

  <div class="onebox-metadata">
    
    
  </div>

  <div style="clear: both"></div>
</aside>
<aside class="onebox twitterstatus" data-onebox-src="https://x.com/libingjiang47/status/2099903199117517089">
  <header class="source">

      <a href="https://x.com/libingjiang47/status/2099903199117517089" target="_blank" rel="noopener nofollow ugc">x.com</a>
  </header>

  <article class="onebox-body">
    <img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/f/fbdc48e70e1fd5530574447ea8a5f2b36cb55334.jpeg" class="thumbnail onebox-avatar" alt="" data-dominant-color="B27954" width="48" height="48">
<h4><a href="https://x.com/libingjiang47/status/2099903199117517089" target="_blank" rel="noopener nofollow ugc">libingjiang</a></h4>
<div class="twitter-screen-name"><a href="https://x.com/libingjiang47/status/2099903199117517089" target="_blank" rel="noopener nofollow ugc">@libingjiang47</a></div>

<div class="tweet">
  <span class="tweet-description">The xcDOT recovery snapshot is now public.
We identified 11,785 addresses with non-zero xcDOT balances in Moonbeam’s terminal state.
Verified balance:
233,450.6800114108 xcDOT
Explorer:
<a target="_blank" href="https://libingjiang47.github.io/xcdot-recovery-kit/" rel="noopener nofollow ugc">libingjiang47.github.io/xcdot-recovery…</a></span>
</div>

<div class="date">
  <a href="https://x.com/libingjiang47/status/2099903199117517089" class="timestamp" target="_blank" rel="noopener nofollow ugc">4:48 PM - 15 Sep 2026</a>


</div>

  </article>

  <div class="onebox-metadata">
    
    
  </div>

  <div style="clear: both"></div>
</aside>

<p>If anyone finds an issue with the terminal-state anchor, address set, balances, proofs, or recovery assumptions, please point it out publicly.</p>

robert

Advice requested: recovery path for DOT backing stranded xcDOT after Moonbeam shutdown

<h2><a name="p-40973-governance-1" class="anchor" href="#p-40973-governance-1" aria-label="Heading link"></a>Governance</h2>
<ul>
<li>Polkadot Treasury received another <strong>$610k in USDT/USDC</strong> from the legacy Treasury account, bringing stablecoin additions to <strong>$920k over the past week</strong> (via <a href="https://x.com/BillLaboon/status/2099514333130596598" rel="noopener nofollow ugc">BillLaboon</a>).</li>
<li>Research proposed reducing Polkadot’s maximum validator nominations from <strong>16 to 8</strong>, based on observed nomination usage patterns (via <a href="https://x.com/rossbulat/status/2099352841450381381" rel="noopener nofollow ugc">rossbulat</a>).</li>
</ul>
<h2><a name="p-40973-technical-network-2" class="anchor" href="#p-40973-technical-network-2" aria-label="Heading link"></a>Technical &amp; Network</h2>
<ul>
<li>Polkadot Academy’s <strong>Catamarca On-Chain</strong> program gained local media coverage in Argentina following its institutional opening at Casa de Gobierno with provincial officials (via <a href="https://x.com/AcademyPolkadot/status/2099490318689148969" rel="noopener nofollow ugc">AcademyPolkadot</a>).</li>
<li>Polkadot Hub developer materials show support for paying a <strong>DOT transfer fee in USDT</strong>, highlighting alternative fee assets as a UX improvement (via <a href="https://x.com/cryptowolfN/status/2099480316578570302" rel="noopener nofollow ugc">cryptowolfN</a>).</li>
<li>Chainspect ranked Polkadot <span class="hashtag-raw">#1</span> for decentralization with a <strong>Nakamoto Coefficient of 177</strong> (via <a href="https://x.com/chainspect_app/status/2099451243454165376" rel="noopener nofollow ugc">chainspect_app</a>).</li>
<li>Bifrost reported <strong>120,000 vDOT</strong> redeemed in about 31 hours, representing nearly <strong>200,000 DOT</strong>, with Fast Redeem reducing wait time by around <strong>34%</strong> versus Polkadot’s native unbonding period (via <a href="https://x.com/Bifrost/status/2099437508623053144" rel="noopener nofollow ugc">Bifrost</a>).</li>
</ul>
<hr>
<h2><a name="p-40973-processing-log-3" class="anchor" href="#p-40973-processing-log-3" aria-label="Heading link"></a>PROCESSING LOG</h2>
<ul>
<li><strong>Report Generated:</strong> 2026-09-15 10:03:26</li>
<li><strong>Total X posts curated:</strong> 624</li>
<li><strong>Posts Filtered and Analysed:</strong> 601</li>
<li><strong>Data Source:</strong> X (Twitter)</li>
</ul>
<hr>
<p><sup>This report is auto-generated and provided for informational purposes only by OpenShore, a Pala Labs initiative. The content is based on posts from X and may contain inaccuracies. We do not guarantee its completeness or correctness.</sup></p>

Polkadot Socials Daily Digest: 2026-09-15

<p>Should work now <code>https://parity.io/rss.xml</code> <img src="https://emoji.discourse-cdn.com/twitter/victory_hand.png?v=15" title=":victory_hand:" class="emoji" alt=":victory_hand:" loading="lazy" width="20" height="20"></p>

Karim | Applied Engineering @ Parity

Could Parity add an RSS feed to its blog?

<h2><a name="p-40962-ecosystem-1" class="anchor" href="#p-40962-ecosystem-1" aria-label="Heading link"></a>Ecosystem</h2>
<ul>
<li><strong>Polkadot Academy launched Catamarca On-Chain in Argentina</strong>: The programme opened at Casa de Gobierno with provincial officials, including Governor Raúl Jalil, focused on blockchain and digital governance training (via <a href="https://x.com/AcademyPolkadot/status/2098938066421289412" rel="noopener nofollow ugc">AcademyPolkadot</a>, <a href="https://x.com/jslusser/status/2099125295877968025" rel="noopener nofollow ugc">jslusser</a>).</li>
<li><strong>PAY IT added Polkadot to supported networks</strong>: The payments platform listed Polkadot among its live supported chains, alongside Bitcoin, Ethereum, Solana and others (via <a href="https://x.com/Payit_xyz/status/2098938492248051984" rel="noopener nofollow ugc">Payit_xyz</a>).</li>
<li><strong>KodaDot-linked NFT works appeared on secondary markets</strong>: An artist noted that pieces from the NFT Paris 2025 exhibition organised by KodaDot and Polkadot are available on ChaoticApp’s secondary marketplace, priced in DOT (via <a href="https://x.com/V4wEnko/status/2099074405015888245" rel="noopener nofollow ugc">V4wEnko</a>).</li>
</ul>
<h2><a name="p-40962-market-2" class="anchor" href="#p-40962-market-2" aria-label="Heading link"></a>Market</h2>
<ul>
<li><strong>21Shares TDOT ETF flows drew attention</strong>: 10x Research cited steady inflows into the 21Shares TDOT spot ETF while noting DOT’s recent weekly performance (via <a href="https://x.com/10xResearch/status/2098912541128995152" rel="noopener nofollow ugc">10xResearch</a>, <a href="https://x.com/RipBullWinkle/status/2098918144815329572" rel="noopener nofollow ugc">RipBullWinkle</a>).</li>
</ul>
<hr>
<h2><a name="p-40962-processing-log-3" class="anchor" href="#p-40962-processing-log-3" aria-label="Heading link"></a>PROCESSING LOG</h2>
<ul>
<li><strong>Report Generated:</strong> 2026-09-14 10:05:54</li>
<li><strong>Total X posts curated:</strong> 635</li>
<li><strong>Posts Filtered and Analysed:</strong> 610</li>
<li><strong>Data Source:</strong> X (Twitter)</li>
</ul>
<hr>
<p><sup>This report is auto-generated and provided for informational purposes only by OpenShore, a Pala Labs initiative. The content is based on posts from X and may contain inaccuracies. We do not guarantee its completeness or correctness.</sup></p>

Polkadot Socials Daily Digest: 2026-09-14

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

Blockchain Alert Platform for Web3 | BlockPing

Encointer System Chain – Infrastructure Operations (Apr–Dec 2026)

Encointer Retroactive Treasury Proposal for July-Dec 2025

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

Pilot Proposal: RMTerra "Choose Green" RegenFi - RWA  (Small Spender, ~10k KSM)

ZKAMA - ZK Verifier SDK Proposal {Post-AssetHub Hackathon Curation}

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)

# Kusama Coretime Referendum

## What is this?
This is a vote about who helps run **Kusama Coretime**, a part of the Kusama network.

## What is changing?
- Kusama Coretime is called a **Tier-2** chain, which means it is somewhat important.
- It will have **4 special collators** (helpers) paid by the community.
- It will also have **2 open slots** anyone can apply for.

## New helpers being added
- STKD
- Chris-Staking
- HYPERSPEED
- TUXEDO

## Helpers being removed
- CoinStudio
- YellowFin / Bluefin Tuna
- Turboflakes
- LuckyFriday
- Mile
- The previous invulnerable helper

## What stays the same?
- None of the old helpers are kept in the new group.

## Final list of helpers
- STKD
- Chris-Staking
- HYPERSPEED
- TUXEDO

## Who wrote this?
Will from Paradox (ParaNodes.io).

Deciding

Kusama Coretime — Invulnerable Collator Set Adjustment

# Kusama People Referendum

This is a vote about **Kusama People**, a blockchain in the Kusama network.

- Kusama People is a **Tier 1** chain. That means it is very important.
- It will have **8 special collators**. Collators are computers that help run the chain.
- These 8 collators are paid by the community.
- There will also be **4 open slots** for anyone to become a collator.
- **6 new collators** are being added to the team.
- **6 old collators** are being removed.
- **2 collators** are staying: CoinStudio and Stakeworld.

The goal is to pick collators who have done a good job for a long time.

Kusama People — Invulnerable Collator Set Adjustment

# Kusama Bridge Hub Referendum

## What is this?
This is a vote to change the special computer helpers for Kusama Bridge Hub.

## What are the changes?
- Kusama Bridge Hub is a **Tier 1** chain. That means it is very important.
- It will have **8 special helpers** paid by the community.
- It will have **4 open slots** for other helpers.

## Who is joining?
- BESTVALIDATOR / Zurich
- CoinStudio
- MathCrypto
- openbitlab
- Staker Space
- Faraday

## Who is leaving?
- Four old helpers are being removed.

## Who is staying?
- YellowFin / Bluefin Tuna
- Mile

## Why does this matter?
- The goal is to pick helpers who are reliable and have been around a long time.
- The change also keeps the open helper slots from being too many compared to the special helpers.

Kusama Bridge Hub — Invulnerable Collator Set Adjustment

**Kusama Asset Hub Collator Referendum**

- This is a vote about who helps run **Kusama Asset Hub**.
- Kusama Asset Hub is very important, so it is called a **Tier 1** chain.
- It will have **8 special collators** that the community pays for.
- It will also have **4 open spots** for anyone to join.
- Two collators are **being added**: **MegaTron / Eric** and **DPSTK / Dapestake**.
- Three old collators are **being removed**.
- Six collators are **staying**.
- This plan helps keep the important chain safe and working well.

Kusama Asset Hub — Invulnerable Collator Set Adjustment

# Kusama System Parachain Collator Funding Top-Up

- Kusama wants to give more money to help run small computer helpers called "collators."
- This money will pay for seven months, from July 2026 to January 2027.
- It will pay for 30 helpers on five different Kusama projects.
- It will also pay 3 people to watch over the work and pay for computers and internet.
- The total cost is about $60,725, which is about 17,262 KSM.
- They need this money sooner than planned because KSM is worth less now.
- The plan is the same as before, and nothing costs more than last time.

Executed

Kusama System Collator Bounty 2nd Top-up - 2026

# Kusama Shield Audit

Kusama Shield is a project that keeps people's digital money safe and private on Kusama, Polkadot, and Paseo.

- The project is one of the first to use special "Zero Knowledge" tech on the network.
- It was paid for by the community's treasury.
- The team now needs a security expert to check their code, because real people's money is involved.
- They are asking the community to pay about 56,605 US dollars for this safety check.
- There is only one step (milestone) in this plan.
- The team says their price is much lower than other similar audits.
- People have already used it: about 4,000 to 5,000 private transactions on Paseo, and around 200 on Polkadot.
- Two earlier proposals were liked by the community, with 99% and 89% voting yes.

Rejected

Kusama Shield Audit

- Subscan is a tool to see what happens on Kusama.
- It will work for all of 2026.
- The community pays a small amount each month.
- If service is bad, the community can stop paying.
- The price is lower than before.

Kusama

referenda6

treasury28

discussions1391