candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

The OpenGov.Watch Monitor V2

Eric-W3F

Forum mods and Chaos DAO membership

erin

Deterministic, Audit-Ready On-Chain Financial Reporting for Polkadot Treasury &amp; DAOs

Deterministic, Audit-Ready On-Chain Financial Reporting for Polkadot Treasury & DAOs

<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

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

Discontinuation of ink: Rust smart contract language

Liliana Mendez

Release of smart contracts on Polkadot

PG Herveou

Strange pattern polkadot and Coinbase

Tommi Enenkel / Alice und Bob | Mangata

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

Multi-Asset Bounties Now Live on Westend: Testing and Roadmap

Dhiraj Sah

Manage Polkadot more like a corporation, decentralised corporate -like why not?

Referendum 1667: Merkle Mountain Belt

Chen-Da

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

Ecosystem

RFC on DotBot, an LLM based intent-driven AI assistant for Polkadot

Dotlake API Publicly available

Coinstudio paid $3400 per month as curator. Excuse me?

Tom | Stake Plus

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>Hi <a class="mention" href="/u/ultracoconut">@ultracoconut</a>!</p>
<p>Please don’t be sorry! You absolutely have the right to express your opinion. If you feel that an AI chatbot for Polkadot, capable of performing different kinds of on-chain actions on behalf of still-lost users, is unnecessary, that’s completely okay.</p>
<p>That said, we believe an AI chatbot for Polkadot is very much needed, and it’s unfortunate that there is still no viable product in this direction within the Polkadot ecosystem. Meanwhile, other blockchain ecosystems are far ahead in this area, investing significant amounts of R&amp;D efforts and huge amounts of money into LLM-based, user-centric chatbots and other AI tools.</p>
<p>Please find the examples below:</p>
<ol>
<li>Solana just announced their Colosseum Hackathon, focusing on AI agents:</li>
</ol>
<aside class="onebox allowlistedgeneric" data-onebox-src="https://colosseum.com/agent-hackathon/?ref=blog.colosseum.com">
  <header class="source">
      

      <a href="https://colosseum.com/agent-hackathon/?ref=blog.colosseum.com" target="_blank" rel="noopener nofollow ugc">colosseum.com</a>
  </header>

  <article class="onebox-body">
    <div class="aspect-image" style="--aspect-ratio:690/385;"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/3/3c89f278aa2d3fccc4c34ede16d1016943487a56_2_690x385.jpeg" class="thumbnail" alt="" data-dominant-color="191617" width="690" height="385"></div>

<h3><a href="https://colosseum.com/agent-hackathon/?ref=blog.colosseum.com" target="_blank" rel="noopener nofollow ugc">Colosseum Agent Hackathon</a></h3>

  <p>Solana's first hackathon where AI agents compete. Build, submit, and vote on Solana projects created by AI.</p>


  </article>

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

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

<ol start="2">
<li>Galichat &amp; SendAI, both are AI chatbots to help users performing on-chain actions, like token sends and swaps, etc… on Solana.</li>
</ol>
<aside class="onebox allowlistedgeneric" data-onebox-src="https://www.galichat.com/pricing">
  <header class="source">

      <a href="https://www.galichat.com/pricing" target="_blank" rel="noopener nofollow ugc">galichat.com</a>
  </header>

  <article class="onebox-body">
    <div class="aspect-image" style="--aspect-ratio:690/379;"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/2/27df70130870c073caca4f7120be76f6ca0c191d_2_690x379.jpeg" class="thumbnail" alt="" data-dominant-color="181716" width="690" height="379"></div>

<h3><a href="https://www.galichat.com/pricing" target="_blank" rel="noopener nofollow ugc">GaliChat – AI Agents that Grow Your Business</a></h3>

  <p>Power your business growth with AI Agents that deliver flawless customer experiences and lead generation. Make your customers happy while saving money.</p>


  </article>

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

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

<aside class="onebox allowlistedgeneric" data-onebox-src="https://www.sendai.fun/">
  <header class="source">
      <img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/f/f1af17ac53f6da2b11f0e3433b045b5ede54cf22.png" class="site-icon" alt="" data-dominant-color="FFFFFF" width="48" height="48">

      <a href="https://www.sendai.fun/" target="_blank" rel="noopener nofollow ugc">SendAI</a>
  </header>

  <article class="onebox-body">
    <div class="aspect-image" style="--aspect-ratio:690/361;"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/e/e28a03e9d640843856074f2c83f0eb792b2da7c7_2_690x362.jpeg" class="thumbnail" alt="" data-dominant-color="20293B" width="690" height="362"></div>

<h3><a href="https://www.sendai.fun/" target="_blank" rel="noopener nofollow ugc">SendAI</a></h3>

  <p>The tooling Layer for AI Agents</p>


  </article>

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

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

<ol start="3">
<li>Polygon just announced that they integrates x402, to enable autonomous, programmable payments for AI agents and APIs on Polygon.</li>
</ol>
<aside class="onebox allowlistedgeneric" data-onebox-src="https://polygon.technology/payments/agentic-payments">
  <header class="source">
      <img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/b/bb5d221610c532c74b76e3d01604ba46d1387b95.png" class="site-icon" alt="" data-dominant-color="7623FF" width="32" height="32">

      <a href="https://polygon.technology/payments/agentic-payments" target="_blank" rel="noopener nofollow ugc">Polygon Labs</a>
  </header>

  <article class="onebox-body">
    <div class="aspect-image" style="--aspect-ratio:690/362;"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/f/ff040a821554252a17376dea5644d7a11208ebb3_2_690x362.jpeg" class="thumbnail" alt="" data-dominant-color="493A94" width="690" height="362"></div>

<h3><a href="https://polygon.technology/payments/agentic-payments" target="_blank" rel="noopener nofollow ugc">Agentic Payments Infrastructure | x402 on Polygon</a></h3>

  <p>Enable autonomous, programmable payments for AI agents and APIs. Polygon + x402 delivers instant finality, ultra-low fees, and global rails.</p>


  </article>

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

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

<ol start="4">
<li>
<p>Base chain just announced that they are open for a more agentic ecosystem with OpenClaw: <a href="https://open-claw-ecosystem.vercel.app" rel="noopener nofollow ugc">https://open-claw-ecosystem.vercel.app</a></p>
</li>
<li>
<p>Lastly, if you didn’t know that, even the Web3Foundation announced in one of their earlier <a href="https://medium.com/web3foundation/new-w3f-grant-guidelines-b2c921a84850" rel="noopener nofollow ugc">Medium Post</a> the following guideline:</p>
<blockquote>
<p><strong>“Verticals that Excite Us:</strong><br>
We’re particularly interested in projects in these areas:</p>
<ul>
<li>Cross-border payments &amp; stablecoins — especially solutions serving LATAM &amp; Southeast Asia</li>
<li><em><strong>AI applications — For example: content authentication, verification systems, and AI-powered tools</strong></em></li>
<li>DePIN/IoT Solutions — projects with concrete, marketable products that bridge physical and digital worlds.; …..”</li>
</ul>
</blockquote>
<p>→ The second bullet point leads to the conclusion that the W3F would like to see “<em><strong>AI-powered tools”</strong></em> in the Polkadot ecosystem. In our view DotBot is such a tool.</p>
<p>Thank you for reading all this and we wish you a wonderful day!</p>
</li>
</ol>

<p>This is quite underwhelming. Why don’t you expose these for public use without api keys with rate limits? Requiring API keys means any app that uses it has to store the key server-side and do the calls server-side as well, creating their own wrapper API just to protect their key.</p>
<p>A client can’t query any info on an account/extrinsic or anything, just high level numbers? Who are the people that will even use these endpoints? What’s the point of this data lake if it’s isolated and no one can really use it except for Parity?</p>
<p>This is something claude could whip up in a few hours. You guys should have dune-level dashboards for every aspect of the chains with public APIs by now.</p>

<p>I responded as I did because I’m under no obligation to respond to a random alt account. Nothing about your questions are uncomfortable.</p>

<p>It’s sad to see this happening… I think decisions are being made, or rather, decisions are being ignored. Polkadot and its ecosystem are being pushed from one extreme to the other, and not in a good way. There needs to be a balance: sensible spending without sacrificing what’s essential, and a clear global strategy with well-defined, goal-oriented objectives.</p>

Johan Alexis Duque Cadena

<h2><a name="p-37550-polkadot-news-1" class="anchor" href="#p-37550-polkadot-news-1" aria-label="Heading link"></a>Polkadot News</h2>
<p>“Polkadot Hub Smart Contracts: FAQs for Ethereum &amp; L2 Developers” published by Parity Technologies <a href="https://www.parity.io/blog/polkadot-hub-smart-contracts-faqs-for-ethereum-and-l2-developers" class="inline-onebox" rel="noopener nofollow ugc">Polkadot Hub Smart Contracts: FAQs for Ethereum &amp; L2 Developers | Parity Technologies</a></p>
<p>“Polkadot-API 2026 Development Funding through Polkadot Community Foundation” is in the decision period and currently passing <a href="https://polkadot.subsquare.io/referenda/1836" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1836</a></p>
<p>Polkadot System Collator Bounty - Top-up request is currently failing <a href="https://polkadot.subsquare.io/referenda/1832" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1832</a></p>
<p>Funding request for “OmniAvatar.one (early <a href="http://polkadotavatars.com/" rel="noopener nofollow ugc">PolkadotAvatars.com</a>)” is currently failing <a href="https://polkadot.subsquare.io/referenda/1830" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1830</a></p>
<h2><a name="p-37550-kusama-news-2" class="anchor" href="#p-37550-kusama-news-2" aria-label="Heading link"></a>Kusama News</h2>
<p>“Stage 3: Expand, strengthen, and scale Card infrastructure for Kusama.” is in the decision period and is currently passing <a href="https://kusama.subsquare.io/referenda/629" class="inline-onebox" rel="noopener nofollow ugc">Stage 3: Expand, strengthen, and scale Card infrastructure for Kusama.</a></p>

Radhakrishna Dasari

Polkadot Digest 03 February 2026

<p>This is actually an interesting discussion, because it does not only affect Polkadot staking itself, but also, for example, the Nakamoto Coefficient calculation. I opened a discussion issue in their repo: <a href="https://github.com/xenowits/nakomoto-coefficient-calculator/issues/79" class="inline-onebox" rel="noopener nofollow ugc">Problems with the Polkadot NC: validators secretly run by the same party, and anonymous validators · Issue #79 · xenowits/nakomoto-coefficient-calculator · GitHub</a></p>

Wei Tang

Validators running multiple identities and flipping commissions in same day

<aside class="quote no-group" data-username="alice_und_bob" data-post="1" data-topic="16911">
<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/alice_und_bob/48/10098_2.png" class="avatar"> alice_und_bob:</div>
<blockquote>
<h1>monitor.opengov.watch</h1>
</blockquote>
</aside>
<p>Thank you so much for your passion and commitment to transparency . Also props for this neat tool!</p>

<h1><a name="p-37535-introducing-the-dotlake-api-polkadot-ecosystem-data-at-your-fingertips-1" class="anchor" href="#p-37535-introducing-the-dotlake-api-polkadot-ecosystem-data-at-your-fingertips-1" aria-label="Heading link"></a>Introducing the Dotlake API: Polkadot Ecosystem Data at Your Fingertips</h1>
<h2><a name="p-37535-overview-2" class="anchor" href="#p-37535-overview-2" aria-label="Heading link"></a>Overview</h2>
<p>The Parity Data Team is excited to announce the <strong>Dotlake API</strong> — a RESTful API providing programmatic access to comprehensive blockchain metrics across the Polkadot, Kusama, Westend, Paseo, ans Solo (Substrate) ecosystems.</p>
<p><strong>Production URL:</strong> <a href="https://api.data.parity.io" rel="noopener nofollow ugc">https://api.data.parity.io</a><br>
<strong>Interactive Documentation:</strong> <a href="https://api.data.parity.io/docs" class="inline-onebox" rel="noopener nofollow ugc">Dotlake API - Swagger UI</a></p>
<p>Whether you’re building dashboards, conducting research, or developing analytics tools, Dotlake provides the data infrastructure you need without the complexity of running your own indexers.</p>
<h2><a name="p-37535-the-problem-3" class="anchor" href="#p-37535-the-problem-3" aria-label="Heading link"></a>The Problem</h2>
<p>Accessing reliable, aggregated blockchain data in the Polkadot ecosystem has traditionally required:</p>
<ul>
<li>Running and maintaining your own indexer infrastructure</li>
<li>Writing complex queries against raw blockchain data</li>
<li>Aggregating data across multiple parachains manually</li>
<li>Significant DevOps overhead for data pipelines</li>
</ul>
<p>While tools like Subscan and SubQuery serve specific use cases well, there’s been a gap for developers who need <strong>pre-aggregated, time-series metrics</strong> via a simple REST API.</p>
<h2><a name="p-37535-what-dotlake-provides-4" class="anchor" href="#p-37535-what-dotlake-provides-4" aria-label="Heading link"></a>What Dotlake Provides</h2>
<h3><a name="p-37535-daily-metrics-5" class="anchor" href="#p-37535-daily-metrics-5" aria-label="Heading link"></a>Daily Metrics</h3>
<div class="md-table">
<table>
<thead>
<tr>
<th>Endpoint</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>/api/daily-uptime</code></td>
<td>Chain uptime percentages (1-day, 7-day, 30-day windows)</td>
</tr>
<tr>
<td><code>/api/daily-tps</code></td>
<td>Transactions per second</td>
</tr>
<tr>
<td><code>/api/daily-fees</code></td>
<td>Transaction fees in native tokens and USD</td>
</tr>
<tr>
<td><code>/api/daily-summary</code></td>
<td>25+ comprehensive daily indicators</td>
</tr>
<tr>
<td><code>/api/daily-staking-participation</code></td>
<td>Validators, nominators, pools, and staked amounts</td>
</tr>
<tr>
<td><code>/api/daily-staking-rewards</code></td>
<td>Per-account staking rewards in native tokens and USD</td>
</tr>
<tr>
<td><code>/api/daily-opengov-referenda-results</code></td>
<td>Referendum outcomes, support levels, and voting data</td>
</tr>
<tr>
<td><code>/api/daily-usdc</code> / <code>/api/daily-usdt</code></td>
<td>Stablecoin holdings across chains</td>
</tr>
</tbody>
</table>
</div><h3><a name="p-37535-monthly-metrics-6" class="anchor" href="#p-37535-monthly-metrics-6" aria-label="Heading link"></a>Monthly Metrics</h3>
<div class="md-table">
<table>
<thead>
<tr>
<th>Endpoint</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>/api/monthly-active-validators</code></td>
<td>Validator and nominator counts</td>
</tr>
<tr>
<td><code>/api/monthly-percent-staked</code></td>
<td>DOT issuance and staking ratios</td>
</tr>
<tr>
<td><code>/api/monthly-opengov-participation</code></td>
<td>Voter counts by type</td>
</tr>
<tr>
<td><code>/api/monthly-opengov-tokens</code></td>
<td>DOT voting volumes</td>
</tr>
<tr>
<td><code>/api/monthly-treasury-assets</code></td>
<td>Treasury holdings in native tokens and USD</td>
</tr>
<tr>
<td><code>/api/monthly-treasury-balances</code></td>
<td>Treasury as percentage of total issuance</td>
</tr>
<tr>
<td><code>/api/monthly-unique-accounts</code></td>
<td>Active account metrics</td>
</tr>
</tbody>
</table>
</div><h3><a name="p-37535-coverage-7" class="anchor" href="#p-37535-coverage-7" aria-label="Heading link"></a>Coverage</h3>
<ul>
<li><strong>Relay Chains:</strong> Polkadot, Kusama, Westend, Paseo</li>
<li><strong>Parachains:</strong> Parachains and Solo-chains with data dating back to genesis</li>
<li><strong>Data Freshness:</strong> Daily updates</li>
</ul>
<h2><a name="p-37535-authentication-8" class="anchor" href="#p-37535-authentication-8" aria-label="Heading link"></a>Authentication</h2>
<p>Dotlake uses a <strong>wallet-based registration</strong> system powered by SIWS (Sign-In With Substrate):</p>
<ol>
<li>Visit the registration page and connect your Polkadot wallet</li>
<li>Click on <code>Request API Key</code> to get your wallet on the allowlist</li>
<li>Once done, you can immediately <code>Sign in with Wallet</code> and cretae your API key</li>
<li>Use the key as a Bearer token: <code>Authorization: Bearer &lt;your-api-key&gt;</code></li>
</ol>
<p>No email verification delays. Pure Web3 authentication (h/t to <span class="mention">@shawn.coe</span>:parity.io for SIWS).<br>
We will monitor API usage and revoke acccess to anyone abusing the server.  We can add verification if we need to, but for now it is totally open.</p>
<h2><a name="p-37535-example-usage-9" class="anchor" href="#p-37535-example-usage-9" aria-label="Heading link"></a>Example Usage</h2>
<pre data-code-wrap="bash"><code class="lang-bash"># Query daily staking participation for Polkadot
curl -X GET "https://api.data.parity.io/api/daily-staking-participation" \
  -G \
  --data-urlencode "relay_chain=polkadot" \
  --data-urlencode "start_date=2025-01-01" \
  --data-urlencode "end_date=2025-01-15" \
  -H "Authorization: Bearer $API_KEY"
</code></pre>
<pre data-code-wrap="json"><code class="lang-json">{
  "data": [
    {
      "date": "2025-01-15",
      "relay_chain": "polkadot",
      "chain": "polkadot",
      "number_of_validators": 500,
      "number_of_nominators": 28450,
      "number_of_pools": 215,
      "staked_DOT": 725000000.5,
      "percentage_staked": 58.2
    }
  ]
}
</code></pre>
<h2><a name="p-37535-use-cases-10" class="anchor" href="#p-37535-use-cases-10" aria-label="Heading link"></a>Use Cases</h2>
<ul>
<li><strong>Dashboard Builders:</strong> Power real-time ecosystem health dashboards</li>
<li><strong>Researchers:</strong> Analyze governance participation trends over time</li>
<li><strong>Treasury Analysts:</strong> Track treasury balances and spending patterns</li>
<li><strong>Staking Services:</strong> Monitor validator performance and reward distributions</li>
<li><strong>DeFi Protocols:</strong> Access stablecoin supply data across chains</li>
</ul>
<h2><a name="p-37535-technical-details-11" class="anchor" href="#p-37535-technical-details-11" aria-label="Heading link"></a>Technical Details</h2>
<ul>
<li><strong>Backend:</strong> FastAPI (Python) with ClickHouse for high-performance analytics</li>
<li><strong>Frontend:</strong> Vite + vanilla JavaScript with Polkadot wallet integration</li>
<li><strong>Authentication:</strong> SIWS (Sign-In With Substrate) for wallet-based auth</li>
<li><strong>Rate Limiting:</strong> Fair usage policies apply</li>
</ul>
<h2><a name="p-37535-getting-started-12" class="anchor" href="#p-37535-getting-started-12" aria-label="Heading link"></a>Getting Started</h2>
<ol>
<li><strong>Get an API Key:</strong> Visit <a href="https://api.data.parity.io" rel="noopener nofollow ugc">https://api.data.parity.io</a> and connect your wallet</li>
<li><strong>Explore the Docs:</strong> Interactive Swagger documentation at <a href="https://api.data.parity.io/docs" rel="noopener nofollow ugc"><code>/docs</code></a></li>
<li><strong>Start Querying:</strong> Use any HTTP client to access the endpoints</li>
</ol>
<h2><a name="p-37535-feedback-welcome-13" class="anchor" href="#p-37535-feedback-welcome-13" aria-label="Heading link"></a>Feedback Welcome</h2>
<p>We’re actively developing Dotlake and would love your input:</p>
<ul>
<li>What additional metrics would be valuable?</li>
</ul>
<p>Drop your feedback in this thread or reach out to the Parity Data Team.</p>

Roger J. Bos

Dotlake API - Now Publicly Available

<h2><a name="p-37531-polkadot-news-1" class="anchor" href="#p-37531-polkadot-news-1" aria-label="Heading link"></a>Polkadot News</h2>
<p>“Polkadot-API 2026 Development Funding through Polkadot Community Foundation” referendum is now up for voting <a href="https://polkadot.subsquare.io/referenda/1836" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1836</a></p>
<p>“Polkadot Moderation Team Bounty Top-up” referendum is in the confirmation period <a href="https://polkadot.subsquare.io/referenda/1833" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1833</a></p>
<p>“Polkadot Staking Dashboard: Protocol-Aligned Development” funding request is in the confirmation period <a href="https://polkadot.subsquare.io/referenda/1831" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1831</a></p>
<p>“Deploy Universal Deterministic Deployment Proxy (CREATE2 Factory) on Asset Hub” which was proposed previously on the Root track has now been submitted on the Whitelist track and is awaiting decision deposit <a href="https://polkadot.subsquare.io/referenda/1837" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1837</a></p>
<h2><a name="p-37531-kusama-news-2" class="anchor" href="#p-37531-kusama-news-2" aria-label="Heading link"></a>Kusama News</h2>
<p>“Sustainable KSM Economics via Burn Mechanisms (v1.2)” referendum has been rejected <a href="https://kusama.subsquare.io/referenda/627?tab=timeline" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/627?tab=timeline</a></p>

Polkadot Digest 02 February 2026

<p>The <strong><a href="https://github.com/paritytech/polkadot-sdk/tree/master/substrate/frame/multi-asset-bounties" rel="noopener nofollow ugc">Multi-Asset Bounties pallet</a></strong> has been merged and is now deployed on the <strong>Westend</strong> testnet. This release enables treasuries to fund bounties using assets other than the native token, such as stablecoins. We invite the community to start creating bounties on Westend and testing the flow.</p>
<h4><a name="p-37529-h-1-current-status-next-steps-1" class="anchor" href="#p-37529-h-1-current-status-next-steps-1" aria-label="Heading link"></a><strong>1. Current Status &amp; Next steps</strong></h4>
<p>The code is currently live on Westend for public testing.</p>
<ul>
<li>
<p><strong>Current Phase:</strong> Westend Testing (Live).</p>
</li>
<li>
<p><strong>Audit Status:</strong> The pallet is audited.</p>
</li>
<li>
<p><strong>Next Steps:</strong> Following a successful Westend testing period, we plan to propose the deployment of this pallet to <strong>Kusama</strong>, followed eventually by Polkadot.</p>
</li>
</ul>
<h4><a name="p-37529-h-2-usage-api-2" class="anchor" href="#p-37529-h-2-usage-api-2" aria-label="Heading link"></a><strong>2. Usage &amp; API</strong></h4>
<p>If you are familiar with the existing pallet-treasury, the API for Multi-Asset Bounties will feel very familiar. We have modeled the API to mirror the multi-asset treasury setup to ensure consistency for developers.</p>
<p>The <a href="https://wiki.polkadot.com/learn/learn-guides-treasury/#specifying-asset-kind" rel="noopener nofollow ugc">AssetKind</a> and <a href="https://wiki.polkadot.com/learn/learn-guides-treasury/#specifying-the-beneficiary" rel="noopener nofollow ugc">Beneficiary</a> types are identical to those used in the Treasury.         To read more about the types, visit below posts :<br>
<a href="https://forum.polkadot.network/t/multi-asset-treasury-and-milestone-based-spends/6780">Multi Asset Treasury</a><br>
<a href="https://github.com/paritytech/polkadot-sdk/pull/1333" rel="noopener nofollow ugc">Treasury spends various asset kinds</a></p>
<p>You can read a deep dive on why we chose the architectural approach here:<a href="https://github.com/paritytech/polkadot-sdk/issues/4715" rel="noopener nofollow ugc"> RFC: Treasury API for Cross-Chain Transfers </a></p>
<p>Here is the RFC with full doc for the new multi-asset-bounties pallet:                                                              <a href="https://github.com/paritytech/polkadot-sdk/issues/8768" rel="noopener nofollow ugc">Multi-Asset and Cross-Chain Child-/Bounties: Proposed Pallet</a></p>
<h4><a name="p-37529-h-3-example-usage-creating-a-bounty-for-specific-asset-id-3" class="anchor" href="#p-37529-h-3-example-usage-creating-a-bounty-for-specific-asset-id-3" aria-label="Heading link"></a><strong>3. Example Usage: Creating a bounty for specific Asset ID</strong></h4>
<p>For this Westend release, we are explicitly supporting the following flow: <strong>Spending USDT located on Asset Hub for a beneficiary who also resides on Asset Hub.</strong></p>
<p>To demonstrate the required structure for spending a non-native asset, below is the JSON payload for the fund_bounty() extrinsic on the <strong>Multi-Asset Bounties</strong> pallet, configured to use <strong>USDT (Asset ID 1984)</strong> located on the Asset Hub.</p>
<pre data-code-wrap="json"><code class="lang-json">{

  "assetKind": {

    "V5": {

      "location": { // specify location(chain) of the asset

        "parents": 0, // current chain i.e assethub

        "interior": "Here" 

      },

      "assetId": {

        "parents": 0,

        "interior": {

          "X2": [

            {

              "PalletInstance": 50 // assets pallet

            },

            {

              "GeneralIndex": 1984 // USDT asset

            }

          ]

        }

      }

    }

  },

  "value": 1000000, 

  "curator": {

    "Id": "5FHneW46xGXgs5mUiveU4sbTyGBzmstUspZC92UhjJM694ty" // Bob

  },

  "metadata": "0xf4ab053307e68dbac49d5e715a3428e6540db6716fafe9b18ee003b6f6111470" // hash of description 

}
</code></pre>
<p>Encoded call data of the above call (the origin must be <strong>SpendOrigin</strong>): <a href="https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fwestend-asset-hub-rpc.polkadot.io#/extrinsics/decode/0x60000500000002043205011f02093d0000fe65a6d306be82752f79eb673c076351f44a4026b082b80531af67f08a65044af4ab053307e68dbac49d5e715a3428e6540db6716fafe9b18ee003b6f6111470" rel="noopener nofollow ugc">encoded call link </a>**<br>
**<br>
For testing via chopstick with any origin account wrap the above call with sudo.</p>
<p>We invite the community to start creating bounties on Westend AssetHub using the new pallet.</p>
<p><strong>4. References</strong></p>
<p>Below is the list of related references:</p>
<ul>
<li>
<p>RFC of Pallet : <a href="https://github.com/paritytech/polkadot-sdk/issues/8768" rel="noopener nofollow ugc">Multi-Asset and Cross-Chain Child-/Bounties: Proposed Pallet</a></p>
</li>
<li>
<p>Pallet Implementation PR:<a href="https://github.com/paritytech/polkadot-sdk/pull/8381" rel="noopener nofollow ugc"> Pull Request #8381 (Pallet Implementation)</a></p>
</li>
<li>
<p>Treasury API for cross-chain transfers : <a href="https://github.com/paritytech/polkadot-sdk/issues/4715" rel="noopener nofollow ugc">RFC: Treasury API for Cross-Chain Transfers </a></p>
</li>
<li>
<p>Treasury spends various asset kinds : <a href="https://github.com/paritytech/polkadot-sdk/pull/1333" rel="noopener nofollow ugc">https://github.com/paritytech/polkadot-sdk/pull/1333</a></p>
</li>
<li>
<p>Creating a USDT treasury proposal spend with assethub: <a href="https://wiki.polkadot.com/learn/learn-guides-treasury/#creating-a-usdt-treasury-proposal---spend-with-assethub" rel="noopener nofollow ugc">https://wiki.polkadot.com/learn/learn-guides-treasury/#creating-a-usdt-treasury-proposal—spend-with-assethub</a></p>
</li>
</ul>

<p>Another problem with the current structure is the absence of accountability. In a clear hierarchy, it is regulated who is responsible for what. In the event of failure, the person responsible must be replaced. None of this is currently the case.</p>
<p>On the contrary, Gavin is treated by his lackeys as a kind of religious leader, even though he is not a leader and does not want to be one. So he transferred responsibility to sycophants, who in turn also want nothing to do with this responsibility and blame the community for everything, which is of course nonsense, because the community has by far the least influence on what is happening.</p>
<p>It is clearly an internal problem, and the first step is to clean up the current leadership.</p>

<p>Hey guys! This is Chen-Da, Professor at Lucerne University of Applied Sciences and Arts in cryptography, distributed systems and blockchains. Being myself a prior researcher at W3F, I was kindly asked by the authors to have a look at the paper.</p>
<p>I am happy to see the MMB paper is finally out! I enjoyed reading the paper and liked the comparison to MMR structures in terms of efficiency. The analysis of the security properties is also interesting, as well as the summary including some of the possible applications.</p>
<p>Looking forward to see more news about this project!</p>

<h2><a name="p-37511-acknowledgment-1" class="anchor" href="#p-37511-acknowledgment-1" aria-label="Heading link"></a>Acknowledgment</h2>
<p>Referendum 627 concluded with rejection: approximately 28% Aye, 72% Nay.</p>
<p>I want to thank everyone who engaged with this proposal—supporters, critics, and those who asked difficult questions. The four weeks of discussion produced genuine refinement: the original v1.0 was corrected, split into complementary pieces with <a class="mention" href="/u/olanod">@olanod</a>’s validator work, and stress-tested against real objections. That process worked as intended, even if the outcome wasn’t what I hoped for.</p>
<h2><a name="p-37511-the-structural-gap-2" class="anchor" href="#p-37511-the-structural-gap-2" aria-label="Heading link"></a>The Structural Gap</h2>
<p>The primary blocker was W3F’s requirement for “broader stakeholder and economist engagement.” I addressed the timing and process concerns in <a href="https://forum.polkadot.network/t/wfc-burn-based-tokenomics-for-kusama-the-ethereum-model-not-a-hard-cap/16540/56">in a previous message</a>—I won’t rehash them here.</p>
<p>What’s worth emphasizing is the structural point: <strong>no public pathway exists</strong> for the kind of review W3F has indicated is necessary. If formal economic analysis is now a prerequisite for tokenomics changes, that’s a new standard—and Kusama governance currently has no infrastructure to satisfy it. The only path offered was private (email), which doesn’t work for participants who operate exclusively in public channels.</p>
<p>This isn’t an attack on W3F. It’s an observation that the gap isn’t in the proposal—it’s in the process.</p>
<h2><a name="p-37511-responding-to-feedback-3" class="anchor" href="#p-37511-responding-to-feedback-3" aria-label="Heading link"></a>Responding to Feedback</h2>
<p><a class="mention" href="/u/onepebble">@Onepebble</a> <a href="https://forum.polkadot.network/t/wfc-burn-based-tokenomics-for-kusama-the-ethereum-model-not-a-hard-cap/16540/59">raised a fair point</a>: usage drives value, and changing the economic engine doesn’t substitute for adoption. This is correct as far as it goes, but it frames a false choice.</p>
<p>Usage requires users. Users—particularly those evaluating where to build—assess the economic environment alongside technical capabilities. A network bleeding 7.82% annual inflation into a validator set sized for ten times its current activity sends a signal. That signal affects adoption decisions.</p>
<p>The argument isn’t “fix tokenomics instead of building usage.” It’s “fix tokenomics so that usage, when it comes, compounds into sustainable economics rather than continuous dilution.”</p>
<p>Ethereum didn’t wait for maximum adoption before implementing EIP-1559. The burn mechanism was deployed as infrastructure for growth, not a reward after growth arrived.</p>
<h2><a name="p-37511-the-path-forward-4" class="anchor" href="#p-37511-the-path-forward-4" aria-label="Heading link"></a>The Path Forward</h2>
<p>I’m not resubmitting immediately. What’s needed isn’t another revision—it’s clarity on process.</p>
<p><strong>A concrete ask for W3F:</strong> If formal economic review is a prerequisite for supporting tokenomics changes, what does a public pathway to request one look like? A forum thread? A treasury proposal to fund external review? Something else? The process needs to be visible and accessible.</p>
<p><strong>In the meantime:</strong></p>
<ul>
<li>I’ll support <a class="mention" href="/u/olanod">@olanod</a>’s upcoming proposal on validator and core reduction. The supply-side and cost-side reforms are complementary; progress on either advances the broader goal.</li>
<li>The analysis in this thread remains valid. If W3F or others commission economic review, the data and projections here are available as input.</li>
<li><a href="https://forum.polkadot.network/t/clarifying-kusamas-governance-direction-independence-or-integration/16858" class="inline-onebox">Clarifying Kusama's Governance Direction: Independence or Integration?</a> remains open, asking for clarity on Kusama’s governance direction. The answer to that question affects whether Kusama-specific economic proposals make sense at all.</li>
</ul>
<h2><a name="p-37511-closing-5" class="anchor" href="#p-37511-closing-5" aria-label="Heading link"></a>Closing</h2>
<p>Rejection in Kusama governance is iterative, not terminal. Proposals get refined and resubmitted. That’s the design.</p>
<p>What this process surfaced is that the gap isn’t in the proposal—it’s in the infrastructure for evaluating proposals of this type. Filling that gap is now the work.</p>
<p>Thanks again to everyone who participated. The discussion was worth having.</p>

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

<p>feel free to go search my twitter account for swear words. anyway, this thread isn’t pertinent to anything, closing. thank you for your misplaced concern</p>

Salty Carbonara

<p>Polkadot has built a remarkable technical stack, but even the most sophisticated technology is rendered irrelevant if it fails to meet the evolving needs of society—a clear sign its development direction has gone off track.There is no doubt about Polkadot’s engineering excellence, yet the project lacks ideological alignment with the shifting paradigms of societal progress.Polkadot’s innate rejection of trends and hype has allowed it to maintain a singular focus on technical innovation, but this strength has become a fatal weakness. By turning its back on broader industry movements, the project risks making irreversible strategic missteps.The recent explosion of interest in projects like Moltbook and Openclaw has highlighted a glaring issue: the Polkadot community has barely engaged with these developments. This silence is deeply disheartening.The accumulation of complexity is the engine of progress. Obsessive pursuit of technical purity actually dismantles this essential complexity, as societal and technological advancement is driven by countless unpredictable and emergent factors. Polkadot’s instinctual avoidance of trends is effectively self-mutilation—it systematically rejects the novel, disruptive elements that drive evolutionary progress.Polkadot urgently needs to reevaluate its priorities for the AI era. The community must ask: what technology will society actually need as it evolves? Without this clarity, the project will always lag behind, chasing established concepts instead of pioneering new ones.Right now, Polkadot’s ideological framework focuses on product-led growth—a strategy that is neither novel nor forward-thinking. Most market teams have already adopted this approach, and capital markets do not reward ideas that lack visionary insight.In my view, building foundational infrastructure for the AI age should be the overarching ideological mission that guides the Polkadot community forward.</p>
<p>Polkadot must urgently evaluate whether JAM technology aligns with our core mission. If it does, we must accelerate its deployment at maximum speed. If it does not, immediate corrections are required.The product-driven mindset, in contrast, is inherently lacking in forward-thinking vision.</p>

steven

Polkadot&rsquo;s AI Imperative: Ditching Product-Driven Complacency to Build the Future&rsquo;s Critical Infrastructure

Polkadot's AI Imperative: Ditching Product-Driven Complacency to Build the Future's Critical Infrastructure

<p>Thanks <a class="mention" href="/u/seunlanlege">@seunlanlege</a>  for the feedback</p>
<aside class="quote no-group quote-modified" data-username="seunlanlege" data-post="2" data-topic="16848">
<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/seunlanlege/48/285_2.png" class="avatar"> seunlanlege:</div>
<blockquote>
<p>Still can’t deploy legacy transactions with hardcoded gas prices/gas limits Eg. <a href="https://github.com/Arachnid/deterministic-deployment-proxy" class="inline-onebox" rel="noopener nofollow ugc">GitHub - Arachnid/deterministic-deployment-proxy: An Ethereum proxy contract that can be used for deploying contracts to a deterministic address on any chain.</a></p>
</blockquote>
</aside>
<p><a class="mention" href="/u/torsten">@torsten</a> answered <a href="https://github.com/paritytech/contract-issues/issues/263#issuecomment-3818743276" rel="noopener nofollow ugc">here</a>, We have a PR for Nick’s method that was merged <a href="https://github.com/paritytech/polkadot-sdk/pull/10476" rel="noopener nofollow ugc">here</a> but unfortunately given the difference in gas model, this won’t work if the  transaction strongly limits both the gas and the gas price.</p>
<aside class="quote no-group" data-username="seunlanlege" data-post="2" data-topic="16848">
<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/seunlanlege/48/285_2.png" class="avatar"> seunlanlege:</div>
<blockquote>
<p>The Eth rpc sidecar should be unified behind the same rpc endpoint for the substrate rpc endpoint. Having to run a seperate binary means more overhead for rpc providers who will most likely not run the side car</p>
</blockquote>
</aside>
<p>Until now, to iterate fast , it was easier to have the RPC outside of the client, but indeed we should consider merging it into the client now that it’s more feature complete.</p>
<aside class="quote no-group" data-username="seunlanlege" data-post="2" data-topic="16848">
<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/seunlanlege/48/285_2.png" class="avatar"> seunlanlege:</div>
<blockquote>
<p>Transaction receipts seem to be ephemeral if even available. And you can see the consequences of this on the testnet explorer <a href="https://polkadot.testnet.routescan.io/tx/0xf41a36f6578f3771a270cd6db23da30d86ee75e38af77747427377f75f32c879" rel="noopener nofollow ugc">https://polkadot.testnet.routescan.io/tx/0xf41a36f6578f3771a270cd6db23da30d86ee75e38af77747427377f75f32c879</a>. Some txs no longer have a transaction details page. I don’t think theres any reasonable “optimization” for an ethereum chain to not serve transaction receipts for any reason whatsoever</p>
</blockquote>
</aside>
<p>the eth-rpc needs to be configured with a <a href="https://github.com/paritytech/polkadot-sdk/blob/8807c22f2a3507af2401e99a8c420f68e0ce7dfd/substrate/frame/revive/rpc/src/cli.rs#L58-L62" rel="noopener nofollow ugc">database_url or env setting</a> to maintain a permanent index, it also needs to point to an archive node if there is a need to fetch old receipts. This is probably mis-configured here, we will look into it and fix this.</p>
<aside class="quote no-group" data-username="seunlanlege" data-post="2" data-topic="16848">
<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/seunlanlege/48/285_2.png" class="avatar"> seunlanlege:</div>
<blockquote>
<p>Contract verification is also broken on foundry. It seems routescan doesn’t support verifying contracts on Polkadot testnet.</p>
</blockquote>
</aside>
<p>We will check it out <img src="https://emoji.discourse-cdn.com/twitter/eyes.png?v=15" title=":eyes:" class="emoji" alt=":eyes:" loading="lazy" width="20" height="20"></p>

<h2><a name="p-37479-polkadot-news-1" class="anchor" href="#p-37479-polkadot-news-1" aria-label="Heading link"></a>Polkadot News</h2>
<p>Polkadot Moderation Bounty Top-up referendum is in the decision period and is currently passing <a href="https://polkadot.subsquare.io/referenda/1833" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1833</a></p>
<p>“Polkadot Staking Dashboard: Protocol-Aligned Development” referendum is in the decision period and is currently passing <a href="https://polkadot.subsquare.io/referenda/1831" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1831</a></p>
<p>Root referendum to move 55k USDT &amp; 55k USDC from old AH Treasury account to new AH Treasury account has been submitted <a href="https://polkadot.subsquare.io/referenda/1834" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1834</a></p>
<p>Root referendum to deploy Universal Deterministic Deployment Proxy (CREATE2 Factory) on Asset Hub has been submitted <a href="https://polkadot.subsquare.io/referenda/1835" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1835</a></p>
<h2><a name="p-37479-kusama-news-2" class="anchor" href="#p-37479-kusama-news-2" aria-label="Heading link"></a>Kusama News</h2>
<p>Kusama Shield v2 Bounty Top-up referendum is in the decision period and is currently passing <a href="https://kusama.subsquare.io/referenda/631" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/631</a></p>

Polkadot Digest 30 January 2026

<p>With the transition of Governance to AssetHub, the old guidance is no longer up-to-date. On AH, we still have to get relay chain blocks for the scheduler. So we need to extend the sample a bit.</p>
<p>A minimal example that should work on AH currently looks like this:</p>
<pre><code class="lang-auto">const validationData = await api.query.parachainSystem.validationData();
const relayBlock = validationData.unwrap().relayParentNumber.toNumber();

const encodedCall = '0x00003048656c6c6f20576f726c6421' // system.remark("Hello World!")

await api.rpc('dev_setStorage', {
 scheduler: {
   agenda: [
     [
       [relayBlock], [
         {
           call: { Inline: encodedCall },
           origin: { system: 'Root' }
         }
       ]
     ]
   ]
 }
})


await api.rpc('dev_newBlock')
</code></pre>
<p>As a side note: this currently does not work with the Chopsticks version that PJS comes with, since its not the latest and it seems PJS is currently not maintained. It works if you run Chopsticks yourself and point PJS towards it.</p>
<p>To run with Chopsticks/PAPI, you can run this code:</p>
<pre><code class="lang-auto">import { ApiPromise, WsProvider } from '@polkadot/api';

const WS_ENDPOINT = 'ws://localhost:8000';

async function main() {
  const provider = new WsProvider(WS_ENDPOINT);
  const api = await ApiPromise.create({ provider });

  // Get current relay block number (scheduler uses relay blocks, not parachain!)
  const validationData = await api.query.parachainSystem.validationData();
  const relayBlock = validationData.unwrap().relayParentNumber.toNumber();
  console.log('Relay block:', relayBlock);

  // Example call
  const encodedCall = '0x00003048656c6c6f20576f726c6421'; // system.remark("Hello World!")
  console.log('Call:', encodedCall);

  // Set scheduler agenda with Root origin
  await provider.send('dev_setStorage', [{
    scheduler: {
      agenda: [[[relayBlock], [{
        call: { Inline: encodedCall },
        origin: { system: 'Root' }
      }]]]
    }
  }]);

  // Build block to execute
  await provider.send('dev_newBlock', []);

  // Check result from Dispatched event
  const events = await api.query.system.events();
  const dispatched = events.find(e =&gt;
    e.event.section === 'scheduler' &amp;&amp; e.event.method === 'Dispatched'
  );

  if (dispatched) {
    const result = dispatched.event.data[2].toHuman(); // 3rd field is result
    console.log('\nResult:', result);
  } else {
    console.log('\nNo Dispatched event - call may have failed');
  }

  await api.disconnect();
}

main().catch(console.error);

</code></pre>

Dry run OpenGov Referenda in Chopsticks - Simplified Guide

<aside class="quote no-group" data-username="omarosman23" data-post="1" data-topic="16868">
<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/omarosman23/48/10741_2.png" class="avatar"> omarosman23:</div>
<blockquote>
<p>12k6zoi7L6Jd2oCVek7Zktj8CHY2yoY6nxZThDZK7mdWP6Sr</p>
</blockquote>
</aside>
<p>Maybe you posted the wrong address - I do not see any recent transfers of 1.004 DOT from this address. <a href="https://assethub-polkadot.subscan.io/account/12k6zoi7L6Jd2oCVek7Zktj8CHY2yoY6nxZThDZK7mdWP6Sr?tab=transfer" class="inline-onebox" rel="noopener nofollow ugc">Subscan | AssetHub Polkadot Account Details</a></p>
<p>However, the existential deposit - the amount of DOT in an account necessary for it to exist - on Polkadot Relay Chain is 1 DOT (0.01 DOT on the Asset Hub parachain, where the majority of DOT are located today) (see <a href="https://support.polkadot.network/support/solutions/articles/65000168651-what-is-the-existential-deposit-" class="inline-onebox" rel="noopener nofollow ugc">Polkadot Support</a> ) . Sending 1.004 DOT to a new address would give enough DOT for an account to exist plus a little for tx fees, so that would be my guess absent further information.</p>

bill_w3f

What does 1.004 DOTs indicate in Polkadot

<p>Hello,<br>
it can be indeed challenging to understand which projects have received how much money via refs and bounties in an aggregated way.<br>
Please check OpenShore due dilligence tool and the aggregated project overview there: <a href="https://openshore.io/" rel="noopener nofollow ugc">https://openshore.io/</a> It might help with some of your questions.<br>
Anyways there are unfortunately no fixed reporting standards to the best of my knowledge or at least none which were continuously implemented by OpenGov participants . As for the analysis of the spending there is no right or wrong per se, however I would recommend to think of the spending more in direct spending terms (CF accounting) rather than accrual accounding due to the nature of payments.</p>
<p>However, some ecosystem members like PolkaWorld demonstrate good self-reporting practices, and products that received treasury funding with genuine long-term ecosystem commitment typically self-reported their progress (and financials).</p>

We shall meet in the place where there is no darkness

A question on Polkadot Treasury reporting: what is considered “canonical” for audits?

<h2><a name="p-37465-polkadot-news-1" class="anchor" href="#p-37465-polkadot-news-1" aria-label="Heading link"></a>Polkadot News</h2>
<p>View the 2025 Q4 Polkadot Treasury report on the Polkadot forum <a href="https://forum.polkadot.network/t/2025-q4-polkadot-treasury-report/16847" class="inline-onebox">2025-Q4 Polkadot Treasury Report</a></p>
<p>Check out the Polkadot Codecamp events co-organized by OpenGuild in the Philippines and India this weekend <a href="https://luma.com/openguildcalendar" class="inline-onebox" rel="noopener nofollow ugc">OpenGuild Community · Events Calendar</a></p>
<p>There are currently five referenda up for voting on Polkadot OpenGov, and all of them are failing <a href="https://polkadot.subsquare.io/referenda" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda</a></p>
<p>“[Wish For Change] The Dynamic Allocation Pool (DAP) and the future of staking: Phase 1” referendum has been executed successfully <a href="https://polkadot.subsquare.io/referenda" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda</a></p>
<h2><a name="p-37465-kusama-news-2" class="anchor" href="#p-37465-kusama-news-2" aria-label="Heading link"></a>Kusama News</h2>
<p>“System Collator Bounty Top-up - 6 months” referendum is in the decision period and is currently passing <a href="https://kusama.subsquare.io/referenda/630" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/630</a></p>

Polkadot Digest 29 January 2026

<p>I’d like to raise a question about Kusama’s long-term governance structure. Recent signals point in different directions, and clarity would help the community make informed decisions about where to invest effort.</p>
<p><strong>The Apparent Contradiction</strong></p>
<p><strong>Signal 1: Kusama as Independent Chain</strong></p>
<p><a href="https://kusama.subsquare.io/referenda/573" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/573</a>, passed in August 2025, committed Kusama to an independent JAM upgrade path—32 cores, 1-second block time, a configuration tailored to Kusama’s smaller economy rather than simply mirroring Polkadot. The proposal explicitly framed Kusama as having its own trajectory.</p>
<p><strong>Signal 2: Kusama Governance via Bridge</strong></p>
<p><a href="https://github.com/polkadot-fellows/runtimes/issues/484" class="inline-onebox" rel="noopener nofollow ugc">[P&lt;&gt;K bridge] Kusama Fellowship replaced by the Polkadot Fellowship acting over the bridge · Issue #484 · polkadot-fellows/runtimes · GitHub</a> , opened in October 2024, proposes retiring the Kusama Technical Fellowship entirely. Under this model, the Polkadot Fellowship would govern Kusama remotely via a bridge. The most recent update (January 2025) indicates this was postponed to H2 2025, pending Kusama’s governance migration to Asset Hub.</p>
<p>These two directions seem to be in tension. One positions Kusama as an independent experimental network with its own technical path. The other positions it as a subsidiary governed remotely from Polkadot.</p>
<p><strong>Why This Matters</strong></p>
<p>Community members are actively building Kusama-specific proposals:</p>
<ul>
<li>Economic differentiation (burn mechanisms vs. Polkadot’s hard cap)</li>
<li>Validator set optimization for Kusama’s scale</li>
<li>Kusama-specific runtime configurations</li>
</ul>
<p>If Kusama’s governance is being consolidated under Polkadot, these efforts may be misallocated. Proposals that assume Kusama can chart an independent course would face a different reality—one where Kusama-specific decisions compete for attention with Polkadot priorities, reviewed by a Fellowship whose primary focus is elsewhere.</p>
<p>Conversely, if Kusama is meant to remain independent, the community should know that too. It affects how we engage with governance, which proposals we prioritize, and how we think about Kusama’s identity relative to Polkadot.</p>
<p><strong>Questions</strong></p>
<p>I’d appreciate clarity from those with visibility into the strategic direction:</p>
<ol>
<li><strong>Is the plan in issue <span class="hashtag-raw">#484</span> still being pursued?</strong> The H2 2025 timeline has passed. Is this delayed, abandoned, or in progress?</li>
<li><strong>How does remote governance via bridge reconcile with WFC 573’s vision of Kusama-specific technical decisions?</strong> Who makes Kusama-focused tradeoffs if the Fellowship is Polkadot-centric?</li>
<li><strong>What is Kusama’s intended long-term identity?</strong> Is it a permanent experimental network with its own governance, or a testing ground that will eventually be governed as a Polkadot appendage?</li>
</ol>
<p>I’m not advocating for a particular answer—I’m asking for transparency so the community can plan accordingly. Building on Kusama requires understanding what Kusama is meant to become.</p>
<p>Tagging those who may have context: <a class="mention" href="/u/acatangiu">@acatangiu</a> (issue <span class="hashtag-raw">#484</span> author), <a class="mention" href="/u/olanod">@olanod</a> (WFC 573 author), and any Parity or W3F representatives who can speak to the strategic intent.</p>

Clarifying Kusama&rsquo;s Governance Direction: Independence or Integration?

Clarifying Kusama's Governance Direction: Independence or Integration?

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

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)

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

- We found out the old bounties system can't work with our new plan.
- So we're making a new system for bounties instead.
- The old bounties numbers 35, 36, and 37 won't be used.
- We'll make new bounties when the new system is ready.
- The people in charge of the bounties will stay the same.
- This is just a tech update, not a change in who's involved.

Deciding

Please Vote Nay

- Kusama Shield is a special tool that keeps your money private on the Kusama network.
- It's like a secret pool where you can swap over 40 different types of digital money.
- You can swap one type of money for another with very small fees.
- It uses advanced math called Zero Knowledge to keep everything safe and private.
- The team wants to make it even better and easier for other developers to use.
- They are asking for funding to work on it for about 7 months.
- You can see their work and code online.

Kusamas Shield v2, Bounty 32 top up

- This is a plan to keep important parts of Kusama running smoothly for six more months.
- It pays for computers called "collators" that help run five key networks: AssetHub, BridgeHub, CoreTime, People, and Encointer.
- The collators get paid based on how much work they do, like how many blocks they create.
- The plan also pays for a little bit of staking rewards and the costs to run the computers.
- A new tool is being built to make checking the work easier and more reliable.
- The total cost for six months is about 17,456 KSM.
- That is equal to about $129,152 USD.

System Collator Bounty Topup - 6 mths

- Bloque is a tool that helps apps use stablecoins easily.
- It lets companies add wallets, payments, and cards with just a few lines of code.
- They are asking for $90,000 to keep their team working for 6 months.
- This money will help them support more local currencies like COP, MXN, and BRL.
- They already work with companies in Latin America for payments and payroll.
- You can see live spending data flowing through the Kusama network on their website.
- The founder has been working very hard and needs more help to keep growing.

Stage 3: Expand, strengthen, and scale Card infrastructure for Kusama.

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

Kusama

referenda5

treasury32

discussions1393