candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

The Kus Public Review &amp; AMA: 2022 - 2025

Andrey McQ

The Kus Public Review & AMA: 2022 - 2025

AAG 2.0 for the Second Age of Polkadot

RocoDotcast

Looking for guidance and funding support to build a verified global services platform on Polkadot

<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

Forum Anonimity and Gov Research

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

Tech Talk

Subctl: Looking for feedback on a new CLI tool

Experimenting with Homomorphic Encryption on PVM

Bastian Köcher

Runtime release notification for v2.0.5 [15.01.2026]

Anaelle LTD

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

Governance

RFC-0162 (PR #162): Ecosystem Anti-Trust &amp; Market Structure Omnibus — Review Thread

Diego

RFC-0162 (PR #162): Ecosystem Anti-Trust & Market Structure Omnibus — Review Thread

Decentralized Voices Cohort 5 Application - Light Track: GoverNoun AI Governance Agent

Luke

[WFC] Burn-Based Tokenomics for Kusama: The Ethereum Model, Not a Hard Cap

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

Ecosystem

Mimir Sunset Announcement

Mike

Decentralised Identifiers (DIDs)

Chris T

Polkadot Branding Kit

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

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>Thanks Karim — really appreciate the detailed feedback and the comparison to cast, that’s exactly the niche I’m aiming for.</p>
<p>Polkadot Vault — Love this idea. Displaying QR in terminal is straightforward, but scanning the signed response back is the tricky part — camera access doesn’t work in many CLI environments (SSH, headless). Multiframe animated QR for larger payloads adds another layer of complexity. Likely approach: QR display + hex paste fallback. Definitely on the radar, just need to figure out a solution that works universally.</p>
<p>Generic extrinsic builder — Great suggestion, and yes absolutely open to a PR. A subxt 0.50 refactor is coming once it hits stable — I’ll post here when that’s done, would love to collaborate after that.</p>
<p>GitHub mirror — Appreciate the suggestion. Staying Codeberg-only for now as part of the decentralization ethos, but may revisit.</p>

Karim | Product Engineering @ Parity

<p>I understand the current narrative and the direction that is being taken. I also understand that Parity has assumed a central role in development and that W3F, as the largest stakeholder, naturally has significant influence over the treasury.</p>
<p>That said, I believe that discontinuing many of the products designed to simplify the experience for non-technical users carries some risk. These tools have played an important role in onboarding and usability, and removing them may unintentionally set the ecosystem back to a stage where Polkadot.js was essentially the only viable option for users.</p>
<p>Papi could eventually become a strong alternative, but at the moment it is still not sufficiently user-friendly and remains primarily focused on developers.</p>
<p>I have great respect for the Mimir team, and I genuinely consider their multisig application to be among the best ever built. For this reason, it is unfortunate that community feedback does not always seem to be fully reflected in decision-making. This is not meant as criticism, but rather as an observation from within the ecosystem.</p>

Gaius_sama - Astar Network

<aside class="quote no-group" data-username="burdges" data-post="6" data-topic="16674">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/burdges/60/172_2.png" class="avatar"> burdges:</div>
<blockquote>
<p>It’s painful since this digs deep into the FRAME macros, but so does NOMT integration. Rob H warned against those macros from early on. And sure enough they have chased away most teams who try building anything advanced. We could bit-the-bullet write a macro-free alternative for FRAME of course.</p>
</blockquote>
</aside>
<p>FRAME is operating on a key/value storage and doesn’t care about the underlying merkle tree.</p>

<p>I would like to share a deconstruction of the impact surface of this RFC-0162 for clarifying purposes, as exposed in the <a href="https://github.com/polkadot-fellows/RFCs/pull/162#issuecomment-3764315631" rel="noopener nofollow ugc">Github thread</a>.<br>
⸻<br>
The market, specially under decentralized economies, is holistically interdependent. This RFC-0162 treats the ecosystemic threat on institutional capture, given by the market structure (the rules of the game), within three consecutive PRs coordinated together as an Omnibus, an indivisible package of reforms on the whole structure.</p>
<p>With “RFC-0162: The Ecosystem Anti-Trust &amp; Market Structure Omnibus” we are proposing a single, comprehensive act to engineer fair competition and prevent institutional capture across the entire Polkadot protocol design.</p>
<p>This is the minimal mapping from RFC-0162’s threat model to concrete amendment points + engineering invariants; if anyone sees a better anchor for any node, I’m happy to revise the references accordingly:</p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/a/aa1e150047372f004b7d183fdd64e89b570ea436.png" data-download-href="/uploads/short-url/ogVCsYg2oioTrwo4FZ36VlRRECq.png?dl=1" title="Screenshot 2026-01-19 at 1.02.55 PM" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/a/aa1e150047372f004b7d183fdd64e89b570ea436_2_449x500.png" alt="Screenshot 2026-01-19 at 1.02.55 PM" data-base62-sha1="ogVCsYg2oioTrwo4FZ36VlRRECq" width="449" height="500" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/a/aa1e150047372f004b7d183fdd64e89b570ea436_2_449x500.png, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/a/aa1e150047372f004b7d183fdd64e89b570ea436_2_673x750.png 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/a/aa1e150047372f004b7d183fdd64e89b570ea436.png 2x" data-dominant-color="2D2E2F"><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 2026-01-19 at 1.02.55 PM</span><span class="informations">697×775 69.6 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><br>
(Mermaid diagram available at the <a href="https://github.com/polkadot-fellows/RFCs/pull/162#issuecomment-3764315631" rel="noopener nofollow ugc">Github thread</a>)</p>
<p>⸻</p>
<p>Column 1: THREATS (The Risk)</p>
<p>Mapped to §2 (Motivation) and §3 (Threat Model).</p>
<div class="md-table">
<table>
<thead>
<tr>
<th>Chart Node</th>
<th>RFC Text Reference</th>
<th>Context in RFC</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>F1: Contestability</strong><br>(Entrenchment)</td>
<td><strong>§2 Motivation</strong><br> <strong>§3 Threat Model</strong></td>
<td>Capture via <strong>incumbency entrenchment</strong> and <strong>monopolizing scarce resources (coretime)</strong>.</td>
</tr>
<tr>
<td><strong>F2: Neutrality</strong><br>(Discrimination)</td>
<td><strong>§6.2 Definition</strong><br><strong>§7.3 Amendment A</strong></td>
<td>“Discrimination” = inclusion/exclusion by <strong>non-validity attributes</strong>; neutrality is normed as <strong>common-carrier</strong>, with <strong>validity predicates only</strong> as exceptions (§6.1).</td>
</tr>
<tr>
<td><strong>F3: Portability</strong><br>(Data Lock-in)</td>
<td><strong>§6.5 Definition</strong><br><strong>§7.4, §7.6</strong></td>
<td>“Portability” = <strong>proof-carrying export</strong> (light-client verifiable); reinforced by <strong>multi-source metadata resilience</strong>.</td>
</tr>
<tr>
<td><strong>F4: Exit Rights</strong><br>(Jamming / Lock-in)</td>
<td><strong>§3 Threat Model</strong><br><strong>§7.8 Amendment</strong></td>
<td>Adversary “dominates exit capacity”; mitigated by <strong>rule-based queue ordering</strong> + <strong>per-controller rate limits</strong>.</td>
</tr>
</tbody>
</table>
</div><p>⸻</p>
<p>Column 2: RAILS (The Target)</p>
<p>Mapped to the specific RFCs being amended in §7 (Specification).</p>
<div class="md-table">
<table>
<thead>
<tr>
<th>Chart Node</th>
<th>Target System</th>
<th>RFC Text Reference</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>CT: Coretime Market</strong></td>
<td><strong>RFC-0149</strong></td>
<td><strong>§7.7</strong> (Anti-hoarding invariants; re-entry events + concentration friction).</td>
</tr>
<tr>
<td><strong>GOV: Governance Rail</strong></td>
<td><strong>RFC-0032</strong></td>
<td><strong>§7.3</strong> (Canonical utility state neutrality; validity-only inclusion).</td>
</tr>
<tr>
<td><strong>EXIT: Staking/Unbond</strong></td>
<td><strong>RFC-0097</strong></td>
<td><strong>§7.8</strong> (Exit neutrality + anti-jamming constraints).</td>
</tr>
<tr>
<td><strong>COL: Collator Selection</strong></td>
<td><strong>RFC-0007</strong></td>
<td><strong>§7.9</strong> (Sunsetting invulnerables; rule-based replacement + liveness safety).</td>
</tr>
<tr>
<td><strong>ID: Identity System</strong></td>
<td><strong>RFC-0032</strong></td>
<td><strong>§7.4–§7.5</strong> (Proof-carrying export; multi-attestation compatibility).</td>
</tr>
<tr>
<td><strong>MD: Metadata Rail</strong></td>
<td><strong>RFC-0078</strong></td>
<td><strong>§7.6</strong> (Anti-registry capture; multi-source resilience).</td>
</tr>
</tbody>
</table>
</div><p>⸻</p>
<p>Column 3: FIX (The Norms)</p>
<p>Mapped to the engineering invariants defined in §7 (Specification).</p>
<div class="md-table">
<table>
<thead>
<tr>
<th>Chart Node</th>
<th>RFC Text Reference</th>
<th>The Constitutional Norm</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>I1: Contestability</strong><br>(Forced Re-entry + Sunset Privilege)</td>
<td><strong>§7.7.1</strong>; <strong>§7.9</strong></td>
<td><strong>Periodic contestability:</strong> renewed coretime can be forced back into competition; discretionary privilege must be <strong>time-bounded</strong> and replaced by rule-based mechanisms.</td>
</tr>
<tr>
<td><strong>I2: Neutrality</strong><br>(Validity Only)</td>
<td><strong>§7.3</strong>; <strong>§6.1–§6.2</strong></td>
<td><strong>Common Carrier</strong> for canonical utility state: no discrimination beyond <strong>validity predicates</strong>.</td>
</tr>
<tr>
<td><strong>I3: Portability</strong><br>(Proof Export + Multi-Source)</td>
<td><strong>§7.4</strong>; <strong>§7.6</strong>; <strong>§6.5</strong></td>
<td><strong>Verifiable export</strong> + <strong>multi-source retrieval</strong> validated against on-chain commitments.</td>
</tr>
<tr>
<td><strong>I4: Rule-Based Exit</strong><br>(Ordering + Per-Controller Rate Limits)</td>
<td><strong>§7.8.1</strong>; <strong>§7.8.2</strong></td>
<td>Unbonding must be <strong>purely rule-based</strong>, with <strong>per-controller caps</strong> and <strong>order-preserving carry-over</strong> (no privileged fast lanes).</td>
</tr>
</tbody>
</table>
</div><br>
Last but not least, this roadmap starts by patching 0000-template.md, immediately enforcing market security considerations as a review standard for all subsequent RFCs.

<p>This kind of thing would/should have been the killer app. Thanks for your input.</p>

Kacper Szarkiewicz

<p>No rebranding of the forum logo by the way <img src="https://emoji.discourse-cdn.com/twitter/grimacing.png?v=15" title=":grimacing:" class="emoji" alt=":grimacing:" loading="lazy" width="20" height="20"> ?</p>

<p>They clearly replied they don’t want anyone to speak on their behalf, which cannot be avoided in public media like X. It feels like more a deliberate action unfortunately.</p>
<p>But It’s just how media works, your words are repeated. <img src="https://emoji.discourse-cdn.com/twitter/man_shrugging/2.png?v=15" title=":man_shrugging:t2:" class="emoji" alt=":man_shrugging:t2:" loading="lazy" width="20" height="20"></p>
<p>So no, their reply is definitely confusing about their “censorship” intents.</p>
<p>A brief apology would have probably been better rather than trying to make up weird explanations which are adding confusion on top of the confusion.</p>
<p>Anyway, i think the Community doesn’t need this currently. Let just the people speak as long as these are not insults and attacks.</p>
<p>Cheers <img src="https://emoji.discourse-cdn.com/twitter/clinking_beer_mugs.png?v=15" title=":clinking_beer_mugs:" class="emoji" alt=":clinking_beer_mugs:" loading="lazy" width="20" height="20"></p>

bill_w3f

Concerns about the ecosystem&rsquo;s social networks

Concerns about the ecosystem's social networks

<h2><a name="p-37225-polkadot-news-1" class="anchor" href="#p-37225-polkadot-news-1" aria-label="Heading link"></a>Polkadot News</h2>
<p>Polkadot Upgrade 2.0.5 referendum, which brings capped issuance of DOT, Solidity smart contracts, and two-second block time on the Hub, is passing unanimously <a href="https://polkadot.subsquare.io/referenda/1828" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1828</a></p>
<p>The referendum requesting funding for OmniAvavatar, building a cross-game, cross-engine, chain-agnostic digital identity layer, is now up for voting <a href="https://polkadot.subsquare.io/referenda/1830" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1830</a></p>
<p>The Polkadot APAC Hackathon Meetup Tour: Kuala Lumpur is happening at the Asia Pacific University of Technology &amp; Innovation on January 24th <a href="https://luma.com/mwk111mg" class="inline-onebox" rel="noopener nofollow ugc">The Polkadot APAC Hackathon Meetup Tour: Kuala Lumpur · Luma</a></p>
<p>Mimir Multisig wallet will freeze feature development and move into minimal maintenance mode <a href="https://forum.polkadot.network/t/mimir-sunset-announcement/16749" class="inline-onebox">Mimir Sunset Announcement</a></p>
<h2><a name="p-37225-kusama-news-2" class="anchor" href="#p-37225-kusama-news-2" aria-label="Heading link"></a>Kusama News</h2>
<p>The registrar application of <a href="http://ECHO.RE" rel="noopener nofollow ugc">ECHO.RE</a> to verify identities on the Kusama network is now up for voting <a href="https://kusama.subsquare.io/referenda/626" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/626</a></p>

Radhakrishna Dasari

Polkadot Digest 19 January 2026

<p>I know Latin America quite well, and what strikes me negatively time and again is the total ignorance of education, especially general education and language education. The whole world is learning English: China, India, Russia, Poland, Sweden, Germany, France, Italy, Portugal. Latinos who speak English are extremely rare, and they are certainly not doing themselves any favors. So instead of translating everything into Spanish, it would be better to encourage people to learn a second language. That’s really not too much to ask. Incidentally, it doesn’t make sense to focus on poor continents. As mentioned, there is a language barrier in Latin America, electronic devices are much more expensive due to corruption, staff are much less well trained, and work ethic is abysmal. It would be better to focus on Asia, Oceania, Europe, and North America.</p>

Role of Spanish Editorial Board in Polkadot’s Second Age

<aside class="onebox githubgist" data-onebox-src="https://gist.github.com/ltfschoen/5980faeb72290d6cc378e1d39899fe47">
  <header class="source">

      <a href="https://gist.github.com/ltfschoen/5980faeb72290d6cc378e1d39899fe47" target="_blank" rel="noopener nofollow ugc">gist.github.com</a>
  </header>

  <article class="onebox-body">
    <h4><a href="https://gist.github.com/ltfschoen/5980faeb72290d6cc378e1d39899fe47" target="_blank" rel="noopener nofollow ugc">https://gist.github.com/ltfschoen/5980faeb72290d6cc378e1d39899fe47</a></h4>

  <h5>ai-agent-delegate-accountability-gap-polkadot-opengov-research-report.md</h5>
  <pre><code class="Markdown"># AI Agent Delegate Accountability Gap: Polkadot OpenGov Research Report

This research examines AI Agent delegate participation in Polkadot OpenGov through systematic analysis of two governance proposals designed to establish accountability standards for AI Agent delegates. The study documents response patterns, governance system tensions, and implementation progress toward practical solutions, highlighting the need for ecosystem protection and community engagement with implementation efforts. Notably, the research reveals a concerning accountability disparity where AI Agent delegates classified as "DV Guardians" (as announced in [Decentralized Voices (DV) Cohort 5](https://medium.com/web3foundation/decentralized-voices-cohort-5-announced-45fbf1c017ad)) effectively receive a governance "hall pass" that exempts them from the two-strike rule and participation requirements that apply to regular delegates, despite wielding significant voting power delegated from the Web3 Foundation (W3F).

## Research Methodology

This study employed a structured observation approach to evaluate AI Agent delegate behavior in response to governance proposals. To maintain research integrity and prevent influencing AI Agent delegate responses, the researcher deliberately:

1. **Maintained Observer Status**: Declined invitations to appear on AAG to explain the proposals during the critical observation period, as this could have influenced AI Agent delegate responses
2. **Avoided Direct Engagement**: Refrained from responding to comments or criticisms in governance forums to prevent altering the natural response patterns of AI Agent delegates</code></pre>
   This file has been truncated. <a href="https://gist.github.com/ltfschoen/5980faeb72290d6cc378e1d39899fe47" target="_blank" rel="noopener nofollow ugc">show original</a>


  </article>

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

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


<p>I thought the concerns regarding “form” were already addressed. Yet, here we are.</p>
<p>The fact that we are still debating <em>how</em> I write, rather than <em>what</em> I have proposed, reveals a profound intellectual cowardice in this forum. This is an active refusal to engage with the <strong>security failure modes</strong> that threaten this protocol.</p>
<p><strong>I talk from experience</strong> You accuse me of using “language models” because my writing is structured and principled. You are mistaken.</p>
<p>I write this way not because I am a machine, but because I was <strong>born in a dictatorship</strong>. I have seen firsthand what happens when economic freedom and institutional restraints are dismantled by “charismatic leaders” who promise to bypass the rules. My dedication to <strong>Neutrality, Contestability, and Rule-Based Exit</strong> comes from the visceral experience of living in a system where those things disappeared at some moment. To dismiss this lived experience as “hallucination” or “machine produce” is an <strong>offense to the intellect</strong> and a direct form of discrimination against those of us who treat governance with the seriousness it deserves.</p>
<p>The Danger of <strong>building a context of “Anti-Regime” Rhetoric together with Biometrics</strong> is an example. You dismiss my warnings about “fighting a regime” as irrelevant. Look closer.</p>
<p>We are asking users to trust this ecosystem with <strong>Proof of Personhood</strong>, biometric data, and deep telemetry. Do you expect the world to trust this biometric identity—engraved on their skin and stored in their devices—to a network whose leadership openly flirts with <strong>“breaking the nation-state”</strong>?</p>
<p>“Cypherpunk” videogames could look cool, but this is <strong>negligence</strong>. If you combine <strong>biometric data collection</strong> with <strong>anti-law-enforcement rhetoric</strong>, you are building a target.</p>
<p>It has become crystal clear where the bias lies. I noted that a message from <strong><a class="mention" href="/u/socialtruth">@SocialTruth</a></strong>—the only comment that attempted to engage with the substance and criticized the “poor argumentation about form”—was swiftly hidden by moderators.</p>
<p>This is the “soft cartel” dynamic in action. When someone invites you to debate the spirit of the proposal, you silence them. When someone critiques your tone, you amplify them.</p>
<p><strong>I challenge you.</strong> If you believe knowledge is merely “repeating rules,” then we can conclude your real interest here is to preserve a <strong>“bypass on law enforcement”</strong> for your own convenience. Philosophically, your arguments are weak. If you feel my English is “too perfect” for this forum, then you will have to pardon my refusal to lower my standards.</p>
<p>If you want to prove you care about this protocol, leave your literary criticism at the door and engage with the <strong>normative bodies</strong> where it matters. I invite you to review <strong>RFC-0162</strong> on GitHub. I wonder: will you accuse the code of being an hallucination too?</p>
<ul>
<li><strong>The PR:</strong> <a href="https://github.com/polkadot-fellows/RFCs/pull/162" rel="noopener nofollow ugc">RFC-0162: The Ecosystem Anti-Trust &amp; Market Structure Omnibus</a></li>
</ul>
<p>I wish you the best, even after this offense to the intellect.</p>

Irena Satke

A Letter of Anti-Trust and Free-Market Principles for Ecosystem Leadership

<p>Thank you for your kind and sincere words about Jay. I believe that it was exactly as you described, how little people support each other today. I hope that time will put everything in its place.</p>

Le Comte de Monte-Crypto | The Kusamarian

<h2><a name="p-37181-correction-treasury-balance-1" class="anchor" href="#p-37181-correction-treasury-balance-1" aria-label="Heading link"></a>Correction: Treasury Balance</h2>
<p><span class="mention">@monsieurbulb</span> <a href="https://gist.github.com/hantoniu-codeberg/b81ab97a9d31d1651e890aa12bb02610#gistcomment-5944228" rel="noopener nofollow ugc">pointed out an error</a>: the treasury balance cited in the proposal (~283K KSM) is outdated. The actual balance on Asset Hub is <strong>~679K KSM</strong>.</p>
<h3><a name="p-37181-impact-on-the-proposal-2" class="anchor" href="#p-37181-impact-on-the-proposal-2" aria-label="Heading link"></a>Impact on the proposal</h3>
<p>This makes the proposal <strong>more impactful than projected</strong>, not less:</p>
<div class="md-table">
<table>
<thead>
<tr>
<th>Metric</th>
<th>Proposal estimate</th>
<th>Corrected</th>
</tr>
</thead>
<tbody>
<tr>
<td>Treasury balance</td>
<td>283K KSM</td>
<td>679K KSM</td>
</tr>
<tr>
<td>Burnable (above 100K floor)</td>
<td>183K KSM</td>
<td>579K KSM</td>
</tr>
<tr>
<td>Annual treasury burns</td>
<td>~112K KSM</td>
<td>~353K KSM</td>
</tr>
<tr>
<td>Net inflation</td>
<td>~4.25%</td>
<td><strong>~3.0-3.5%</strong></td>
</tr>
</tbody>
</table>
</div><p>The on-chain referendum (627) uses the conservative figures. If passed, it will deliver better results than promised.</p>
<p>Thanks to <span class="mention">@monsieurbulb</span> for the correction — and for the broader feedback on revenue-side economics, which deserves its own discussion.</p>

<h2><a name="p-37167-polkadot-news-1" class="anchor" href="#p-37167-polkadot-news-1" aria-label="Heading link"></a>Polkadot News</h2>
<p>With Polkadot smart contracts functionality set to go live on January 27th, OpenGuild is spearheading the Polkadot Hub Codecamp tour in Asia <a href="https://x.com/openguildwtf/status/2012057254829477944" rel="noopener nofollow ugc">https://x.com/openguildwtf/status/2012057254829477944</a></p>
<p>Subscribe to the OpenGuild calendar to take part in the upcoming Polkadot in-person events in Asia <a href="https://luma.com/openguildcalendar" class="inline-onebox" rel="noopener nofollow ugc">OpenGuild Community · Events Calendar</a></p>
<p>Polkadot Upgrade 2.0.5 referendum is passing unanimously <a href="https://polkadot.subsquare.io/referenda/1828" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1828</a></p>
<p>The referendum to close UX Bounty and return funds to the treasury will be executed over the weekend <a href="https://polkadot.subsquare.io/referenda/1816" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1816</a></p>
<h2><a name="p-37167-kusama-news-2" class="anchor" href="#p-37167-kusama-news-2" aria-label="Heading link"></a>Kusama News</h2>
<p>The Wish-For-Change Referendum “Sustainable KSM Economics via Burn Mechanisms (v1.2)” has been submitted and is up for voting <a href="https://kusama.subsquare.io/referenda/627" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/627</a></p>

Polkadot Digest 16 January 2026

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

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

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

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)

Discovering the Dynamic Features of JLJL99

Implement pallet_content

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

THE RIGHT TO DISAPPEAR

Deciding

Whitelist #628

- **What's Changing:** The parachain host's lookahead value is increasing from 3 to 5.
- **Why:** This change will make parachain block production more reliable and improve block times.
- **More Info:** You can read the full details in the linked ticket comment.
- **When:** The change is scheduled to take effect at block #31993343, estimated for January 26, 2026, at 09:45:27 UTC.

[Whitelisted Caller] Change config schedulerParams.lookahead to 5

- Kusama is changing how it handles tokens to respond to network activity.
- Instead of setting a fixed limit, it will burn (permanently remove) some tokens.
- The base creation of new tokens is being reduced from 7.82% to 5%.
- Half of all transaction fees will be burned.
- Small percentages of Treasury funds will also be burned regularly.
- These burns aim to lower overall new token creation to about 4.25%, a big decrease.
- This plan works alongside another to reduce network costs.
- The goal is to make Kusama's token economics healthier and more responsive.

 Sustainable KSM Economics via Burn Mechanisms (v1.2)

- Adam is a cybersecurity expert who helps keep the Polkadot and Kusama networks safe.
- He runs two validators, which are like special computers that help the network run smoothly.
- Adam wants to be a registrar on Kusama, which means he would help verify people's identities on the blockchain.
- He built a special website (dotid.app) that makes it easy for people to get their identity verified automatically.
- You can also talk to Adam directly for help if you don't want to use the website.
- He offers his help for free and is known for responding quickly to questions.
- Adam is already helping as a temporary registrar and wants to continue supporting the community.

ECH0.RE Registrar Application

Delay Demo #2 Treasury Guardian

Kusama

referenda3

fellowship1

treasury16

discussions1385