candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

Does Kusama Asset Hub actively accept anything other than Kusama?

Rust Syndicate

The Current State of Jobs in the Polkadot Ecosystem &amp; Introducing DotJobs

Diego

The Current State of Jobs in the Polkadot Ecosystem & Introducing DotJobs

Using multiple physical Ledger devices on staking.polkadot.cloud?

bill_w3f

<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:

Rajesh Shirsagar

Welcome to the Polkadot Forum 👋

Getting started: Read this first

Polkadot Forum Super Admin

Master / PhD student in Cryptology

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

Tech Talk

RFC: Polkadollar - A Modular Stablecoin Infrastructure for Polkadot

Prasad | Chainscore Labs

Why Polkadot-API?

Josep

DOT 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

Transparency in DN Validator Selection — Community Concerns

Ruby

Treasury Proposal: ink! v6 and cargo-contracts Security Audit by Oak Security

Michi

Treasury Guardianship

Gabriel

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

Ecosystem

:sparkles: October 2025 Updates to the Ecosystem Resource Center

Ivan - Distractive

✨ October 2025 Updates to the Ecosystem Resource Center

Tapping the underused developer power of PBA graduates

K Gunjan

Why does Polkadot not building products?

Give more than you receive

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

<p>Hey community,</p>
<p>Over the past few months, the Polkadot community has been actively discussing the future of <strong>native stablecoins</strong>, most notably through <a href="https://github.com/polkadot-fellows/RFCs/pull/155" rel="noopener nofollow ugc">RFC-155: pUSD</a> and Referendum <a href="https://polkadot.polkassembly.io/referenda/1761" rel="noopener nofollow ugc">#1761</a>.</p>
<p>While these efforts aim to bring</p>
<p>Blockquote</p>
<p>stability and liquidity to the Polkadot ecosystem, we believe a more <strong>strategic and scalable direction</strong> is possible—one that <strong>empowers the entire ecosystem</strong>, rather than deploying a single monolithic stablecoin. Polkadot’s is home to some of the most advanced Web3 technology, yet it faces a stablecoin liquidity deficit. With less than $100 million in stablecoins, we have captured <strong>under 0.03%</strong> of a global market that now exceeds $300 billion.</p>
<p>We are seeing a powerful trend across DeFi: the rise of application-specific stablecoins. Projects on Ethereum/Solana (eg like Aave with GHO, Curve’s crvUSD, Ethena’s USDe) and our own ecosystem’s Hydration (with HOLLAR) have shown that dApps thrive when they have their own native stable assets for value capture and user retention.  Every major application will soon prefer its own stablecoin — tailored to its economy, risk appetite, and user base.</p>
<p>Instead of building a single, monolithic stablecoin that competes with our own ecosystem projects and concentrates systemic risk, what if we built the foundational infrastructure for a thousand stablecoins to bloom?</p>
<hr>
<h3><a name="p-34638-introducing-polkadollar-codename-open-to-suggestions-1" class="anchor" href="#p-34638-introducing-polkadollar-codename-open-to-suggestions-1"></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"> Introducing Polkadollar (codename, open to suggestions)</h3>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/9/99f7dcb8bf5eb1d00ed68751b4563d10ad0be27e.jpeg" data-download-href="/uploads/short-url/lY45UfX8whNz5Q1wHlBWVuITz9Y.jpeg?dl=1" title="Polka_Dollar" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/9/99f7dcb8bf5eb1d00ed68751b4563d10ad0be27e_2_690x460.jpeg" alt="Polka_Dollar" data-base62-sha1="lY45UfX8whNz5Q1wHlBWVuITz9Y" width="690" height="460" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/9/99f7dcb8bf5eb1d00ed68751b4563d10ad0be27e_2_690x460.jpeg, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/9/99f7dcb8bf5eb1d00ed68751b4563d10ad0be27e_2_1035x690.jpeg 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/9/99f7dcb8bf5eb1d00ed68751b4563d10ad0be27e_2_1380x920.jpeg 2x" data-dominant-color="49271A"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">Polka_Dollar</span><span class="informations">1536×1024 674 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>
<p>We’re introducing <strong>Polkadollar</strong>, a <strong>modular stablecoin infrastructure layer</strong> for Polkadot, designed to enable <em>any</em> parachain, app-chain, or dApp to launch its own stablecoin with minimal effort, maximal flexibility, and strong interoperability — a set of Smart Contracts or a Pallet that form a <em>“Stablecoin Hub”</em> on Polkadot.</p>
<p>It’s designed to:</p>
<ul>
<li>
<p>Enable any app to <strong>launch its own stablecoin</strong> through a permissionless <strong>Stablecoin Factory on Hub</strong>.</p>
</li>
<li>
<p>Provide <strong>Stable AMMs</strong> to ensure deep, slippage-minimized liquidity.</p>
</li>
<li>
<p>Allow <strong>1:1 stablecoin swaps</strong> via a built-in <strong>Peg Stability Module (PSM)</strong>.</p>
</li>
<li>
<p>Let dApps <strong>earn 4–6% APY</strong> of stablecoin TVL from protocol-level “real yield” (staking, RWAs, money markets) - adding a major chunk to their revenue</p>
</li>
<li>
<p>Unlock <strong>LST-backed collateralization</strong>, tapping into billions in productive assets like vDOT, GETH, and GDOT.</p>
</li>
<li>
<p>Insurance module that <strong>covers for bad debt</strong>, and allows users earn yield with idle capital</p>
</li>
</ul>
<p>The design moves away from “one-size-fits-all” stablecoins to a <strong>federated ecosystem</strong> of stable assets — each app governing its own risk, while sharing a unified liquidity and collateral infrastructure.</p>
<hr>
<h3><a name="p-34638-core-components-2" class="anchor" href="#p-34638-core-components-2"></a><img src="https://emoji.discourse-cdn.com/twitter/gear.png?v=15" title=":gear:" class="emoji" alt=":gear:" loading="lazy" width="20" height="20"> Core Components</h3>
<div class="md-table">
<table>
<thead>
<tr>
<th>Component</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Stablecoin Factory</strong></td>
<td>Permissionless minting engine (Maker-style CDPs) for apps to define collateral, ratios, and fees.</td>
</tr>
<tr>
<td><strong>Stable AMMs</strong></td>
<td>Curve-style StableSwap pools for stablecoins to trade with minimal slippage.</td>
</tr>
<tr>
<td><strong>1:1 Swap Module (PSM)</strong></td>
<td>Unified liquidity layer allowing direct stable-to-stable swaps at $1 parity.</td>
</tr>
<tr>
<td><strong>Yield Engine</strong></td>
<td>Blue-chip Collateral &amp; Stablecoin yield (staking + RWAs + lending) shared back to dApps and users (target 4–6% APY).</td>
</tr>
<tr>
<td><strong>LST Collateral Integration</strong></td>
<td>Support for productive assets (vDOT, stETH, etc.), enabling higher capital efficiency.</td>
</tr>
<tr>
<td></td>
<td></td>
</tr>
<tr>
<td><strong>Insurance Module</strong></td>
<td>Cover for bad debt, enabling investors to earn attractive interest on their idle capital</td>
</tr>
</tbody>
</table>
</div><hr>
<h3><a name="p-34638-why-this-matters-for-polkadot-3" class="anchor" href="#p-34638-why-this-matters-for-polkadot-3"></a><img src="https://emoji.discourse-cdn.com/twitter/bar_chart.png?v=15" title=":bar_chart:" class="emoji" alt=":bar_chart:" loading="lazy" width="20" height="20"> Why This Matters for Polkadot</h3>
<div class="md-table">
<table>
<thead>
<tr>
<th>Stakeholder</th>
<th>Key Benefit</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Developers</strong></td>
<td>Launch stablecoins in minutes; earn sustainable yield; achieve protocol sovereignty.</td>
</tr>
<tr>
<td><strong>Users</strong></td>
<td>Stable, yield-bearing assets; composable swaps; lower volatility.</td>
</tr>
<tr>
<td><strong>Traders/LPs</strong></td>
<td>Deep, low-risk stable pools with arbitrage opportunities.</td>
</tr>
<tr>
<td><strong>Polkadot Treasury</strong></td>
<td>Earns protocol-level fees; retains liquidity; boosts TVL and DOT utility.</td>
</tr>
</tbody>
</table>
</div><p>A single treasury-funded stablecoin (like pUSD) centralizes both risk and reward.<br>
A factory-based model <strong>distributes risk</strong>, <strong>multiplies innovation</strong>, and <strong>aligns incentives</strong> across the entire network.</p>
<hr>
<h3><a name="p-34638-the-lst-opportunity-4" class="anchor" href="#p-34638-the-lst-opportunity-4"></a><img src="https://emoji.discourse-cdn.com/twitter/chart_increasing_with_yen.png?v=15" title=":chart_increasing_with_yen:" class="emoji" alt=":chart_increasing_with_yen:" loading="lazy" width="20" height="20"> The LST Opportunity</h3>
<p>The <strong>Liquid Staking Token market now exceeds $70B</strong>, with assets like stETH, rETH, and vDOT offering intrinsic yields of 5–10%.</p>
<p>By integrating LSTs as core collateral:</p>
<ul>
<li>
<p>Polkadot can <strong>unlock billions in latent liquidity</strong>.</p>
</li>
<li>
<p>Attract users from other ecosystems (e.g., ETH holders minting Polkadot-native stables with bridged stETH).</p>
</li>
<li>
<p>Capture <strong>real yield</strong> from staked capital — enhancing Treasury sustainability.</p>
</li>
</ul>
<p>Ignoring this market, as the current DOT-only model does, is a missed opportunity for Polkadot to lead in DeFi innovation.</p>
<hr>
<h3><a name="p-34638-strategic-positioning-5" class="anchor" href="#p-34638-strategic-positioning-5"></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"> Strategic Positioning</h3>
<p>Instead of having a single <em>“central bank stablecoin”</em>, Polkadollar proposes having a <strong>financial plumbing</strong> that lets <strong>every parachain become its own bank</strong>.</p>
<p>This modular, composable approach:</p>
<ul>
<li>
<p>Mirrors the <strong>M0 protocol</strong> model (multi-issuer stablecoin infra).</p>
</li>
<li>
<p>Promotes competition, innovation, and risk isolation.</p>
</li>
<li>
<p>Establishes Polkadot as the <strong>first Layer-0 with native multi-stablecoin support</strong>.</p>
</li>
</ul>
<p>Though, a similar model of having a stablecoin treasury backed, say PUSD, could be a unifying stablecoin and be also used to back other stablecoins as in below:</p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/1/104b56e5b80465fd1be02a0d6eb205c6c252aab2.jpeg" data-download-href="/uploads/short-url/2k93jNNkMjp2w4SaOFwrOizOBnI.jpeg?dl=1" title="PUSD-Interop" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/1/104b56e5b80465fd1be02a0d6eb205c6c252aab2_2_690x460.jpeg" alt="PUSD-Interop" data-base62-sha1="2k93jNNkMjp2w4SaOFwrOizOBnI" width="690" height="460" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/1/104b56e5b80465fd1be02a0d6eb205c6c252aab2_2_690x460.jpeg, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/1/104b56e5b80465fd1be02a0d6eb205c6c252aab2_2_1035x690.jpeg 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/1/104b56e5b80465fd1be02a0d6eb205c6c252aab2_2_1380x920.jpeg 2x" data-dominant-color="E9E3EC"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">PUSD-Interop</span><span class="informations">1536×1024 116 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>
<hr>
<h3><a name="p-34638-requesting-feedback-6" class="anchor" href="#p-34638-requesting-feedback-6"></a><img src="https://emoji.discourse-cdn.com/twitter/magic_wand.png?v=15" title=":magic_wand:" class="emoji" alt=":magic_wand:" loading="lazy" width="20" height="20">  Requesting Feedback</h3>
<p>We are submitting <strong>Polkadollar</strong> for open community review before formalizing it as a <strong>Treasury Proposal</strong>.</p>
<p><strong><a href="https://docs.google.com/document/d/1e9vLx12fuK2b1oU8V9le3pjCYTeBYlAJwaQQwJ-8RqI/edit?usp=sharing" rel="noopener nofollow ugc">Polkadollar Technical Specification (Google Doc)</a></strong></p>
<h4><a name="p-34638-were-seeking-feedback-on-7" class="anchor" href="#p-34638-were-seeking-feedback-on-7"></a>We’re Seeking Feedback On:</h4>
<ul>
<li>
<p>Integration feasibility with Asset Hub &amp; XCM.</p>
</li>
<li>
<p>Potential governance model for the Stablecoin Hub.</p>
</li>
<li>
<p>LST collateralization risk parameters.</p>
</li>
<li>
<p>Treasury involvement — should it seed liquidity or act as a meta-governor?</p>
</li>
<li>
<p>Preferred launch order (Factory first vs. StableAMMs first).</p>
</li>
</ul>
<hr>
<h3><a name="p-34638-closing-note-8" class="anchor" href="#p-34638-closing-note-8"></a><img src="https://emoji.discourse-cdn.com/twitter/bridge_at_night.png?v=15" title=":bridge_at_night:" class="emoji" alt=":bridge_at_night:" loading="lazy" width="20" height="20"> Closing Note</h3>
<blockquote>
<p>“The future of Polkadot DeFi is not one stablecoin — it’s a thousand interoperable ones.”</p>
</blockquote>
<p>By building <em>infrastructure, not competition</em>, Polkadot can unlock sustainable on-chain liquidity, retain ecosystem value, and create a foundation for exponential DeFi growth.</p>
<p>We invite Fellowship members, parachain teams, and Treasury delegates to review the spec and share feedback.</p>
<hr>
<h3><a name="p-34638-about-us-9" class="anchor" href="#p-34638-about-us-9"></a>About Us</h3>
<p>Chainscore Labs is a DeFi R&amp;D firm founded in 2021, we specialise in delivering composable financial models for DeFi having worked on 20+ protocols. We’re a team of PBA alumnis, W3F grantees and developers of JAM client - Tessera.</p>
<p>More at: <a href="https://chainscore.finance/en" class="inline-onebox" rel="noopener nofollow ugc">ChainScore Labs | Web3 &amp; Blockchain Development Partner</a></p>

<p>Polimec has been removed! <a class="mention" href="/u/juba.k">@Juba.K</a></p>

Juba K

<p>Clearly a much needed initiative and would love to join !</p>

<p>Every voice matters.<br>
Follow the <a href="https://polkadot.subsquare.io/referenda/1775" rel="noopener nofollow ugc">link</a> and take action - this is important.<br>
<strong>We, the independent validators, must stand united right now.</strong></p>
<p><img src="https://emoji.discourse-cdn.com/twitter/+1.png?v=14" title=":+1:" class="emoji" alt=":+1:" loading="lazy" width="20" height="20"> Likes and <img src="https://emoji.discourse-cdn.com/twitter/loudspeaker.png?v=14" title=":loudspeaker:" class="emoji" alt=":loudspeaker:" loading="lazy" width="20" height="20"> comments also matter - pay attention to who is defending the status quo.</p>
<p>We are <strong>independent validators</strong> - the very foundation of Polkadot’s vision.<br>
<img src="https://emoji.discourse-cdn.com/twitter/high_voltage.png?v=14" title=":high_voltage:" class="emoji" alt=":high_voltage:" loading="lazy" width="20" height="20"> Act now or never.</p>

<p><a class="mention" href="/u/bane">@bane</a> as for Products this will be exactly the focus for the next months. Please check out: <a href="https://www.youtube.com/watch?v=Rkoh1RnM0HM" rel="noopener nofollow ugc">https://www.youtube.com/watch?v=Rkoh1RnM0HM</a></p>
<p>Your observations are very appreciated. Thank you for sharing.</p>

<h2><a name="p-34628-polkadot-news-1" class="anchor" href="#p-34628-polkadot-news-1"></a>Polkadot News</h2>
<p>The Polkadot Technical Fellowship is reviewing the PR that suggests performing Polkadot Asset Hub migration at relay chain block number 28490502, which will be around TUESDAY 4TH NOVEMBER, 8 AM UTC. <a href="https://github.com/polkadot-fellows/runtimes/pull/984" class="inline-onebox" rel="noopener nofollow ugc">[AHM] Schedule Polkadot Migration by ggwpez · Pull Request #984 · polkadot-fellows/runtimes · GitHub</a></p>
<p>Want to know more about the Polkadot Asset Hub migration and how it is relevant for you? Here is the document put together by the support team at Web3 Foundation <a href="https://support.polkadot.network/support/solutions/articles/65000190561" class="inline-onebox" rel="noopener nofollow ugc">Polkadot Support</a></p>
<p>The Polkadot Asset Hub migration was also discussed in detail during yesterday’s  OpenDev Polkadot Fellowship Call <a href="https://x.com/Polkadot/status/1980637397810549194" rel="noopener nofollow ugc">https://x.com/Polkadot/status/1980637397810549194</a></p>
<p>The referendum requesting funding for Polkawatch, Decentralization Analytics, Infrastructure, and Maintenance 2025 is passing and now in the confirmation period <a href="https://polkadot.subsquare.io/referenda/1766" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1766</a></p>
<p>The referendum for StellaSwap Incentive Program is currently failing <a href="https://polkadot.subsquare.io/referenda/1771" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1771</a></p>
<p>Discover Road to Sub0 Polkadot Developer Party meetups in your neighbourhood! Today’s meetup at Addis Ababa Science and Technology University is sold out <a href="https://luma.com/user/Polkadot" rel="noopener nofollow ugc">https://luma.com/user/Polkadot</a></p>
<h2><a name="p-34628-kusama-news-2" class="anchor" href="#p-34628-kusama-news-2"></a>Kusama News</h2>
<p>The disruption to Kusama Validators’ Self-Stake and Rewards has been fixed and will be part of the upcoming 1.9.3 runtime upgrade on Kusama Network <a href="https://forum.polkadot.network/t/psa-disruption-to-kusama-validators-self-stake-and-rewards/15599" class="inline-onebox">PSA: Disruption To Kusama Validators' Self-Stake and Rewards</a></p>
<p>The proposal from Fusion3 requesting funding for the Solidity-XCM (Sol-XCM) project, a typed interface generator for Solidity, is currently failing <a href="https://kusama.subsquare.io/referenda/606" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/606</a></p>

Radhakrishna Dasari

Polkadot Digest 22 October 2025

<p>As per feedback on our <a href="https://polkadot.subsquare.io/referenda/1767" rel="noopener nofollow ugc">Treasury Proposal</a>, community members brought up the issue of the delay and cancel reward percentages of 2% and 5% respectively leading to very large payouts to Guardians when intervening on large referenda (we have some proposals with request amounts in the millions). When potential rewards drastically outweigh the effort involved in milestone verification and intervention, very large rewards could potentially lead to negative effects for the treasury and OpenGov.</p>
<p>As one voter put it eloquently:</p>
<blockquote>
<p>“I can easily see this degrade into nitpicking milestones and shit flinging from anonymous accounts.”</p>
</blockquote>
<p>To ensure that interests are properly aligned between Guardians and the Treasury without introducing negative side effects, we are proposing introducing maximum reward caps for both delay and cancel referenda. <strong>What cap amounts (in USD) does the community feel to be appropriate for delay and cancel rewards?</strong></p>
<p><em><strong>Example: 1k USD cap for delay, 3k USD cap for cancel</strong></em></p>
<p>The reward curve would look something like this:</p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/3/3d1b94d5fcb81fa714748a2e487a37c1be92e849.png" data-download-href="/uploads/short-url/8IAdy7ns0dFtkuPoQEBQw3xtkSt.png?dl=1" title="Screenshot 2025-10-22 at 11.03.05" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/3/3d1b94d5fcb81fa714748a2e487a37c1be92e849_2_690x284.png" alt="Screenshot 2025-10-22 at 11.03.05" data-base62-sha1="8IAdy7ns0dFtkuPoQEBQw3xtkSt" width="690" height="284" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/3/3d1b94d5fcb81fa714748a2e487a37c1be92e849_2_690x284.png, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/3/3d1b94d5fcb81fa714748a2e487a37c1be92e849.png 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/3/3d1b94d5fcb81fa714748a2e487a37c1be92e849.png 2x" data-dominant-color="F7F6F7"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">Screenshot 2025-10-22 at 11.03.05</span><span class="informations">975×402 58.8 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>
<p>Sample payout amounts with their respective rewards:</p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/b/bce7704dc96b9c9bca046ef5ebc7cb741e065b2f.png" data-download-href="/uploads/short-url/qX7CpwKY8rx09LhMZHIX0e0VdNB.png?dl=1" title="Screenshot 2025-10-22 at 11.11.05" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/b/bce7704dc96b9c9bca046ef5ebc7cb741e065b2f.png" alt="Screenshot 2025-10-22 at 11.11.05" data-base62-sha1="qX7CpwKY8rx09LhMZHIX0e0VdNB" width="412" height="341"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">Screenshot 2025-10-22 at 11.11.05</span><span class="informations">412×341 14.5 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>

<p>Thank you for posting here, Stefan!</p>
<p>As one of the core developers of ink! I want to emphasize that we had a number of meetings with Oak Security about how to best approach this audit. Oak brought a number of options to the table and after discussing them, we believe the approach from the proposal is best suited for this audit and the changes entailed from v5 to v6.</p>
<p>The proposal was reviewed by a number of people working on ink! v6, we are aligned with it and fully support it <img src="https://emoji.discourse-cdn.com/twitter/slightly_smiling_face.png?v=14" title=":slightly_smiling_face:" class="emoji" alt=":slightly_smiling_face:" loading="lazy" width="20" height="20"> .</p>

<p>Hey everyone <img src="https://emoji.discourse-cdn.com/twitter/waving_hand.png?v=14" title=":waving_hand:" class="emoji" alt=":waving_hand:" loading="lazy" width="20" height="20"></p>
<p>As some of you may know, we received a grant from the Web3 Foundation to build a taxation software for the Polkadot ecosystem.<br>
The project is still ongoing, but we’ve now completed our first two milestones <strong><img src="https://emoji.discourse-cdn.com/twitter/tada.png?v=14" title=":tada:" class="emoji only-emoji" alt=":tada:" loading="lazy" width="20" height="20"></strong> and would love to gather feedback from fellow Polkadot enthusiasts.</p>
<p>If you’re interested in trying out the app and sharing your thoughts, you can check it out here:<br>
<img src="https://emoji.discourse-cdn.com/twitter/link.png?v=14" title=":link:" class="emoji" alt=":link:" loading="lazy" width="20" height="20"> App: <a href="https://polkatax.com/" rel="noopener nofollow ugc">https://polkatax.com/</a></p>
<p><img src="https://emoji.discourse-cdn.com/twitter/memo.png?v=14" title=":memo:" class="emoji" alt=":memo:" loading="lazy" width="20" height="20"> Feedback form (~3 minutes): <a href="https://forms.gle/wvzf2KrZokf2esFM9" class="inline-onebox" rel="noopener nofollow ugc">PolkaTax Feedback Survey</a></p>
<p>Your feedback is incredibly valuable and will directly help us improve the product as we move forward.<br>
Just a quick note — the current version only supports data gathering and export for the 2024 tax year onward.</p>
<p>Thanks so much for your time and support <img src="https://emoji.discourse-cdn.com/twitter/folded_hands.png?v=14" title=":folded_hands:" class="emoji" alt=":folded_hands:" loading="lazy" width="20" height="20"></p>

Polkatax

Feedback Wanted: Polkadot Taxation Software (Web3 Foundation Grant Milestones 1 &amp; 2 Complete)

Feedback Wanted: Polkadot Taxation Software (Web3 Foundation Grant Milestones 1 & 2 Complete)

<p>Thank you very much for your response.<br>
I understand that while the Polkadot SDK release version 2509 for AHM, the Polkadot-js API will not release a specific version for AHM; it is sufficient to keep it updated to the latest version.</p>

Makkan

Joyce Siqueira

Asset Hub Migration 2025

<p>Once we have the fix in place, we can do a back of an envelope calculation and tip all of them. I am for now encouraging others to look into it, hopefully one community member will pick this up and calculate it. If not, I will do it myself <img src="https://emoji.discourse-cdn.com/twitter/handshake.png?v=14" title=":handshake:" class="emoji" alt=":handshake:" loading="lazy" width="20" height="20"></p>

Kian Paimani

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

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

<h2><a name="p-34610-polkadot-news-1" class="anchor" href="#p-34610-polkadot-news-1"></a>Polkadot News</h2>
<p>Earlier this month, Web3 Foundation updated guidelines for its grants program with emphasis on user-centric innovation, to strengthen the Polkadot economy <a href="https://medium.com/web3foundation/new-w3f-grant-guidelines-b2c921a84850" class="inline-onebox" rel="noopener nofollow ugc">New Grant Guidelines. At the Web3 Foundation, we’re… | by Web3 Foundation Team | Web3 Foundation | Oct, 2025 | Medium</a></p>
<p>Today, the Polkadot Builder Party Hackathon features a session on “Web2 to Web3—Rapid Digital Asset (SmartNFT) Deployment With Unique SDK.” Tune in here: <a href="https://www.youtube.com/watch?v=KiDRg8ug6Vc" rel="noopener nofollow ugc">https://www.youtube.com/watch?v=KiDRg8ug6Vc</a></p>
<p>The treasury proposal: ink! Alliance — Enabling Rust Smart Contracts and Developer Growth on Polkadot Hub is now up for voting <a href="https://polkadot.subsquare.io/referenda/1773" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1773</a></p>
<p>After receiving feedback from the community, Entropretty requests to cancel the current referendum and will post an updated proposal on the Web3 Citizenship incentive plan soon <a href="https://polkadot.subsquare.io/referenda/1770" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1770</a></p>
<p>The referendum to cancel the referendum 1770 to clear the Polkadot Root track is now up for voting <a href="https://polkadot.subsquare.io/referenda/1774" class="inline-onebox" rel="noopener nofollow ugc">Cancel #1770 to clear the root track</a></p>
<h2><a name="p-34610-kusama-news-2" class="anchor" href="#p-34610-kusama-news-2"></a>Kusama News</h2>
<p>The proposal from Fusion3 requesting funding for the Solidity-XCM (Sol-XCM) project, a typed interface generator for Solidity, is currently failing <a href="https://kusama.subsquare.io/referenda/606" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/606</a></p>

Polkadot Digest 21 Oct 2025

<p>Thanks for raising this!  We actually analyze these trends promptly as they happen (for example, we reached out to Neuroweb back in January 2025 to get confirmation of the drop), but your post is a good reminder that we should also share our findings more proactively with the community here, not just verify for the dashboards accuracy sake.</p>
<p>In Neuroweb’s case, the decrease was confirmed by the team to be due to protocol-level <a href="https://docs.origintrail.io/useful-resources/previous-updates/dkg-v8.0-update-guidebook/protocol-updates" rel="noopener nofollow ugc">changes</a> (DKG v8 and batch minting), which made on-chain activity more efficient and less transaction-heavy - not an actual decline in usage.</p>
<p>For Frequency, our team analyzed activity across all pallets and confirmed that the drop wasn’t due to data ingestion or decoding issues. The decline appears genuine on-chain, as event counts fell sharply across all pallets around September 9–10. We’ve reached out to the Frequency team for clarification on whether this reflects an intentional protocol change or a temporary drop in activity, but with no response. If the Frequency team is here, we would appreciate their help in figuring this out.</p>
<p>For Frequency, in the queries for the data parity website, we are using <code>statefulStorage</code> for the proxy activity, but there isn’t any other pallet that the activity has moved to. All pallets seem to be showing a big decrease in activity:</p>
<pre><code class="lang-auto">pallet      capacity  handles  messages   msa  statefulStorage  system  utility
date                                                                           
2025-09-06    221137     1782      8072  3146           189596  245602   389799
2025-09-07    230959     1832      8140  3209           197473  255557   407508
2025-09-08    234182     1948      8187  3357           200212  259000   413415
2025-09-09     95753      614      8160  1062            68975  120482   141537
2025-09-10     31836       11      8592    29             6367   56992    12733
2025-09-11     68258       44     21076    90                0  130020      132
2025-09-12     27033       12      8575    24                0   51975       36
2025-09-13     26901       10      8031    22                0   51285       30
2025-09-14     26727        7      8267    16                0   51183       25
2025-09-15     26898       19      9253    39                0   52431       57
2025-09-16     21682       18      7038    40                0   46491       56
2025-09-17      4268       15       236    30                0   28720       45
2025-09-18     25632        6       961    16                0   49717       18
2025-09-19     41088       16      3824    32                0   88752       54
2025-09-20     29562        5      1348    10                0   66430       15
2025-09-21     37274       12      1790    24                0   85354       36
2025-09-22     20909       16       968    32                0   44919       48

</code></pre>

Pavla | Data @ Parity

What happened to Frequency&rsquo;s active accounts?

What happened to Frequency's active accounts?

<aside class="quote no-group" data-username="Maxx" data-post="3" data-topic="15416">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/48.png" class="avatar"> Maxx:</div>
<blockquote>
<p>It’s just too bad that these features aren’t built into the main wallet dapps themselves, and we have to rely on 3rd Party dapps to initiate transfers such as these, especially between two interconnected networks?</p>
</blockquote>
</aside>
<p>Vitalik has been saying stuff around these lines as well, wallet providers should integrate tools such as shield.markets, but requires the wallet provider to maintain it..  We have great tech to do cross chain transfers(snowbridge) it just requires more than a balance transfer transaction… But since the ethereum proxy will stable soonish, you should be able to use any EVM compatible wallet with it. I think its good that we have lots of different dapps by different independent teams that can make custom transactions depending on there usecase. I think most projects just integrate wallet connect(<a href="https://walletconnect.com/" rel="noopener nofollow ugc">https://walletconnect.com/</a>) and call it a day, is wallet connect supporting your wallet?</p>

<aside class="quote no-group" data-username="Gr33nHatt3R" data-post="8" data-topic="11971">
<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/gr33nhatt3r/60/5530_2.png" class="avatar"> Gr33nHatt3R:</div>
<blockquote>
<p>Do we know when collators and parachain runtimes will upgrade to the Polkadot SDK version 2509?</p>
</blockquote>
</aside>
<p>We are already working to upgrade AH to ES on testnets  (Westend, Paseo), then Kusama and Polkadot after the migration.</p>

Andrei Sandu

Jonathan

Elastic Scaling - wen 500ms blocks

<aside class="quote no-group" data-username="sinzii" data-post="2" data-topic="15555" data-full="true">
<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/sinzii/48/6947_2.png" class="avatar"> sinzii:</div>
<blockquote>
<p>Super excited to see the Staking Dashboard coming back with more exciting new proposed features and changes. I’m looking forward to all the updates, especially the liquid staking support and the expansion to the Paseo testnet and Vara network. LFG!</p>
</blockquote>
</aside>
<p>Thanks for the support Thang! We aim to maintain the dashboard as a flagship Dedot implementation and I believe this proposal gives the product enough relevancy and new features to really push Dedot as much as we can.</p>
<p>We decided to go all out with this proposal in terms of onboarding DeFi features users will find useful, and in the process remove the friction of having to bounce around numerous applications to get one job done.  Our approach is calculated and focused on key features rather than throwing everything at the wall - this is evident with our initial focus on stablecoins and rolling out a DeFi feature-set that will benefit the most users in the ecosystem.</p>
<p>What I find exciting is that, if passed, the dashboard can evolve from a staking solution to a more robust DeFi solution. It will be a gateway into Polkadot DeFi with the simple UI it is known for, rather than just a gateway into DOT staking. I see this as is a huge opportunity to expand the platform. Smart contracts on AssetHub will play a role in the evolution of Polkadot DeFi, and this will pick up pace as soon as they are deployed on Polkadot Asset Hub. We want to position the dashboard to be able to onboard contract-based features too, with advanced mode being the ideal place for such features.</p>
<p>We’ve calculated every action item on this proposal to fit with the future evolution of AssetHub and staking, and we’re confident the dashboard can grow exponentially in terms of both traffic and relevancy with these proposed upgrades - and Dedot plays a huge part in making that happen.</p>
<aside class="quote no-group" data-username="muddlebee" data-post="3" data-topic="15555">
<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/muddlebee/48/9730_2.png" class="avatar"> muddlebee:</div>
<blockquote>
<p>Lovely. Excited for this.<br>
Going forward can we expect some sort of cross chain liquidity aggregator? which finds the best yields across the ecosystem?</p>
</blockquote>
</aside>
<p>Thank you Muddlebee, your support is always hugely appreciated! Exploring liquidity aggregation tooling would be a massive advanced mode feature I’d personally love to see in the dashboard. Solutions will likely be hybrid - both protocol and UI - where contracts can play the part of providing yield strategies on behalf of users and execute them, and the UI can mine various protocol statistics and provide more manual gateways.</p>
<p>Like I mentioned with Thang, this opens up the dashboard from staking-only to a more robust DeFi finance product. It may even warrant a rebrand to <code>earn.polkadot.cloud</code> or something along those lines, but this is more of a medium-term consideration. We firstly need to get funding  - then it is full steam ahead.</p>
<p>I am curious to hear <a class="mention" href="/u/bill_w3f">@bill_w3f</a> opinions relating to this direction. By expanding DeFi tooling, we morph into a singular, seamless gateway for a range of DeFi features. Rather than having one Dapp for one protocol (E.g. one for Bifrost, one for Hydration, etc), we see the dashboard supporting numerous protocols, where warranted, on a per-feature basis. No bias towards which to use, but rather allowing features and user-demand to dictate which ones we integrate.</p>

Ross Bulat

Keep the Staking Dashboard Growing — Your Flagship Gateway to Staking &amp; DeFi

Keep the Staking Dashboard Growing — Your Flagship Gateway to Staking & DeFi

<h2><a name="p-34584-polkadot-news-1" class="anchor" href="#p-34584-polkadot-news-1"></a>Polkadot News</h2>
<p>Polkadot Builder Party Hackathon now has 1800+ registrations. This week features talks on digital assets, everything about Polkadot testnets, and building projects that matter. More info here: <a href="https://polkadot.devpost.com/" rel="noopener nofollow ugc">https://polkadot.devpost.com/</a></p>
<p>Missed attending Polkadot Builder party sessions and workshops? Here is the full playlist of past and upcoming talks <a href="https://www.youtube.com/playlist?list=PLOyWqupZ-WGvx3e73tc4gYObf0rJ4UV1X" rel="noopener nofollow ugc">https://www.youtube.com/playlist?list=PLOyWqupZ-WGvx3e73tc4gYObf0rJ4UV1X</a></p>
<p>The referendum requesting funding for Polkadot Staking Dashboard: Improvements, Upgrades &amp; DeFi Integration is now up for voting <a href="https://polkadot.subsquare.io/referenda/1772" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1772</a></p>
<p>The referendum for StellaSwap Incentive Program is now up for voting <a href="https://polkadot.subsquare.io/referenda/1771" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1771</a></p>
<h2><a name="p-34584-kusama-news-2" class="anchor" href="#p-34584-kusama-news-2"></a>Kusama News</h2>
<p>The Runtime Upgrade 1.9.2 performing post-migration cleanup on Kusama Hub has been executed successfully <a href="https://kusama.subsquare.io/referenda/607?tab=timeline" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/607?tab=timeline</a></p>
<p>The funding request to implement MVP for Kusama forum, powered by an on-demand parachain which uses KSM as its native token, has been approved <a href="https://kusama.subsquare.io/referenda/603" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/603</a></p>
<p>The proposal from Fusion3 requesting funding for Solidity-XCM (Sol-XCM) project, a typed interface generator for Solidity is currently failing <a href="https://kusama.subsquare.io/referenda/606" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/606</a></p>

Polkadot Digest 20 Oct 2025

<p>What’s truly baffling is that despite Polkadot’s massive spending on marketing, the results have been remarkably poor. As far back as two years ago, media outlets exposed Polkadot’s pattern of high investment with low returns, and they were widely ridiculed for it.</p>
<p>Two years later, this behavior still hasn’t been effectively addressed. As an early holder of DOT, I’ve watched the price plummet from $50 to the current $3—a staggering 90%+ drop.</p>
<p>It’s deeply disheartening to see the team continue to ignore the token price issue and persist in doing things their own way.</p>

Jose NoName

Concerns about WagMedia

<p>Thanks for engaging in this conversation, <a class="mention" href="/u/sinzii">@sinzii</a>!</p>
<aside class="quote no-group" data-username="sinzii" data-post="16" data-topic="15468">
<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/sinzii/48/6947_2.png" class="avatar"> sinzii:</div>
<blockquote>
<p>The memory consumption difference here is mostly due to caching, where we sacrifice memory to gain data availability for operations and calls that are done repetitively.</p>
</blockquote>
</aside>
<p>This is incorrect. PAPI also caches and reuses data so repeated operations are served from cache. The primary reason PAPI performs better in the benchmark is simpler: <strong>Dedot repeatedly downloads metadata for all historical blocks</strong>, whereas PAPI only fetches metadata when needed. When we hit a block that’s not connected to the tip, we first check whether we already have its metadata and avoid redundant downloads. Re-downloading metadata every time an operation targets an old block, as Dedot currently does, incurs substantial overhead, which your own benchmark highlights.</p>
<p>If it helps, feel free to port the PAPI approach, or ask follow-ups about our strategy for avoiding unnecessary metadata fetches. Let’s fix the root cause rather than inventing a non-existing “memory for availability” trade-off.</p>
<aside class="quote no-group" data-username="sinzii" data-post="16" data-topic="15468">
<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/sinzii/48/6947_2.png" class="avatar"> sinzii:</div>
<blockquote>
<p>There is no right or wrong here — what we have chosen is a balance.</p>
</blockquote>
</aside>
<p>Choosing to download additional data that isn’t needed, slowing things down and increasing memory pressure, doesn’t look like a good balance from a performance standpoint.</p>
<aside class="quote no-group" data-username="sinzii" data-post="16" data-topic="15468">
<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/sinzii/48/6947_2.png" class="avatar"> sinzii:</div>
<blockquote>
<p>developers never need to clear the cache manually</p>
</blockquote>
</aside>
<p>If that were strictly true, there wouldn’t be a public <a href="https://github.com/dedotdev/dedot/blob/1252671f59eeff8f17b2280a8b13925024191438/packages/api/src/client/DedotClient.ts#L203-L210" rel="noopener nofollow ugc"><code>clearCache</code> API</a>.</p>
<aside class="quote no-group" data-username="sinzii" data-post="16" data-topic="15468">
<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/sinzii/48/6947_2.png" class="avatar"> sinzii:</div>
<blockquote>
<p>PJS signer interface is the most well-adopted signing interface in the ecosystem, and I don’t understand why you’re criticizing supporting it even though PAPI still support it in the first place.</p>
</blockquote>
</aside>
<p>To clarify: I’m <strong>not</strong> criticizing supporting it; I’m criticizing <strong>adopting it as Dedot’s own public signing interface</strong>. That cements long-known limitations: difficulty creating extrinsics for modern chains, heavier signers, and awkwardness around custom signed-extensions, among others. Supporting legacy interfaces for compatibility is fine; elevating them to your primary public surface is a missed opportunity for a “modern” library.</p>
<aside class="quote no-group" data-username="sinzii" data-post="16" data-topic="15468">
<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/sinzii/48/6947_2.png" class="avatar"> sinzii:</div>
<blockquote>
<p>I bet the original author would never have been able to imagine how Polkadot would evolve in the future when designing the first version of the interface</p>
</blockquote>
</aside>
<p>Exactly. Which is why modern libraries should converge on <strong>better, interoperable</strong> interfaces rather than re-entrench old ones.</p>
<aside class="quote no-group" data-username="sinzii" data-post="16" data-topic="15468">
<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/sinzii/48/6947_2.png" class="avatar"> sinzii:</div>
<blockquote>
<p>what we have to do is continue improving it.</p>
</blockquote>
</aside>
<p>Agreed! That’s <a href="https://forum.polkadot.network/t/toward-an-interoperable-transaction-interface-introducing-createtransaction/15060">what we’re doing</a>. It would be great to see Dedot decouple from the PJS signer interface and join this work.</p>
<aside class="quote no-group" data-username="sinzii" data-post="16" data-topic="15468">
<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/sinzii/48/6947_2.png" class="avatar"> sinzii:</div>
<blockquote>
<p>We started Dedot without awareness of the new JSON-RPC specs</p>
</blockquote>
</aside>
<p>The <a href="https://forum.polkadot.network/t/new-json-rpc-api-mega-q-a/3048">new JSON-RPC API mega Q&amp;A</a> came out a few months before Dedot’s development started, alongside with other posts and public discussions. Library authors have a responsibility to track and leverage upstream changes, precisely to avoid repeating past mistakes.</p>
<aside class="quote no-group" data-username="sinzii" data-post="16" data-topic="15468">
<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/sinzii/48/6947_2.png" class="avatar"> sinzii:</div>
<blockquote>
<p><a href="https://github.com/dedotdev/dedot/blob/1252671f59eeff8f17b2280a8b13925024191438/packages/providers/src/types.ts#L38-L74" rel="noopener nofollow ugc">The interface</a> is simple, with methods to send requests, subscribe, connect, and disconnect from the network</p>
</blockquote>
</aside>
<p>It’s more opinionated than it appears, which makes it <strong>non-interoperable</strong> and coupled to Dedot internals. Neither generic JSON-RPC nor the modern Polkadot JSON-RPC define a standard “subscribe” primitive; subscriptions are conventions built on notifications. Returning a <code>Promise</code> from your <code>subscribe</code> function also leaks an implementation detail about how Dedot internally manages subscriptions.</p>
<p>By contrast, the <a href="https://github.com/polkadot-api/polkadot-api/blob/ad5615339b6c2be1696eeb5af7ad3d26fdf74e99/packages/json-rpc/json-rpc-provider/src/index.ts" rel="noopener nofollow ugc">JSON-RPC interface we proposed</a> is deliberately minimal and library-agnostic. Smoldot’s <a href="https://github.com/smol-dot/smoldot/blob/98c41cd95128dd8a9de09917bb2017ea8c259d52/wasm-node/javascript/src/public-types.ts#L127-L219" rel="noopener nofollow ugc">public interface for Chains</a> is another interoperable example. You can translate between smoldot’s and PAPI’s easily (because they are both interoperable).</p>
<p>In fact, we could use any PAPI provider with Dedot’s modern client by “impersonating” a smoldot chain. The reverse isn’t feasible with Dedot’s current provider API.</p>
<p>If you don’t like PAPI’s interface, proposing a simpler/better interoperable one (or adopting smoldot’s) would still be a win. We’re not fully satisfied with smoldot’s because disconnects require rejecting the latest <code>Promise</code>, it limits synchronous message bursts, and it’s harder to ensure consumers drain all yielded promises. Even so, we’d be willing to compromise on it.</p>
<aside class="quote no-group" data-username="sinzii" data-post="16" data-topic="15468">
<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/sinzii/48/6947_2.png" class="avatar"> sinzii:</div>
<blockquote>
<p>While the two clients have different implementations, they both share <a href="https://github.com/dedotdev/dedot/blob/1252671f59eeff8f17b2280a8b13925024191438/packages/api/src/types.ts#L113-L150" rel="noopener nofollow ugc">the same generic interface</a>, and therefore they both expose a common set of APIs for on-chain interactions.</p>
</blockquote>
</aside>
<p>This interface is missing several strengths the modern JSON-RPC provides: subscribing to all finalized blocks, tracking current best blocks, automatic recovery across reconnections, etc.</p>
<p>And practically speaking, the modern client isn’t usable with Dedot today. As I wrote above:</p>
<aside class="quote no-group" data-username="josep" data-post="1" data-topic="15468">
<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/josep/48/2619_2.png" class="avatar"> josep:</div>
<blockquote>
<p>the modern client is hard to use because several endpoints aren’t fully compliant with the modern JSON‑RPC spec. Instead of using generic middlewares (like those PAPI provides) to bridge gaps, Dedot delivers a broken DX on the modern client. Everyone ends up on the legacy client, which can’t offer the guarantees modern APIs provide. This cements legacy usage while still failing to offer minimum guarantees.</p>
</blockquote>
</aside>
<p>This is exactly how a “modern” library inadvertently reinforces legacy JSON-RPC usage. Offering two clients, where one works and the other doesn’t, pushes users toward the legacy path. This is a solved problem: you can deliver a solid DX on the modern client.</p>
<aside class="quote no-group" data-username="sinzii" data-post="16" data-topic="15468">
<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/sinzii/48/6947_2.png" class="avatar"> sinzii:</div>
<blockquote>
<p>Dedot will never throw this behavior when a dapps interact with an unknown on-chain APIs.</p>
</blockquote>
</aside>
<p>It will. A recent example: at Polkadot People block-height <strong>2188447</strong>, the structure of the <code>Identity.IdentityOf</code> storage-value changed. Dedot can’t detect these structural changes on runtime upgrades on the fly. Without a compatibility API, tools like <a href="https://diff.papi.how" rel="noopener nofollow ugc">https://diff.papi.how</a> aren’t achievable. We’ve explained this in multiple places; denying it doesn’t make the limitation go away.</p>
<aside class="quote no-group" data-username="sinzii" data-post="16" data-topic="15468">
<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/sinzii/48/6947_2.png" class="avatar"> sinzii:</div>
<blockquote>
<p>The question now is which standard to pick and how to make it work with both libraries</p>
</blockquote>
</aside>
<p>Regarding the JSON-RPC Provider. We propose using a <a href="https://github.com/polkadot-api/polkadot-api/blob/ad5615339b6c2be1696eeb5af7ad3d26fdf74e99/packages/json-rpc/json-rpc-provider/src/index.ts" rel="noopener nofollow ugc">super simple and minimalistic API</a>, although for v2 we have realized that it’s slightly better if the payloads are <a href="https://github.com/polkadot-api/polkadot-api/blob/37ed0f0590225e5e7a4a45943027ee2e12452f39/packages/json-rpc/json-rpc-provider/src/index.ts#L1-L37" rel="noopener nofollow ugc">actually parsed</a>, which is better for performance. They are essentially the same, though.</p>
<p>We’re open to either, or to a third option, so long as it’s simple, performant, and <strong>decoupled from any single library’s internals</strong>.</p>
<aside class="quote no-group" data-username="sinzii" data-post="16" data-topic="15468">
<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/sinzii/48/6947_2.png" class="avatar"> sinzii:</div>
<blockquote>
<p>Even though PJS is in maintenance mode, something like the signer interface still needs to reach agreement within the community before we move forward.</p>
</blockquote>
</aside>
<p>That agreement exists. The new interface we proposed <a href="https://github.com/polkadot-js/api/issues/6213#issuecomment-3400231241" rel="noopener nofollow ugc">is being added into PJS</a>.</p>

<p>Who will now inform the community about the development progress?</p>

Birdo

Polkadot Mobile App Updates

<p>Centralising the demand-supply job market matching promotes deeper inefficiencies given the market structure I’ve been addressing for some time now in the forum, i.e. highly concentrated economy.</p>
<p>Actually, my understanding is that the job opportunity matching is already centralised around the PBA and related efforts, distracting the educational efforts into job seeking more than knowledge pursue and innovation. My partners at the PBA can be witnesses on this fact.</p>
<p>I advocate on free markets for strong political reasoning based on real world observation on how free markets contribute to market efficiencies. The main condition for a free market to work efficiently is distribution of operations and revenue taking participants. If this conditions are not met, the job market will continue operating in a centralised way with all the inefficiencies you are just describing. In this sense, I don’t think it is accurate there has been lacking centralisation of the job matching market, actually the contrary and I don’t believe there are good reasons it should continue this way from the economical efficiency perspective, specially with Parity taking over the strong operative arm for Polkadot development with this next recent management change, the reelected CEO.</p>

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

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

PolkArena: Revolutionizing Events for the Polkadot Era

- Sol-XCM is a tool for Solidity contracts.
- It helps contracts talk to other parts of the ecosystem.
- Contracts can be used on Kusama Hub and soon on Polkadot Hub.
- It makes contracts work together easily.
- This is special because it lets contracts connect with many different systems.
- The main goal is to make contracts more connected.
- It focuses on making communication simple and useful.

Deciding

Executed

Runtime Upgrade 1.9.2 (again)

- Polkadot Nigeria wants to help small businesses in Nigeria use Kusama blockchain
- Nigeria has millions of small businesses but very few use blockchain technology
- They plan to bring 6 businesses into the Kusama ecosystem
- These businesses will be from farming, delivery, healthcare, and money sectors
- They will work with government agencies and other partners
- The project will create tools and training for businesses
- They have already helped many people learn about Polkadot before
- They are asking for 2,800 KSM to make this happen

TimedOut

Enterprise Adoption & Institutional Collaborations for Kusama in Nigeria

- This is a plan to build a special website for the Kusama community.
- It will be a place where people can talk and share ideas.
- The website will be built using blockchain technology.
- It will be different from regular websites because no one company controls it.
- People will be able to post messages, pictures, and comments.
- The creator has built similar websites before.
- It will be ready by the end of 2025.
- This helps Kusama by giving it its own special place online.

Here's a simple summary of Referendum Alert:

- It's a free Telegram bot for Kusama and Polkadot
- Sends instant alerts when people vote on proposals
- Shows who voted and how they voted
- Works in private chats and group chats
- Now shows people's names if they have them set up
- Plans to make daily vote summaries
- Will group alerts to avoid too many messages
- Helps people follow governance decisions easily

Rejected

Referendum Alert: Real-Time OpenGov Vote Notifications on Telegram

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

treasury18

discussions1388