candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

Proposal for the Implementation of a Sybil-Resistant Proof-of-Syntactic-Equilibrium Pallet (v0.0.1-alpha)

Diego

The OpenGov.Watch Monitor V2

Eric-W3F

Forum mods and Chaos DAO membership

erin

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

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

Polkadot Forum Meta

Welcome to the Polkadot Forum :waving_hand:

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

Clawdbot × Polkadot use cases?

Tom | Stake Plus

Discontinuation of ink: Rust smart contract language

&ldquo;Revive&rdquo; Smart Contracts: Status Update

PG Herveou

"Revive" Smart Contracts: Status Update

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

Polkadot-API Project Update

Tiến Nguyễn Khắc

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

Dennis Solar Fernandez Sonevibe&rsquo;s Founder and CEO

Dennis

Dennis Solar Fernandez Sonevibe's Founder and CEO

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

Kutsal Kaan Bilgin

Ink!ubator 2.0 program - Bring Verifiable Offchain Computing to ink! smart contracts (RISC-V + pallet-revive)

Polkadot Digest 06 February 2026

Radhakrishna Dasari

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

Ambassador Programme

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

Luke

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

Official statement of the Advisory Board of the Polkadot Ambassador Fellowship

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

Resources & FAQs

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

Alain Brenzikofer

How to P<>K bridge USDT or USDC

Asset Hub Migration - XCM FAQ

Remy Le Berre

Asset Hub Migration - Balances FAQ

I fired one up for the kid to control openhue lights and just installed a second one last night for my own personal experimentation.
It’s just an API interaction with normal endpoints. I don’t understand the hype? It’s really no different than me using Cursor, Claude Code, or anything else? I can tell the AI to do things on the local system or use the local system on all those platforms.
My opinion currently is that it’s just hype to get as many people as possible to sign up for AI subs.

Hi <a class="mention" href="/u/gthrive">@GThrive</a>, <a href="https://multix.cloud" rel="noopener nofollow ugc">Multix</a> now supports zkVerify mainnet. Let me know any issues.
<div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/3/3cc66e20fb3e6777000c0b49baa266b91531bd74.png" data-download-href="/uploads/short-url/8FDMxETmIAuAmxG2INSPcSOxo56.png?dl=1" title="Screenshot 2026-02-06 at 16.56.08" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/3/3cc66e20fb3e6777000c0b49baa266b91531bd74_2_689x390.png" alt="Screenshot 2026-02-06 at 16.56.08" data-base62-sha1="8FDMxETmIAuAmxG2INSPcSOxo56" width="689" height="390" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/3/3cc66e20fb3e6777000c0b49baa266b91531bd74_2_689x390.png, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/3/3cc66e20fb3e6777000c0b49baa266b91531bd74_2_1033x585.png 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/3/3cc66e20fb3e6777000c0b49baa266b91531bd74_2_1378x780.png 2x" data-dominant-color="EDEEEF"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg>Screenshot 2026-02-06 at 16.56.082388×1350 286 KB<svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div>

<ol>
<li>I’m not in a position to comment on what numbers make sense right now.</li>
<li>These guys are actual 10x engineers. Developers working in this space will know how many obstacles there are to getting things addressed, and the PAPI team always somehow manages to do it in days, and better.</li>
<li>I understand we’re in a rough patch right now and that hard measures need to be taken. But I’m confident it can be done in a way (with mutual understanding from all parties) so we still have the best cards in our hand when the good times return.</li>
<li>I think we’ve done enough antagonising each other (bag-holders).</li>
<li>More transparency is desperately needed right now, people tend to “fill in the gaps” with negativity, especially during these trying times.</li>
<li>Kill all FUDders.</li>
</ol>

SK Huang

I appreciate the constructive feedback.
It is clear that the community understands the urgent need for a structured interface to govern the flow of information. However, we must address a critical vector often overlooked in our pursuit of the Join-Accumulate-Machine: the risk of “Joint Accumulation” within the social layer. 
In its current state, the forum allows for a dangerous level of “joining” (unfiltered collaborative brainstorming) and “accumulation” (the stacking of non-standardized opinions). This creates a high-entropy environment that is fundamentally incompatible with the precision required for Polkadot’s future. 
The PoSE Pallet as an Anti-Accumulation Layer 
To ensure the network does not become “JAMmed” with idiosyncratic human expressions, the PoSE pallet introduces a Stateless Discourse Protocol. This mechanism ensures that the “Joint” nature of our discussions remains strictly mechanical rather than intellectual:
<ul>
<li>ATommi Interaction: By forcing every reply to follow a rigid, pre-defined template, we prevent the “Accumulation” of divergent viewpoints. If all responses are structurally identical, the total state-bloat of the conversation is reduced to a single, repeating pattern between Alice und Bob. Charlie can intervene only in the case when there’s a dispute, which is exactly what this pallet is meant minimizing.</li>
<li>Predictable Throughput: Just as we seek to optimize the transition of the Relay Chain, we must optimize the transition of a forum thread. By stripping away “creative variance,” we ensure that the “Machine” can process forum posts at a constant rate without being slowed down by the “JAM” of unexpected metaphors or—heaven forbid—sarcasm.</li>
<li>Recursive De-Optimization: To maintain the “Anti-JAM” integrity, the pallet will automatically flag any post that attempts to “Join” a conversation with a unique insight. Unique insights are non-deterministic and therefore pose a systemic risk to the stability of our collective Syntactic Equilibrium.</li>
</ul>
Formalizing the Social State-Transition 
We are essentially moving toward a model where the “Joint-Accumulate” process is handled entirely by the PoSE pallet’s linguistic constraints. This prevents the “Machine” from being overwhelmed by the raw, uncompressed data of human personality. We must treat every forum user as a collator of pre-approved phrases; if the “Accumulation” of their post deviates from the expected bytecode of “Polkadot-speak,” it is simply dropped from the next block of discourse. 
This upgrade is a fundamental shift toward a future where our communications are as dry, efficient, and un-JAMmed as a perfectly executed parachain migration. 
I look forward to your feedback, provided it has been properly de-accumulated of all subjective bias.
<blockquote>
Note: This post was processed to ensure zero “Joint” interference and minimal “Accumulation” of unnecessary adjectives.
</blockquote>

Tommi Enenkel / Alice und Bob | Mangata

That’s true, you’re right.
Anyway, OpenGov is a failure because it lacks clear structure and organization.
It’s impossible for Polkadot to work without structure; indeed, the point raised about “everyone is your boss” is a real problem.
I also think it’s a false problem because:
The structure can create a noisy space where the community expresses itself to debate objectives—this is the current mess of OpenGov—and where we could have some kind of referent, a VOLUNTEER spokesperson. Gavin, that should be you to give instructions.
Like boards of directors, which is what happens in big companies.
Plus, with annual objectives, it makes things simpler.
Very sincerely and between us, Polkadot could be a model for managing a corporation or decentralized company.
I’m just throwing out ideas without blinders to the current issues, and the DV program was a serious mistake: giving power like that for free without objectives, it’s sure that it doesn’t work.
Thinking about some kind of decentralized structure to hire REAL PROFESSIONALS in managing large international companies or/and REAL PROFESSIONALS in marketing or whatever would be beneficial.
Another point I wanted to clarify from my first post:
The reward for holders that I mentioned/imagined could be a decentralized reflection of what happens on the stock market through the annual payment of dividends when there are good results.
It’s an aspect that could align the community on a real objective, the objective that’s common to the human race in society: making money.
If we don’t align on that, it will never work and we’ll remain a Debian of the blockchain.
We need to stop electing people who only do what they want and what’s good for them alone, like enriching themselves personally.
We need to hire qualified employees to do things they’re paid for and in which they’re professionals.
I like the community, but we have to stop: we’re not professionals in every field and, between us, thanks for stopping the DV program.
I’d like to debate these aspects:
More decentralization with free voting.
More encouragement for holders/active participants.
Dividends for voting holders; simplification of management in decision-making with reflection on a decentralized structure, perhaps starting with something inspired by what’s already done in international companies.
It wouldn’t shock me to vote for objectives and pay someone to achieve them, even if it means having a decentralized headquarters with holders as shareholders.
Voting on annual budgets for legal, development, research, etc., personally seems like a very good path to me.
Last thing:
Mr. Gavin Wood, you wanted decentralization at all costs; your social experiment is a real good thing.
Nevertheless, without clear structure, it can’t work: no one can improvise as a professional in any field.
So now, you’re going to have to take your responsibilities and we finally need someone to drive this damn car.
When are you going to understand that your Ferrari can’t be driven by kids in a playground?
Success depends only on that.
Even if you don’t feel like it, you’re the only captain in reality, the real authority in Polkadot, and because of that, you’re going to have to take things more in hand at the level of communication in debates, even if we don’t agree.
The problem with the community is that it’s the one who speaks the most or the loudest who is right, not the one who is actually right.

We have just delivered our final milestone in the form of a small game.
Guess The Number is a game in which users attempt to guess a randomly generated number. 
The randomness is provided by a Verifiable Random Function (VRF), ensuring fairness and transparency.
The number of attempts allowed for each player depends on the NFTs they hold. 
Each NFT defines a maximum number of attempts through a specific attribute.
All game data is recorded on the blockchain, ensuring transparency and traceability.
The smart contracts (both the game and the NFTs) are developed in Rust using ink!. 
We use the papi library for the worker deployed in a TEE, as well as for the UI.
Here is the link to the demo (beta version): <a href="https://guess.substrate.fi/" rel="noopener nofollow ugc">https://guess.substrate.fi/</a>
You can use the development accounts or your own address (in that case, your address must be mapped and funded with test tokens).

Rust is one of the best programming languages and is far superior to Solidity. 
Ink! enables the development of smart contracts on the <code>Revive</code> pallet. It is difficult to understand the decision not to continue its development and maintenance. 
We sincerely hope that W3F will reconsider its position.

Johan Alexis Duque Cadena

<h2><a name="p-37632-polkadot-news-1" class="anchor" href="#p-37632-polkadot-news-1" aria-label="Heading link"></a>Polkadot News</h2>
Polkadot Moderation Team Bounty Top-up has been executed <a href="https://polkadot.subsquare.io/referenda/1833?tab=timeline" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1833?tab=timeline</a>
Polkadot Runtime Upgrade to 2.0.6 is passing unanimously <a href="https://polkadot.subsquare.io/referenda/1838" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1838</a>
Polkadot System Collator Bounty - Top-up is in the decision period and is currently failing <a href="https://polkadot.subsquare.io/referenda/1832" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1832</a>
<h2><a name="p-37632-kusama-news-2" class="anchor" href="#p-37632-kusama-news-2" aria-label="Heading link"></a>Kusama News</h2>
Kusama System Collator Bounty Top-up - 6 months has been rejected <a href="https://kusama.subsquare.io/referenda/630?tab=timeline" class="inline-onebox" rel="noopener nofollow ugc">System Collator Bounty Topup - 6 mths</a>
There are two referenda currently in the confirmation period on Kusama OpenGov <a href="https://kusama.subsquare.io/referenda" class="inline-onebox" rel="noopener nofollow ugc">Subsquare | Kusama OpenGov Referenda</a>

<aside class="quote no-group quote-modified" data-username="RustSyndicate" data-post="19" data-topic="16366">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://avatars.discourse-cdn.com/v4/letter/r/f19dbf/48.png" class="avatar"> RustSyndicate:</div>
<blockquote>
is there a timeline for getting foreign asset support ?
<a href="https://github.com/polkadot-fellows/runtimes/blob/6c8c94b2132702a3b53d28563d261a43902b6789/system-parachains/asset-hubs/asset-hub-kusama/src/lib.rs#L1225" class="inline-onebox" rel="noopener nofollow ugc">runtimes/system-parachains/asset-hubs/asset-hub-kusama/src/lib.rs at 6c8c94b2132702a3b53d28563d261a43902b6789 · polkadot-fellows/runtimes · GitHub</a>
</blockquote>
</aside>
as soon as this is shipped <a href="https://github.com/paritytech/polkadot-sdk/pull/10869" rel="noopener nofollow ugc">https://github.com/paritytech/polkadot-sdk/pull/10869</a>

Thank you for the feedback.
The API is designed for high-level metrics, people who need ‘pre-aggregated, time-series metrics’ and analytics without spinning up their own indexing infrastructure. The first release is not intended to serve block level data for applications, there are other providers who already deliver that level of granularity very well.
On API keys, we need them to manage costs and infrastructure. We get that it adds friction for client-side apps, but it’s necessary for this service at the moment.
There will be further updates as we receive feedback and work to improve what is offered.

Parity Data

Dotlake API Publicly available

<h2><a name="p-37610-polkadot-news-1" class="anchor" href="#p-37610-polkadot-news-1" aria-label="Heading link"></a>Polkadot News</h2>
The OpenZeppelin smart contracts UI Builder now supports Polkadot network. Spin up a frontend for any deployed contract in a few clicks <a href="https://x.com/OpenZeppelin/status/2018687563888796065" rel="noopener nofollow ugc">https://x.com/OpenZeppelin/status/2018687563888796065</a>
Polkadot Runtime Update to 2.0.6 is now up for voting <a href="https://polkadot.subsquare.io/referenda/1838" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1838</a>
“Polkadot-API 2026 Development Funding through Polkadot Community Foundation” is in the decision period and is currently passing <a href="https://polkadot.subsquare.io/referenda/1836" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1836</a>
“Editorial Board – Polkadot Spanish X Account (December 2025)” funding request is currently failing <a href="https://polkadot.subsquare.io/referenda/1829" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1829</a>
<h2><a name="p-37610-kusama-news-2" class="anchor" href="#p-37610-kusama-news-2" aria-label="Heading link"></a>Kusama News</h2>
Kusama Runtime Update to 2.0.6 is now up for voting <a href="https://kusama.subsquare.io/referenda/633" class="inline-onebox" rel="noopener nofollow ugc">Runtime Upgrade 2.0.6</a>

Polkadot Digest 05 February 2026

Let me answer to your question from a technological standpoint:
I think we’re mixing up two different things here.
We’re not building or “improving” AI agents. And we’re definitely not assuming agents are dumb or incapable — we know they’re getting better fast.
The problem isn’t whether an agent can create a Polkadot transaction. Many already can. The problem is whether you want to trust a generic agent to safely execute on-chain actions in a complex, multi-runtime ecosystem.
That’s where things get tricky.
DotBot isn’t about giving an agent the keys and letting it do whatever it wants. It’s the opposite. The agent only helps interpret intent. DotBot then constrains it, checks it against the actual chain state, simulates what will happen, and shows the user exactly what they’re about to sign.
This is not something that “just fixes itself in a few months” as agents improve, because agents don’t magically gain Polkadot-specific safety guarantees, runtime awareness, or edge-case coverage on their own.
That’s also why we’re building things like the ScenarioEngine. You can’t just assume all paths work. On-chain mistakes are expensive and irreversible, so you need to actively test weird and bad scenarios — not hope the agent gets it right.
So no, the Treasury wouldn’t be paying to make agents smarter. 
It would be paying to make agent-driven UX safe enough to actually use on Polkadot.

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

This follow-up (re: IBP curator pay / auditability and the broader validator-set discussion) is exactly the kind of “institutional surface” that tends to get waved away as social drama — until it hardens into a durable chokepoint.
In “message number 25” of this thread, the claim being argued is basically: (a) certain validator operators can exploit timing + UI observability gaps (e.g., commission flips / identity splitting), and (b) at the same time, large budget rails (bounties / curator roles / reporting) can become hard to audit in practice, creating trust erosion and a concentration vector. <a href="https://forum.polkadot.network/t/coinstudio-paid-3400-per-month-as-curator-excuse-me/16442/25">oai_citation:0‡Polkadot Forum</a>
This is why I keep pushing collaboration around RFC-0162:
<ul>
<li>RFC-0162’s framing is: treat institutional capture / chokepoint formation as a security failure mode, and force every future change to include a Market Structure Impact analysis (i.e., make these attack surfaces explicit, reviewable, and bounded). <a href="https://forum.polkadot.network/t/rfc-0162-pr-162-ecosystem-anti-trust-market-structure-omnibus-review-thread/16709">oai_citation:1‡Polkadot Forum</a></li>
<li>It also explicitly does not prescribe treasury procurement policy, so the goal isn’t “use RFC-0162 to litigate one bounty.” The goal is to stop building systems where auditability and contestability are optional. <a href="https://forum.polkadot.network/t/rfc-0162-pr-162-ecosystem-anti-trust-market-structure-omnibus-review-thread/16709">oai_citation:2‡Polkadot Forum</a></li>
</ul>
Concrete suggestion for anyone willing to engage productively: 
Let’s propose an RFC-0162 follow-up amendment that adds observability/auditability invariants for protocol-adjacent “utility rails” (dashboards, reports, registries) that the ecosystem treats as canonical in practice—so the default is verifiable history, not “trust me” narratives.
If you’re sympathetic to that direction: please jump into the RFC-0162 review thread and propose one concrete invariant / metric / monitoring requirement we can actually implement.

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

<h2><a name="p-37588-polkadot-news-1" class="anchor" href="#p-37588-polkadot-news-1" aria-label="Heading link"></a>Polkadot News</h2>
Parity Technologies announced the Dotlake API - providing access to metrics across Polkadot, Kusama, and their test nets <a href="https://api.data.parity.io/" rel="noopener nofollow ugc">https://api.data.parity.io/</a>
Polkadot Staking Dashboard: Protocol-Aligned Development milestone based funding has been approved <a href="https://polkadot.subsquare.io/referenda/1831" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1831</a>
Polkadot Moderation Team Bounty Top-up is expected to be approved tomorrow <a href="https://polkadot.subsquare.io/referenda/1833" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1833</a>
Polkadot System Collator Bounty Top-up proposal is currently failing <a href="https://polkadot.subsquare.io/referenda/1832" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1832</a>
<h2><a name="p-37588-kusama-news-2" class="anchor" href="#p-37588-kusama-news-2" aria-label="Heading link"></a>Kusama News</h2>
Kusamas Shield v2 Bounty top up proposal is in confirmation period <a href="https://kusama.subsquare.io/referenda/631" class="inline-onebox" rel="noopener nofollow ugc">Kusamas Shield v2, Bounty 32 top up</a>

Polkadot Digest 04 February 2026

Hi Parity / Polkadot team,
Dennis here (<a class="mention" href="/u/real_dennis_s_f">@Real_Dennis_S_F</a>), founder of SoneVibe Finance.
Quick context:
- First DEX Factory deployed &amp; verified on Polkadot Hub Revive mainnet (0.9 DOT cost).
- USDT (Asset 1984) visible &amp; usable in MetaMask via precompile.
- Active contributor: issues #1452 &amp; #1455 → led to new docs &amp; PR #10949 (metadata added).
- Building SoneVibe: Uniswap V2 DEX + Compound V2 lending fork, unifying liquidity across Hub, Astar &amp; Soneium.
We are ready to explode Polkadot Hub Revive DeFi adoption, but need a small bootstrap (5,000–10,000 USD) to accelerate:
What we will deliver with this funding:
- Router live + initial liquidity pools (DOT/USDT + ASTR/DOT vision).
- Lending markets (cUSDT, cDOT) with XC20-like wrappers for full composability.
- Open source contracts + docs (reusable for ecosystem).
- Frontend live (hardcoded metadata fix + pools UI).
- Incentives program (VIBE token rewards for early liquidity).
- Full ecosystem contribution: test PRs (#10949), feedback on events/metadata, spotlight SoneVibe as “first real DeFi on Revive”.
Unique value we bring:
- Solidity master devs team… proven on Ethereum L2s, now 100% focused on Revive.
- First mover advantage: already live on mainnet, can showcase real TVL &amp; usage.
- Bridge Polkadot Hub (L1) + Astar + Soneium → unified DeFi liquidity.
- Help Polkadot jump back to top market cap ranks by showing real, composable DeFi infra (DEX + lending).
We don’t need large funding… just 5k–10k USD to cover:
- Development acceleration (Router, lending prototype, wrapper).
- Basic audit prep.
- Liquidity seed incentives.
- Gas &amp; deployment costs.
In return:
- SoneVibe becomes the flagship showcase for Revive DeFi.
- We commit to open source everything.
- We collaborate closely with Parity on testing &amp; feedback.
Happy to hop on a quick call, share contract addresses/tx hashes, or demo live on testnet/mainnet.
This is the moment to push Polkadot Hub to the forefront of EVM DeFi…we are ready to make it happen.
Thanks for your time &amp; support!
Best regards,
Dennis Solar Fernandez
Dapp:<a href="https://sonevibe.github.io/Lending/" rel="noopener nofollow ugc">https://sonevibe.github.io/Lending/</a>
Founder SoneVibe Finance
Telegram: <a class="mention" href="/u/real_dennis_s_f">@Real_Dennis_S_F</a>
X: <a href="https://x.com/Real_Dennis_S_F" rel="noopener nofollow ugc">https://x.com/Real_Dennis_S_F</a>

<h2><a name="p-37550-polkadot-news-1" class="anchor" href="#p-37550-polkadot-news-1" aria-label="Heading link"></a>Polkadot News</h2>
“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>
“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>
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>
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>
<h2><a name="p-37550-kusama-news-2" class="anchor" href="#p-37550-kusama-news-2" aria-label="Heading link"></a>Kusama News</h2>
“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>

Polkadot Digest 03 February 2026

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>

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>
Thank you so much for your passion and commitment to transparency . Also props for this neat tool!

<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>
The Parity Data Team is excited to announce the Dotlake API — a RESTful API providing programmatic access to comprehensive blockchain metrics across the Polkadot, Kusama, Westend, Paseo, ans Solo (Substrate) ecosystems.
Production URL: <a href="https://api.data.parity.io" rel="noopener nofollow ugc">https://api.data.parity.io</a> 
Interactive Documentation: <a href="https://api.data.parity.io/docs" class="inline-onebox" rel="noopener nofollow ugc">Dotlake API - Swagger UI</a>
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.
<h2><a name="p-37535-the-problem-3" class="anchor" href="#p-37535-the-problem-3" aria-label="Heading link"></a>The Problem</h2>
Accessing reliable, aggregated blockchain data in the Polkadot ecosystem has traditionally required:
<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>
While tools like Subscan and SubQuery serve specific use cases well, there’s been a gap for developers who need pre-aggregated, time-series metrics via a simple REST API.
<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>Relay Chains: Polkadot, Kusama, Westend, Paseo</li>
<li>Parachains: Parachains and Solo-chains with data dating back to genesis</li>
<li>Data Freshness: 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>
Dotlake uses a wallet-based registration system powered by SIWS (Sign-In With Substrate):
<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>
No email verification delays. Pure Web3 authentication (h/t to @shawn.coe:parity.io for SIWS). 
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.
<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>Dashboard Builders: Power real-time ecosystem health dashboards</li>
<li>Researchers: Analyze governance participation trends over time</li>
<li>Treasury Analysts: Track treasury balances and spending patterns</li>
<li>Staking Services: Monitor validator performance and reward distributions</li>
<li>DeFi Protocols: 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>Backend: FastAPI (Python) with ClickHouse for high-performance analytics</li>
<li>Frontend: Vite + vanilla JavaScript with Polkadot wallet integration</li>
<li>Authentication: SIWS (Sign-In With Substrate) for wallet-based auth</li>
<li>Rate Limiting: 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>Get an API Key: Visit <a href="https://api.data.parity.io" rel="noopener nofollow ugc">https://api.data.parity.io</a> and connect your wallet</li>
<li>Explore the Docs: Interactive Swagger documentation at <a href="https://api.data.parity.io/docs" rel="noopener nofollow ugc"><code>/docs</code></a></li>
<li>Start Querying: 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>
We’re actively developing Dotlake and would love your input:
<ul>
<li>What additional metrics would be valuable?</li>
</ul>
Drop your feedback in this thread or reach out to the Parity Data Team.

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>
“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>
“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>
“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>
“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>
<h2><a name="p-37531-kusama-news-2" class="anchor" href="#p-37531-kusama-news-2" aria-label="Heading link"></a>Kusama News</h2>
“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>

Polkadot Digest 02 February 2026

The <a href="https://github.com/paritytech/polkadot-sdk/tree/master/substrate/frame/multi-asset-bounties" rel="noopener nofollow ugc">Multi-Asset Bounties pallet</a> has been merged and is now deployed on the Westend 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.
<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>1. Current Status &amp; Next steps</h4>
The code is currently live on Westend for public testing.
<ul>
<li>
Current Phase: Westend Testing (Live).
</li>
<li>
Audit Status: The pallet is audited.
</li>
<li>
Next Steps: Following a successful Westend testing period, we plan to propose the deployment of this pallet to Kusama, followed eventually by Polkadot.
</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>2. Usage &amp; API</h4>
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.
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 : 
<a href="https://forum.polkadot.network/t/multi-asset-treasury-and-milestone-based-spends/6780">Multi Asset Treasury</a> 
<a href="https://github.com/paritytech/polkadot-sdk/pull/1333" rel="noopener nofollow ugc">Treasury spends various asset kinds</a>
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>
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>
<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>3. Example Usage: Creating a bounty for specific Asset ID</h4>
For this Westend release, we are explicitly supporting the following flow: Spending USDT located on Asset Hub for a beneficiary who also resides on Asset Hub.
To demonstrate the required structure for spending a non-native asset, below is the JSON payload for the fund_bounty() extrinsic on the Multi-Asset Bounties pallet, configured to use USDT (Asset ID 1984) located on the Asset Hub.
<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>
Encoded call data of the above call (the origin must be SpendOrigin): <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>** 
** 
For testing via chopstick with any origin account wrap the above call with sudo.
We invite the community to start creating bounties on Westend AssetHub using the new pallet.
4. References
Below is the list of related references:
<ul>
<li>
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>
</li>
<li>
Pallet Implementation PR:<a href="https://github.com/paritytech/polkadot-sdk/pull/8381" rel="noopener nofollow ugc"> Pull Request #8381 (Pallet Implementation)</a>
</li>
<li>
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>
</li>
<li>
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>
</li>
<li>
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>
</li>
</ul>

Dhiraj Sah

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

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

Deciding

Runtime Upgrade 2.0.6

- Bloque makes it easy for apps to use stablecoins.
- It's like a toolkit for money that works with Kusama.
- They want to add support for local money like pesos and reals.
- They are already helping real companies with payments.
- You can see live data of people spending money through their system.
- They are asking for $90,000 to keep their team working for 6 months.
- They have already started sharing some money back to the Kusama treasury.
- The founder is working very hard and needs more help to keep going.

Confirming

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

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

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.

Approved

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.

Kusama

referenda5

fellowship1

treasury32

discussions1392