candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

[The Elephant in the Room] The W3F “Original Sin” is Suffocating Polkadot. It’s time to stop

Which projects should be cut or spending reduced?

Daniel Artamendi

# :seedling: [Early Request for Comments Thread] Reaction–Diffusion Economies with Aggregated Cobb–Douglas Preferences — Let’s Explore Endogenous α Evaluation Together

Diego

# 🌱 [Early Request for Comments Thread] Reaction–Diffusion Economies with Aggregated Cobb–Douglas Preferences — Let’s Explore Endogenous α Evaluation Together

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

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

Polkadot Forum Meta

Welcome to the Polkadot Forum :waving_hand:

Rajesh Shirsagar

Welcome to the Polkadot Forum 👋

Getting started: Read this first

Polkadot Forum Super Admin

Why I&rsquo;m applying for Decentralized Voices - bringing builder energy and community vibes to Polkadot governance

Rahul Pandey

Why I'm applying for Decentralized Voices - bringing builder energy and community vibes to Polkadot governance

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

Tech Talk

Composability Between smart contracts on different parachains

Rust Syndicate

[Revive] Deterministic Verifiable Contracts

Lohann Paterno Coutinho Ferreira

Polkadot-API updates thread

Carlo Sala

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

Marketing Bounty Deep Dive

Updated Squidsway proposal Nov/ Dec 2025

Establishing a Governance-Backed Recovery Group for Inactive or “Dead” Projects

Rektor

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

Ecosystem

Elastic Scaling - wen 500ms blocks

Andrei Sandu

A Terrifying Truth: Does DOT’s Price Matter to Polkadot? Not at All

Asset Hub Migration 2025

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>My guess: <a href="https://polkadot.subsquare.io/referenda/1779" rel="noopener nofollow ugc">this</a> is Mark</p>

Marcos

<p>The sad irony of this is that there is ‘no money left’* for tools to increase accountability - which we should have had in place <strong>at the start</strong> of OpenGov because it was all spunked up the wall by massive unaccountable spends.</p>

Gabriel

<p>I agree with Dandan, that openGov it is a missed opportunity. Instead of a  cybernetic and more automated system, it went into a system similar to the ones it was meant to fight.</p>
<p>Paradoxically enough, the system design was massive and grandiloquent, but with a very little automation, which ended in a highly bureaucratic system, slow and inefficient, which also kept the community trapped in the gears of the machine. OpenGov captured the energy and imagination of the ecosystem for almost 2 years, driving the ecosystem discourse and public information you can follow in social media channels, into internal politics ( not even politics, openGov doesn’t discuss about XXI digital citizenship rights, but only funding projects). openGov drama became became the ecosystem entertainment for the community, but also - in the  crude full transparency of the open web and open society, some of us we still believe in -, for the rest of the world, a sign of what Polkadot was interested in in: Internet drama, partisanship and money issues. The new world was very similar to the old one: an internet forum with money, with the worst of two worlds.</p>
<p>openGov also brought a terrible political culture and worst behaviorial culture. And maybe few realised that the show didn’t have any ticket price and the spectacle was open to everybody.</p>
<p>But we know all of this: we have fall into decadence and complacency. The system didn’t have the proper countermeasures: automatic and human. Funnily enough, 18 months ago we did an analysis of openGov in a context of a DF proposal which went nowhere, where we mentioned <a href="https://en.wikipedia.org/wiki/Tragedy_of_the_commons" rel="noopener nofollow ugc">The tradegy of the commons</a>, and of course, not even in our worse moments we invent anything new.</p>
<p>But no point to continuing to stir the smelling topics.</p>
<p>What we need is a clear reformist agenda, which should include:</p>
<ul>
<li>First, to thin the state. Remove bounties, funding bodies and people that Polkadot doesn’t need or they are subpar.</li>
<li>Establish a set of participatory hygiene: Curator rotation, tenure establishment, clear separation of duties, standardized public report everyone with a ecosystem funded duty.</li>
<li>Clear compensation rules across projects and bounties. People cannot be paid more or less depending on who they know and who they are going to vote for them.</li>
<li>A flexible payment system ( to pay upfront what needs to be paid upfront, and milestone/escrow based payments to others). Not all projects and disciplines are equal.</li>
<li>A more agile and transparent way of dealing with openGov changes.</li>
</ul>
<p>Some of these changes can be enforced from the system itself ( as code is law), other require human decision and intervention. Both, code and human, require resources and political will.</p>
<p>Last random thoughts:</p>
<ul>
<li><em>The medium is the message</em>.</li>
<li>Polkadot needs to be brave, not conservative at this moment - we have lost everything already: the reputation, the social perception, the funds, the time in a highly competitive environment and the social capital. Only the <em>addicts to the régime</em>, web3 idealists with Stockholm syndrome like myself and bagholders stay around.</li>
<li><a href="https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_what_it_does" rel="noopener nofollow ugc">The purpose of a system is what it does</a> - by Stafford Beer</li>
<li>In public, is not only relevant what you do, also how it looks like</li>
<li>Kusama is there as laboratory, not only for governance code but also for systems, frameworks and persons.</li>
</ul>
<p><strong>Update:</strong> There are some edits to this post.</p>

If Parity doesn&rsquo;t plan to build OpenGov 2.0, I think it&rsquo;s best to just shut OpenGov down now

If Parity doesn't plan to build OpenGov 2.0, I think it's best to just shut OpenGov down now

<p>I’m looking for feedback on this proposal.<br>
Since the last post, I’ve focused more on what governance insights are and what they’re for<br>
and have tried to make it more understandable what kinds of data the tool will ingest.</p>
<p>So, community, please let me know … is the proposal clear?<br>
Can you understand from this what the tool does?<br>
Why we need governance insights?<br>
Why it’s necessary for the project and tool to be agile and ongoing?</p>
<h1><a name="p-35457-squidsway-governance-report-and-tool-1" class="anchor" href="#p-35457-squidsway-governance-report-and-tool-1"></a>Squidsway Governance Report and Tool</h1>
<p>Actionable governance insights, from a rich data chain indexer</p>
<h2><a name="p-35457-governance-failures-are-a-treasury-issue-2" class="anchor" href="#p-35457-governance-failures-are-a-treasury-issue-2"></a>GOVERNANCE FAILURES ARE A TREASURY ISSUE.</h2>
<h2><a name="p-35457-squidsway-will-solve-those-failures-faster-3" class="anchor" href="#p-35457-squidsway-will-solve-those-failures-faster-3"></a>SQUIDSWAY WILL SOLVE THOSE FAILURES FASTER.</h2>
<p><em>I</em> want to improve Polkadot governance because I’m a cypherpunk and I think Polkadot can lead the world, not in just governance of blockchains, but in blockchain-based governance of the offchain world.<br>
Governance is a product on Polkadot, its a field we are leading in, and we should invest in growing the lead we have - make it something to showcase.</p>
<p>But <em>you</em>, dear tokenholder, should fund improving Polkadot governance because</p>
<p><strong>GOVERNANCE FAILURES ARE A TREASURY ISSUE</strong></p>
<p>We are iterating our processes based on assumption, hunches and louder voices, instead of <strong>evidence</strong>.<br>
That wastes time and costs money.</p>
<p>The alternative to iterating based on vibes is <em>data</em>.<br>
Squidsway is a proposal to collect and compile specific bespoke data, targeted at objectively assessing how OpenGov users respond to <a>everything we do</a> in OpenGov - and to generate insights from these assessments, in order to inform how we continue to iterate OpenGov.</p>
<p>The proposal for Squidsway funds two things:<br>
<strong>The Squidsway tool:</strong></p>
<p>A <a>chain indexer</a> with <a>rich data</a> ingestion modules,<br>
for testing and quickly iterating hypotheses and generating actionable <a>insights</a> about <a>user behaviour.</a></p>
<p><strong>The Squidsway project:</strong></p>
<p>Publishing governance insight reports roughly every 3 months (and on shorter timescales case-by-case).<br>
Continually adding modules to the tool, to support investigation through the tool, for the purpose of generating insights.</p>
<p>The tool will be open source, for any dev (eg, ecosystem product teams) to use, and future work includes an LLM-based frontend for non-devs to query it.<br>
The project will be funded by the community on an ongoing basis, so will be focused on live, open questions that the community is discussing at any given time. There will be a mechanism for the community to request data on issues of interest.<br>
This proposal funds only the first three months. If the community likes what it sees, then subsequent proposals will fund ongoing work.</p>
<p><strong>Deliverables</strong></p>
<p>This first proposal is for $8k USDC, to fund 80 (=40+40) hours over around 3 months,<br>
being the development of an MVP, followed by the first half of the validation phase.</p>
<p>At the end of the work funded by this proposal, the tool should consist of:</p>
<p>modules to:<br>
.    ingest relevant governance events from chain data<br>
.    ingest structured/quantitative offchain data (e.g. from Polkassembly)<br>
.    curate data (using queries to assign tags, e.g. “whale”, “shrimp”)</p>
<p>and<br>
.    an indexer capable of reindexing based on these types of data.</p>
<p>The second proposal would fund the second half of the validation phase.<br>
By the end of that work, I intend that the tool will be ingesting qualitative (natural language) data and outputs would begin to demonstrate what is possible with the tool. I should also have some basic benchmarking to flag up any feasibility questions and potential non-labour costs for the future.</p>
<p><strong>Methodology</strong></p>
<p>The methodology is intended to be very, very agile.<br>
The idea of generating insights is to tell us something we didn’t know, rather than setting out to prove or disprove a pre-defined set of hypotheses.<br>
Central to that is the ability to, in investigative terms, ‘pull on threads’ - or, in software terms, to ‘rapidly iterate’. This means that the treasury will, for each sprint/for each proposal, be funding something that it does not know what it will be.</p>
<p>This agile way of working is necessary because:</p>
<p>1 - We need to go where the evidence takes us<br>
2 - It’s likely that many of each of the small technical steps that would make up a milestone can only be identified once a previous step is complete, so identifying and costing out these small technical steps in advance would either lead to wasted labour or force investigations down an inflexible path.</p>
<p>The fact that, in the base case of Squidsway funding referenda, the treasury will be funding something unknown should be mitigated by the ongoing nature of the project, and the fact that each ‘milestone’ (ie funding period) is a small amount.</p>
<h2><a name="p-35457-what-kind-of-user-behaviour-are-we-trying-to-encourage-4" class="anchor" href="#p-35457-what-kind-of-user-behaviour-are-we-trying-to-encourage-4"></a>What kind of user behaviour are we trying to encourage?</h2>
<p>Defining and encouraging the desired outcomes is a question for OpenGov or for the teams making use of Squidsway.<br>
Squidsway is not the part which incentivises or encourages user behaviours<br>
– it’s the part which <strong>identifies where the opportunities are</strong> to do that.</p>
<p><strong>‘user behaviour’:</strong></p>
<p>To illustrate the meaning, though: ‘user behaviours’ will generally be (individual or aggregated) <strong>measurable actions</strong> that can be taken onchain in the Polkdaot ecosystem, such as voting, staking, liquidity provision, but likely in more <strong>specific detail</strong> then this, such as “voting by pre-existing wallets that never voted before”.</p>
<p><strong>‘encourage’:</strong><br>
Already, we seek to change user behaviours all the time - incentivising adoption and liquidity, using social norms to encourage delegation and voting, working on UX to reduce friction and using (some pretty blunt) technical instruments to encourage the adoption of procedures and norms for proposer and delegate behaviours.<br>
The mechanisms we are using - game theory, finely targeted incentivisation and the like - are powerful but we are often applying them amateurishly, iterating our processes and mechanisms based on just guessing what works.</p>
<p>The idea behind Squidsway is that we encourage these kinds of user behaviours by more empirical (ie more reliable) means.</p>
<h2><a name="p-35457-wtf-is-rich-data-chain-indexer-5" class="anchor" href="#p-35457-wtf-is-rich-data-chain-indexer-5"></a>WTF is ‘rich data’ / ‘chain indexer’?</h2>
<p>A chain indexer is a tool that indexes and stores, in greater or lesser detail, a blockchain’s data. Most relevant data in a blockchain (even data as basic as account balances) is not accessible unless you consult a node or an indexer. RPCs under the hood of polkadot.js or your wallet software connect to full nodes but data applications like most block explorers, or data dashboards, use chain indexers on their backend.</p>
<p>Applications that process blockchain data usually index and store the information which is easiest to obtain, and when they want to combine of these different data sources (such as comparing voting frequency of wallets against those wallets’ balances), they combine already indexed datasets. This is faster, but limits the complexity of the combination.<br>
More complex data applications such as Chainalysis’s perform some degree of multi-step indexing, allowing them to retrieve <em>during</em> index time, so they can treat their datasets as <em>graph data</em> (meaning the indexer can follow trails at index time).<br>
The Squidsway tool takes this a couple of steps further with what I’ll call 'compiled and ‘curated’ data.</p>
<p><strong>compiled data</strong> is just data that has been indexed and combined through multi-step context-aware indexing. It could be, for example, “average conviction” for each account (across the accounts’ lifetimes), or “voted on with higher/ lower/ usual conviction” for each proposal.</p>
<p><strong>curated data</strong> uses tags for fast reindexing of commonly used conclusions - for example, accounts could be tagged with categories from “whale” to “shrimp” despite the fact that account balances change over time.</p>
<p>In addition to these, the third and most powerful kind of rich data the Squidsway tool will index is<br>
<strong>offchain data</strong><br>
Since the tool will reindex multiple times, there is less need for its data sources to be fast.<br>
This opens up the possibility to make use of (API-based) web data and, at a higher processing cost, scraped web data and LLM outputs.<br>
For example, the tool will ingest discussions from Polkassembly/ Subsquare / Polkadot forum and process the natural language in discussions there in order to generate tags for sentiment, contentiousness, compliance with each norm, etc.<br>
I hope that this particular feature will help proposers avoid creating proposals that fail for predictable reasons, and create a healthier environment in online governance discussions in general.</p>

<p>I wish I could. They gone from the Discord, not answearing any questions for a months now.</p>

<p>Hi Crane,</p>
<p>it has been 4 days since the statement, and since then no proof has been shared.</p>
<p>Will you be able to produce proofs for your statement?</p>

Tommi Enenkel / Alice und Bob | Mangata

Crane

On-chain data exposes suspicious payment to marketing bounty director

<aside class="quote no-group" data-username="florentina57" data-post="15" data-topic="11971">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/florentina57/48/7854_2.png" class="avatar"> florentina57:</div>
<blockquote>
<p><a class="mention" href="/u/sandreim">@sandreim</a> do you expect this to be related to latency? Or do you have any clues so I can further investigate on my side? Thanks</p>
</blockquote>
</aside>
<p>I already asked for some logs from the collators. But otherwise it is expected to get less votes if the parachain blocks your validators are backing are not posted on-chain. One reason it happens is because some ancestor block was not backed and then it’s descendants cannot be backed as well.</p>

Pablo Andrés Dorado Suárez

<h2><a name="p-35439-solidity-approach-1" class="anchor" href="#p-35439-solidity-approach-1"></a>Solidity approach</h2>
<p>Solidity compiler appends a <a href="https://docs.soliditylang.org/en/v0.8.30/metadata.html#encoding-of-the-metadata-hash-in-the-bytecode" rel="noopener nofollow ugc">CBOR-encoded hash</a> at the end of all smart-contract bytecode, this allows tools like Etherscan to verify and index deployed contracts.</p>
<ul>
<li>Solidity compiler is deterministic and self-contained, any release is compiled to all major targets, including <code>wasm</code> (solc-js).</li>
<li>Instead the compiled code’s codehash, solidity uses the <a href="https://docs.soliditylang.org/en/v0.8.30/metadata.html" rel="noopener nofollow ugc">contract metadata hash</a>, which includes compiler settings, compiled bytecode and believe or not the plain-text source and dependencies, this means any changes in the plain-text source results in a different hash. This have downsides too, but is how they guarantees one source to one binary relationship, thus allows “full verification”, as well as pinning the files publicly on IPFS to be accessed with the metadata hash.</li>
<li><strong>solc-js</strong> compiler allows tools like <strong>Remix IDE</strong> to exist, it provides a complete developer experience directly in the browser, very appealing for beginners.</li>
<li>Compared to docker imagens, solc runs natively and the binaries are small (less than 10mb), they are easily distributed using github releases or package managers like Solidity Version Manager (SVM).</li>
</ul>

<p>gm <a class="mention" href="/u/milus">@milus</a></p>
<aside class="quote no-group" data-username="milus" data-post="4" data-topic="16006">
<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/milus/48/10047_2.png" class="avatar"> milus:</div>
<blockquote>
<p>In one sentence, what concrete type of contracts are expected to be sourced and signed by a director? are the contacts always ad-hoc following opengov proposal approval?</p>
</blockquote>
</aside>
<p>I agree with <a class="mention" href="/u/thewhiterabbitm">@thewhiterabbitM</a></p>
<aside class="quote no-group" data-username="thewhiterabbitM" data-post="7" data-topic="16006">
<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/thewhiterabbitm/48/9774_2.png" class="avatar"> thewhiterabbitM:</div>
<blockquote>
<p>The Directors’ primary duty is to sign enforceable legal agreements to execute specific decisions approved via OpenGov. While the contracts are typically <em>ad-hoc</em> following a proposal’s approval, they may contain additional clauses necessary to ensure legality and compliance under Cayman Islands Law and relevant third-party jurisdictions.</p>
</blockquote>
</aside>
<p>Another example that would not require an additional proposal (maybe <img src="https://emoji.discourse-cdn.com/twitter/thinking.png?v=15" title=":thinking:" class="emoji" alt=":thinking:" loading="lazy" width="20" height="20">) is the Polkadot App, which may need to sign multiple contracts with various service providers, banks, and other entities. A similar case was the now-defunct marketing bounty, which had a single proposal authorizing it to sign all necessary contracts to fulfill its obligations.</p>
<aside class="quote no-group" data-username="milus" data-post="4" data-topic="16006">
<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/milus/48/10047_2.png" class="avatar"> milus:</div>
<blockquote>
<p>how many contracts have been signed and their execution overseen so far?</p>
</blockquote>
</aside>
<p>There is no public record of any PCF report, etc. We are putting together all the available information in the <a href="https://www.polkadot.law/pcf" rel="noopener nofollow ugc">polkadot law webpage</a></p>
<aside class="quote no-group" data-username="milus" data-post="4" data-topic="16006">
<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/milus/48/10047_2.png" class="avatar"> milus:</div>
<blockquote>
<p>is any physical presence required for the meeting of directors?</p>
</blockquote>
</aside>
<p>No, online meetings are allowed under Article 52 of the Articles of Association.<br>
“<em>52. A general meeting may be held, and any person may participate in a meeting, by means of a conference telephone or similar communications equipment by means of which all persons participating in the meeting are capable of hearing each other, and such participation shall be deemed to constitute presence in person at the meeting.</em>”</p>

Wario

Mike | TWR

Appointment of DOT Directors

<p>Hey *,</p>
<p>After getting into the smart contracts on the Hub and trying to make different (Solidity and PVM)smart contracts on different parachains talk to eachother(not with super much success.. ), the only cross contract call that we can get working is having one contract on assethub then accessing the XCM precompiles to send asset transfers from one contract on another parachain. But what about sending messages from one contract on one chain to another.</p>
<p>Questions:</p>
<p>1 - With Smart contracts, is it possible for <strong>one contract on assethub to talk with another smart contract on another parachain</strong>?</p>
<p>There is several use cases for having one main contract on the hub talk to other contracts on hydration for defi fluff or utilize some special functionality on a parachain in trustless way.</p>
<p>Right now the only way seems to be a contract on the hub sending asset transfer to a moonbeam chain(as its one of the few chains besides from assethub that also supports XCM precompiles)</p>
<p>2 - Is there any plans in the nearby future(or maybe already possible?) for one high level smart contract on one parachain to read the state/some internal storage of one contract on one parachain and act based on that? Is there some plan with maybe a precompile for XCQ( <a href="https://forum.polkadot.network/t/cross-consensus-query-language-xcq/7583" class="inline-onebox">Cross-Consensus Query Language (XCQ)</a> ) or any other way ?</p>
<p>Thanks!</p>
<p>~flipchan</p>

<p>Just sell and take the haircut man… you’ll feel better…</p>
<p>Everybody here is disappointed in DOT’s price action. It’s a shame that the most innovative project in crypto has nothing to show for it’s investors. I have lost more than I care to admit.</p>
<p>Polkadot has been nonstop good ideas with terrible execution for years. And, it is a highly inflationary asset. What people failed to realize is that inflation is everything. People will not hold an asset that loses over 12% of it’s value annually. And people can’t make up for that with staking in high tax jurisdictions.</p>
<p>That store of value is the main reason people buy most cryptocurrencies right now. People aren’t buying thousands of dollars worth of ETH to pay their fees or buy things. People aren’t buying thousands of dollars of BTC to pay fees or buy things. DOT took away the primary reason that attracts holders of a token with a high inflationary model.</p>
<p>Atleast something is finally being done about it but it could be too little too late… people will always look back in the charts at polkadot’s old price point and view the current price with the inflated supply in a bad light.</p>
<p>Parity and Web3 Foundation have failed time and time again to make change on the one thing that drives sentiment which is price. It is nonstop negative feedback about lack of support for the parachain teams, issues w/ treasury, difficult development experiences, etc.</p>
<p>Not to mention, there have been no solutions to give the DOT token additional value. Polkadot Plaza never happened. People don’t build applications w/ DOT. Even if there was considerable demand in DOT coretime, it wouldn’t be a significant amount of DOT being purchased to fund development. The average person is not going to buy DOT for governance purposes. And you can no longer fund projects via auctions w/ the DOT token. It has basically become a utility token.</p>
<p>There has been no clear leadership in the space for so long. Purely democratic systems do not always work.</p>
<p>DOT is now ranked <span class="hashtag-raw">#29</span> on cmc, behind 28 other coins that are all technically inferior. And, we will continue to sink unless the community and leadership gets their shit together.</p>
<p>There ought to be some sort of rebranding and 2nd look marketing campaign once all the changes of 2026 are in.</p>

<aside class="quote no-group" data-username="alice_und_bob" data-post="1" data-topic="16001">
<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>
<p>To help newcomers to Polkadot read this report, we want to begin by offering a few ideas that guide the strategic decision-making of many voters.</p>
</blockquote>
</aside>
<aside class="quote no-group" data-username="alice_und_bob" data-post="1" data-topic="16001">
<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>
<p>A complete stack of Web3 services that allow builders to create powerful and scalable applications and business cases at a fraction of the cost of other ecosystems.</p>
</blockquote>
</aside>
<p><a class="mention" href="/u/alice_und_bob">@alice_und_bob</a> - authoring yourselves as the originators of these concepts which are posted in response to public discussion is truly diabolical work lol.</p>
<p>gg &amp; wp <img src="https://emoji.discourse-cdn.com/twitter/victory_hand.png?v=15" title=":victory_hand:" class="emoji" alt=":victory_hand:" loading="lazy" width="20" height="20"></p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/6/62b966d7cbab835318edf0402e8195913a337f5a.png" data-download-href="/uploads/short-url/e5m0POsFTb9ujXfEfvAA68uwwTE.png?dl=1" title="Jan 7" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/6/62b966d7cbab835318edf0402e8195913a337f5a_2_673x500.png" alt="Jan 7" data-base62-sha1="e5m0POsFTb9ujXfEfvAA68uwwTE" width="673" height="500" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/6/62b966d7cbab835318edf0402e8195913a337f5a_2_673x500.png, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/6/62b966d7cbab835318edf0402e8195913a337f5a_2_1009x750.png 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/6/62b966d7cbab835318edf0402e8195913a337f5a.png 2x" data-dominant-color="090A0A"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">Jan 7</span><span class="informations">1210×898 76.6 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/a/a216b0cb69454adf471bce4663278dd7482b90c4.png" data-download-href="/uploads/short-url/n7TXNWU5F8CvPgTptoOU5EV3gUY.png?dl=1" title="Jan7 2" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/a/a216b0cb69454adf471bce4663278dd7482b90c4_2_594x500.png" alt="Jan7 2" data-base62-sha1="n7TXNWU5F8CvPgTptoOU5EV3gUY" width="594" height="500" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/a/a216b0cb69454adf471bce4663278dd7482b90c4_2_594x500.png, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/a/a216b0cb69454adf471bce4663278dd7482b90c4_2_891x750.png 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/a/a216b0cb69454adf471bce4663278dd7482b90c4.png 2x" data-dominant-color="070708"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">Jan7 2</span><span class="informations">1082×910 61.1 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/6/6206c7413a81652d6abd80b4fdf1ac5e04613d83.png" data-download-href="/uploads/short-url/dZbjvqLSFHQmdc5EyjIiKsPWMyD.png?dl=1" title="Oct 2024" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/6/6206c7413a81652d6abd80b4fdf1ac5e04613d83_2_690x404.png" alt="Oct 2024" data-base62-sha1="dZbjvqLSFHQmdc5EyjIiKsPWMyD" width="690" height="404" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/6/6206c7413a81652d6abd80b4fdf1ac5e04613d83_2_690x404.png, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/6/6206c7413a81652d6abd80b4fdf1ac5e04613d83_2_1035x606.png 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/6/6206c7413a81652d6abd80b4fdf1ac5e04613d83.png 2x" data-dominant-color="0C0C0C"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">Oct 2024</span><span class="informations">1246×730 70 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/1/1a5d471d93611a11861e9b8220f2bed2a611be89.png" data-download-href="/uploads/short-url/3LegbeeOBgtgVm3NXaqlKAooTmp.png?dl=1" title="Screenshot 2025-11-24 at 14.32.23" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/1/1a5d471d93611a11861e9b8220f2bed2a611be89_2_690x360.png" alt="Screenshot 2025-11-24 at 14.32.23" data-base62-sha1="3LegbeeOBgtgVm3NXaqlKAooTmp" width="690" height="360" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/1/1a5d471d93611a11861e9b8220f2bed2a611be89_2_690x360.png, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/1/1a5d471d93611a11861e9b8220f2bed2a611be89_2_1035x540.png 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/1/1a5d471d93611a11861e9b8220f2bed2a611be89.png 2x" data-dominant-color="141515"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">Screenshot 2025-11-24 at 14.32.23</span><span class="informations">1080×564 62.7 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/8/8b3eced3e05831a850d28586b110d8e4a08ad366.jpeg" data-download-href="/uploads/short-url/jROVTiJ720IyPLFfgtZDFgcLkJE.jpeg?dl=1" title="signal-2025-11-24-141124" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/8/8b3eced3e05831a850d28586b110d8e4a08ad366.jpeg" alt="signal-2025-11-24-141124" data-base62-sha1="jROVTiJ720IyPLFfgtZDFgcLkJE" width="659" height="385"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">signal-2025-11-24-141124</span><span class="informations">659×385 29.5 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>

2025-Q3 Polkadot Treasury Report

<p>Hi there <img src="https://emoji.discourse-cdn.com/twitter/waving_hand.png?v=15" title=":waving_hand:" class="emoji" alt=":waving_hand:" loading="lazy" width="20" height="20"></p>
<p>After two busy months, here’s a fresh update from the PAPI team!</p>
<h1><a name="p-35423-staking-optimizer-sdk-1" class="anchor" href="#p-35423-staking-optimizer-sdk-1"></a><img src="https://emoji.discourse-cdn.com/twitter/chart_increasing.png?v=15" title=":chart_increasing:" class="emoji" alt=":chart_increasing:" loading="lazy" width="20" height="20"> Staking Optimizer (&amp; SDK!)</h1>
<p>One of the most significant dApps we’ve released so far is the <strong>Staking Optimizer</strong>!<br>
<a class="mention" href="/u/voliva">@voliva</a> recently <a href="https://forum.polkadot.network/t/introducing-a-new-trio-from-papi-staking-optimizer-staking-sdk-and-polkahub/15923#p-35175-staking-optimizer-2">shared it on the Polkadot forum</a>, and it’s already getting strong traction from many users. We received very positive feedback from early users!</p>
<p>As with all our dApps, it’s built <em>light-client first</em>. This time, however, we also offer an optional centralized indexer so users can access trusted data in a snappier way.</p>
<p>The dApp is primarily <a href="https://bafybeidhg7g3doyrwu6udfpqmlhw5lc3s4oimdta5ivveuutvg2nb5foga.ipfs.inbrowser.link" rel="noopener nofollow ugc">made available through IPFS</a> (as of <strong>2025-11-24</strong>, CID: <code>bafybeidhg7g3doyrwu6udfpqmlhw5lc3s4oimdta5ivveuutvg2nb5foga</code>), and secondarily available through a <a href="https://staking.usepapi.app" rel="noopener nofollow ugc">centralized server</a>.</p>
<h1><a name="p-35423-polkahub-2" class="anchor" href="#p-35423-polkahub-2"></a><img src="https://emoji.discourse-cdn.com/twitter/artist_palette.png?v=15" title=":artist_palette:" class="emoji" alt=":artist_palette:" loading="lazy" width="20" height="20"> PolkaHub</h1>
<p>We’ve released <strong><a href="https://github.com/polkadot-api/polkahub" rel="noopener nofollow ugc">PolkaHub</a></strong>, an account and wallet toolkit designed for dApps. It follows a concept similar to <strong><a href="https://rainbowkit.com" rel="noopener nofollow ugc">RainbowKit</a></strong> in the Ethereum ecosystem, and we’re really proud of how it turned out.<br>
PolkaHub is highly configurable, fully frontend-agnostic, and built to make wallet integration effortless for developers.<br>
<a class="mention" href="/u/voliva">@voliva</a> also <a href="https://forum.polkadot.network/t/introducing-a-new-trio-from-papi-staking-optimizer-staking-sdk-and-polkahub/15923#p-35175-polkahub-6">highlighted it in a recent forum post</a>.</p>
<h1><a name="p-35423-polkadot-apicheck-runtime-3" class="anchor" href="#p-35423-polkadot-apicheck-runtime-3"></a><img src="https://emoji.discourse-cdn.com/twitter/toolbox.png?v=15" title=":toolbox:" class="emoji" alt=":toolbox:" loading="lazy" width="20" height="20"> <code>@polkadot-api/check-runtime</code></h1>
<p>We had yet another release over the past two months: the <strong><code>check-runtime</code> CLI</strong>. This plug-and-play tool performs sanity checks and flags common pitfalls in Substrate runtimes, helping ensure that production runtimes remain as safe and reliable as possible.</p>
<p>It has already been integrated by <strong><a href="https://github.com/paritytech/polkadot-sdk/pull/10226" rel="noopener nofollow ugc">Westend runtimes by Parity</a></strong> and by <strong><a href="https://github.com/paseo-network/runtimes/pull/308" rel="noopener nofollow ugc">Paseo</a></strong>, with more integrations expected in other chains’ pipelines. The tool has already helped uncover runtime issues in both Paseo and Westend!</p>
<h1><a name="p-35423-polkadot-api121-4" class="anchor" href="#p-35423-polkadot-api121-4"></a><img src="https://emoji.discourse-cdn.com/twitter/books.png?v=15" title=":books:" class="emoji" alt=":books:" loading="lazy" width="20" height="20"> <code>polkadot-api@1.21</code></h1>
<h2><a name="p-35423-typed-signed-extensions-5" class="anchor" href="#p-35423-typed-signed-extensions-5"></a>Typed Signed Extensions</h2>
<p>Starting from <code>polkadot-api@1.21.0</code>, custom signed extensions are now <em>strongly typed</em>, delivering a major improvement to the developer experience.</p>
<p>We’ve seen growing demand for this feature, likely driven by the upcoming <strong>Extrinsic V5</strong> format and the introduction of new authentication mechanisms across various chains. We’re proud to say that PAPI has full Extrinsic V5 support.</p>
<p>The <strong><a href="https://dev.papi.how" rel="noopener nofollow ugc">PAPI Console</a></strong> has also adopted this upgrade, making it easier than ever to work with custom signed extensions.</p>
<h2><a name="p-35423-solidity-codegen-6" class="anchor" href="#p-35423-solidity-codegen-6"></a>Solidity Codegen</h2>
<p>Developers using <code>ink!</code> are already familiar with the <code>papi ink</code> command, and now we’re excited to share that <strong><code>papi sol</code> is officially here</strong>!<br>
Solidity contracts are now first-class citizens in PAPI (and in <code>@polkadot-api/sdk-ink</code>), making it incredibly easy to interact with them from a dApp in a fully typed manner.</p>
<h2><a name="p-35423-providers-work-7" class="anchor" href="#p-35423-providers-work-7"></a>Providers Work</h2>
<p>Over the past few months, we’ve done extensive fine-tuning on our providers, especially the WebSocket provider. This includes improvements to the heartbeat logic (the WS <code>ping-pong</code> mechanism), ensuring stale connections are detected and closed promptly, as well as tightening up reconnection and teardown edge cases.</p>
<p>Thanks to this work, our providers are now in an exceptionally stable state.</p>
<h2><a name="p-35423-upcoming-polkadot-api20-8" class="anchor" href="#p-35423-upcoming-polkadot-api20-8"></a>Upcoming <code>polkadot-api@2.0</code></h2>
<p><code>polkadot-api</code> is preparing itself to receive its first major update since the stable release. We’re working actively on it, and expect to release the first release candidate before EOY. It will come with a bunch of changes improving the developer experience, reducing the API surface where necessary, and adding new useful APIs.<br>
The migration will be straightforward, and a migration guide will be released prior to the final release.</p>
<p>Make sure to follow this thread to be informed!</p>
<h1><a name="p-35423-sub0-symbiosis-buenos-aires-9" class="anchor" href="#p-35423-sub0-symbiosis-buenos-aires-9"></a><img src="https://emoji.discourse-cdn.com/twitter/airplane_departure.png?v=15" title=":airplane_departure:" class="emoji" alt=":airplane_departure:" loading="lazy" width="20" height="20"> <code>sub0</code> Symbiosis @ Buenos Aires</h1>
<p>Two weeks ago we visited Buenos Aires to attend the <strong><code>sub0</code> conference</strong>, where we gave a talk on the PAPI SDKs and PolkaHub. We also mentored at the <strong>WebZero</strong> hackathon and hosted a barcamp session, all of them with very positive outcomes.<br>
We’re deeply grateful for the invitation and for the hard work of the entire organizing team!</p>

<p>Thanks for the feedback <img src="https://emoji.discourse-cdn.com/twitter/rocket.png?v=15" title=":rocket:" class="emoji" alt=":rocket:" loading="lazy" width="20" height="20"><br>
I’ve been updating the proposal based on other folks’ feedback and I will start updating this forum post now.<br>
Hopefully this will make the technical approach clearer.</p>
<p>As I’ve drilled down into what the project can offer to various stakeholders, it’s become clear that the use cases I included in the original version of this forum post are the just tip of the iceberg.</p>
<p>The closest I’ve come to a common theme among them is that governance failures cost everyone involved in OpenGov - in misallocated treasury capital,  but also our time, headaches and often a toxic environment.</p>
<p>I’ve also realised that I need to make the use cases outside OpenGov clearer - so there will be more focus in the updated proposal on ‘user behaviour’ - so that this can not just include efficient and effective governance, but also any onchain behaviours that anyone - eg product teams, or just Polkadot nerds - want to measure or know how to incentivise.</p>
<p>The proposal is complete rn, but I will continue to work on it a little, to include where it fits in from the ‘citizenship’ perspective.</p>
<p>Thanks for the feedback.<br>
Rest of OpenGov, I’d love to hear y’all’s thoughts too!</p>

More active voters, less painful proposals! - Squidsway: a tool to make governance, proposal and voting data understandable by all. SEEKING FEEDBACK

<p>Appreciate the explanation mate <img src="https://emoji.discourse-cdn.com/twitter/handshake.png?v=15" title=":handshake:" class="emoji" alt=":handshake:" loading="lazy" width="20" height="20"></p>

Juanma0x | Support W3F

<h2><a name="p-35407-polkadot-news-1" class="anchor" href="#p-35407-polkadot-news-1"></a>Polkadot News</h2>
<p>Polkadot Asset Hub and Bridge Hub runtime upgrade to 2.0.3, which accommodates the Ethereum network’s hard fork on Dec 3rd and also enables additional cross-chain use cases, is now up for voting <a href="https://polkadot.subsquare.io/referenda/1797" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1797</a></p>
<p>Listen to “Making Web3 More Human: Products for People” with Parity Technology’s Karim Jedda on The Kusamarian’s Space Monkeys podcast <a href="https://www.youtube.com/watch?v=cruhQIUoc0s" rel="noopener nofollow ugc">https://www.youtube.com/watch?v=cruhQIUoc0s</a></p>
<p>The referendum submitted by Web3 Foundation Governance team to close the Polkadot Marketing Bounty is in the decision period and is currently passing <a href="https://polkadot.subsquare.io/referenda/1791" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1791</a></p>
<p>The referendum to close the Polkadot Pioneers Prize bounty and return remaining funds to the treasury is passing unanimously <a href="https://polkadot.subsquare.io/referenda/1795" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1795</a></p>
<p>RegionX Hub funding request for retroactive work, key features, and maintenance of Polkadot coretime UI/dashboard has been approved <a href="https://polkadot.subsquare.io/referenda/1788" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1788</a></p>
<h2><a name="p-35407-kusama-news-2" class="anchor" href="#p-35407-kusama-news-2"></a>Kusama News</h2>
<p>The referendum to set KSM/DOT Asset Rate Locations on Kusama Asset Hub (Post-Migration Restoration) is passing unanimously and is expected to confirm in two days <a href="https://kusama.subsquare.io/referenda/615" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/615</a></p>

Radhakrishna Dasari

Polkadot Digest 24 November 2025

<p>The “democratic rabble” didn’t tank DOT — the tiny handful of entities actually steering OpenGov did. We both know who calls the shots, and it’s not the random retail voter who couldn’t push a referendum through. When a few whales, e.g. W3F, effectively control most outcomes, calling Polkadot decentralized is adorable.</p>
<p>And yes, if those same power-holders thought lighting millions on fire for sports sponsorships was visionary strategy, maybe the ROI problem isn’t the “simple minds” noticing DOT at $2 — maybe it’s the governance geniuses who treated the treasury like a marketing slot machine.</p>
<p>Token price reflects usage, not vibes. Polkadot doesn’t have a lot of paying customers because, shocker, there’s still no product people want to pay for.</p>
<p>But sure, tell us again how the real issue is the plebs comparing DOT to ETH.</p>

Miles Patterson

Polkadot is facing an unprecedented crisis

<p>Hi Polkadot Community,</p>
<p>My team Peranto SSI NA LLC and I currently have an unfunded/bonded proposal in OpenGov, Ref 1789. We understand that we are in a bind with the most recent post from Kilt <a href="https://x.com/Kiltprotocol/status/1988220030623117742?s=20" rel="noopener nofollow ugc">https://x.com/Kiltprotocol/status/1988220030623117742?s=20</a> . Please know as part of our exploration work to find a pathway for our clients FlyAdvanced for FlyGateway flight schools and Chilian Mountaineers we have found some options, in addition to reaching out to Kilt directly to understand liabilities of taking over the chain.</p>
<p>First course of action is the initial proposal; to test the technology and remove the bugs, we are proposing to make this effort on Kreivo via Kusama. Once proven our goal is to stand-up Highlander Chain, this is our own deployment (over time) for our custom runtime and multiple applications/verticals listed within our proposal. Please see comprehensive options after phase 1 here; <a href="https://aura.peranto.app/" rel="noopener nofollow ugc">https://aura.peranto.app/</a></p>
<p>Right now, my team is requesting feedback from the community on funding request directive.</p>
<ol>
<li>
<p>We can leave up 1789 put down our deposit for the proposal, fix the verbiage to indicate Krevio is our host for testing (next 7 months), plus adjust our financial numbers for this new direction.</p>
</li>
<li>
<p>Let 1789 end without a deposit and open a new referendum on Kusama for this request?</p>
</li>
</ol>
<p>I have read the feedback and have opened a telegram room for any questions <a href="https://t.me/+CkDiXA9-GnFhZDIx" rel="noopener nofollow ugc">https://t.me/+CkDiXA9-GnFhZDIx</a> and the above, plus our website should address any current questions regarding the sunset of Kilt, as we look to move to Highlander.</p>
<p>Best Regards,</p>
<p>Peranto SSI NA LLC</p>

Ref 1789 Proposal Direction Peranto SSI NA OpenGov

<p>If you have a blockchain dedicated to multiple single uniswap pairs, then you can easily stop sandwiching:</p>
<p>We have a prices vector p_{n-1} from the previous block, so then the current block B_n declares the prices vector p’ for all pairs active within B_n, and then on_finalize computes the new prices vector p_n after B_n finishes, and checks that if p’ is say the mean, or geometric mean, or whatever, of p_{n-1} and p_n.</p>
<p>All tx execute at p’ of course, so that every tx pays exactly the same price given in p’, and sandwiching cannot occur within B_n.  All tx declare their allowed price ranges, so B_n is only valid if all tx in B_n accept p’.</p>
<p>You might require some integer linear program to construct B_n here, because including or excluding a tx does change p’, and so might exclude other txs.   Integer linear programs are NP-complete, but approximation algorithms should yield good results here.</p>
<p>A conventional smart contract platform cannot do this, but if you’ve a dedicate chain then you can enforce p’ being correctly constructed in post-tx logic like on_finalize.</p>
<p>Afaik it’s dubious that non-pairwise high dimensional uniswaps ever make sense anyways, like maybe they’ll always just hemorrhage funds.  If however you do believe in high dimensional uniswaps like hydration, then afaik you could still do this provided your approximation algorithm can benefit from the higher degress of freedom.</p>
<p>I’ve never tried to work this out since I’ve never believed in high dimensional uniswaps anyways, so maybe other higher dimensional cyclic-sandwitching attacks exists here or who knows what, but like I said I’d expect shut like that breaks the underlying high dimensional uniswap.</p>
<p>Anyways this is what I meant by my comment above.</p>
<p>p.s.  I mostly just hate seeing polkadot projects reduced to being smart-contract-like because developers cannot get their minds out of that dumb ETH rut.</p>

Jeff Burdges

Encrypted Mempools: Turning Polkadot&rsquo;s MEV Leak into Treasury Revenue

Encrypted Mempools: Turning Polkadot's MEV Leak into Treasury Revenue

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

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

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

Anonymous OpenGov

THE RIGHT TO DISAPPEAR

Executed

Here's a simple summary of the Kitdot project:

- Kitdot is a toolkit for building apps on PolkaVM using Solidity
- It helps developers work with Kusama Asset Hub
- It lets users log in with social accounts like Google or Twitter
- It makes setting up a local development environment easy
- It helped 200+ contracts get deployed at a hackathon
- 90% of participants were new to the ecosystem
- The creator is asking for funding to continue this work
- Future plans include gasless transactions and account templates

Deciding

[Medium Spender] Referendum #617

- A user lost 102 KSM while transferring from Basilisk to Kusama Asset Hub.
- The transfer worked on Basilisk but the KSM never arrived.
- An XCM message error sent the funds to the wrong chain.
- The funds are not recoverable through normal trapped asset methods.
- The Paraspell team helped find the problem and fixed it.
- The only way to get the funds back is through a treasury spend.
- The user asks the community to approve returning the 102 KSM.
- This was an accident during a system migration, not anyone's fault.

Reimbursement of 102 KSM Lost Due to Incorrect Reserve Selection in XCM Transfer

- This update fixes the KSM and DOT exchange rates on Kusama Asset Hub.
- The rates were lost during a system move and need to be set again.
- It removes old, unused KSM rate information.
- It adds new exchange rates between Kusama and Polkadot Asset Hubs.
- The KSM to DOT rate is set at 4 to 1, just like before.
- Rates are stored using special large numbers for accuracy.
- This helps the treasury system work correctly with KSM and DOT conversions.

Set KSM/DOT Asset Rate Locations on Kusama Asset Hub (Post-Migration Restoration)

- Kusama is now a peer network to Polkadot, not just a test network.
- Polkadot wants to manage identity for Kusama through its own system.
- Kusama should have its own identity system to stay independent.
- Relying on Polkadot could let them change or stop Kusama’s identity rules.
- Having separate systems makes both networks stronger and safer.
- Kusama can build its own identity tools and try new ideas.
- Voting "AYE" means Kusama controls its own identity.
- Voting "NAY" means Polkadot controls Kusama’s identity.

Wish for Change: Deploy Native Proof of Personhood Pallets on Kusama Infrastructure

Here is a summary of the post in simple terms:

- Encointer wants to upgrade its system to version 2.0.0.
- This upgrade includes a fix for cross-chain stable coin treasuries.
- The fix was also in an older version (1.9.2) that was not released.
- A proposal has been made to allow this upgrade.
- Links to release notes and the proposal are provided.

[Whitelisted Caller] Encointer runtime upgrade to 2.0.0

Delay Demo #2 Treasury Guardian

- The referendum is about testing a new tool called Treasury Guardian.  
- It includes a payment to Mr. Bill Laboon, which might be delayed or canceled.  
- The tool helps with milestone-based payments to improve treasury efficiency.  
- The goal is to get more people involved in Kusama and Polkadot OpenGov.  
- Follow [TreasuryEff on X](https://x.com/TreasuryEff) for updates.

Kusama

referenda5

fellowship1

treasury33

discussions1388