candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

On Anonymity, Accountability, and Respectful Debate

Towards informed and respectful criticism about the DAP proposal and concerns about unilateral public censorship of this forum (Both together)

Tommi Enenkel / Alice und Bob | Mangata

Which projects should be cut or spending reduced?

Daniel Artamendi

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:

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

[Revive] Deterministic Verifiable Contracts

Make Anonymity Coherent Again: Proposal for privacy as first-class citizen in JAM

Gonzalo Etse

Composability Between smart contracts on different parachains

Rust Syndicate

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

Eric ~Distractive.xyz

Ref 1789 Proposal Direction Peranto SSI NA OpenGov

On-chain data exposes suspicious payment to marketing bounty director

Crane

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

Ecosystem

DOT Events Bounty Report for Q3 2025 (July 1st - September 30th)

Events Bounty Curators

Anti-Scam Bounty - what a joke

Polkadot JS Progress Update &amp; Moving Forward - BlockDeep

Josep

Polkadot JS Progress Update & Moving Forward - BlockDeep

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

GM Sax,
For documentation purposes, there’s a backup of our <a href="https://gleaming-card-17f.notion.site/Marketing-Bounty-2b50123d1f0c81bca866c44f3d4a9627" rel="noopener nofollow ugc">Notion page available here</a>. We also updated the link on our X-account.
We’ll update this page soon with additional documents and insights for others to learn from.
We gladly answer any questions from future curators, bounties, ecosystem marketing teams, Parity, and the W3F.
Cheers <img src="https://emoji.discourse-cdn.com/twitter/saluting_face.png?v=15" title=":saluting_face:" class="emoji" alt=":saluting_face:" loading="lazy" width="20" height="20">
PS: <a href="https://assethub-polkadot.subscan.io/extrinsic/10571308-4" rel="noopener nofollow ugc">All MB funds have been returned</a>.

Dear Mark65,
Thank you for the questions!
You can find the full details of the EB curator compensation in the latest <a href="https://polkadot.subsquare.io/referenda/1734?tab=call" rel="noopener nofollow ugc">top up proposal. </a>
Each proposal needs to be reviewed by a minimum of 4 curators, but in most cases it is reviewed by the entire curator set. Keep in mind that the quorum required to make a decision on a proposal is 4 votes. So the statement that each curator only reviews 3.5 proposals per quarter is not correct.
On top of the proposals, there are reports, which in many cases require far more research and reviews than the actual proposal. The reviews include going through all the receipts (this has been proven to be quite lengthy for Key Events, for an example), swap sheets, slippage returns etc. So the amount of time going into reviews is really much higher than what is stated here, respectfully.
Additionally, each curator has additional responsibilities besides reviewing proposals. These include, for example: reviewing designs, managing the website, X account, advising and guiding proponents, designing, maintaining, and growing the Roots program, putting together a Key Events Calendar, coordinating BD, creating resources…
We would also like to state that once Q4 is over, the EB will release an extensive report in Q1 2026 with full data insights of 2025. We are also liaising with members of Parity &amp; W3F to align on priorities for 2026 and key learnings from the full tenure of the Events Bounty to date.
Thanks.

Mark

Appreciate you taking the time Lily and giving us feedback! It was a pleasure meeting you in person!!! Plus spending time exploring BA together.
Me &amp; my team have some work to do &amp; it may not fit in a pretty box! The Goal is to Solve Problems and to deploy, for this partnerships are required, otherwise this is just a use case that may sit on a shelf. I have always been here to help and try to solve problems. My team and I will put out something well versed when we forward. <img src="https://emoji.discourse-cdn.com/twitter/handshake.png?v=15" title=":handshake:" class="emoji" alt=":handshake:" loading="lazy" width="20" height="20">

Liliana Mendez

<aside class="quote no-group" data-username="Cyrill" data-post="8" data-topic="16042">
<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/cyrill/48/7339_2.png" class="avatar"> Cyrill:</div>
<blockquote>
So what I suggest is to leverage the fact that we actually own the PVM blob container format (unlike Wasm or EVM). Seemingly, the only thing we need is a small change to the PVM loader and disassembler to accept blobs where the blob exceeds the length found in the header. PVM can simply ignore the extra data and the loader just always uses the length specified in the header and not the actual bytes (this completely solves your concern of intermingling metadata as code bytes). Which allows us to follow the Ethereum model. <a class="mention" href="/u/koute">@koute</a> I can implement the change if this looks LGTM from your side.
</blockquote>
</aside>
To be fair, even with the WASM blob format we could do it because it supports custom sections.
But, there’s no need to add any new code to ignore any extra data. This code already exists.
The PVM blob is designed in a way that you can have custom sections with custom data, and even the already deployed <code>pallet-revive</code> will ignore these new sections as long as you give them correct IDs and put them at the end of the blob. The only change needed would be to add this to the linker/toolchain so that your custom section is actually emitted.
There is more. Although this isn’t yet implemented (but it’s trivial to implement, if you’re interested), the PVM blob format was also designed so that you can calculate a hash of the program and be able to trivially skip all of the extra stuff.
Because you see, metadata isn’t the only thing that can be inside of a PVM blob. You can also have things like debug info for example. So the format was designed like this: everything which affects the visible runtime semantics (the program) goes first, and everything which doesn’t goes last. So if you want to calculate a fingerprint of the program that’s easy: you read the first byte of the blob, you skip 8 bytes**, then you read all of the bytes until you either encounter a section ID that is <code>0</code> (i.e. end of file) or with its most significant bit set (i.e. the first optional section), and you hash that all together. There you go. A fingerprint of the program which ignores metadata.
** - The “skip 8 bytes” part is somewhat unfortunate; those 8 bytes there contain the length of the whole blob, and in fact this wasn’t in my original design, but I’ve added it on request to make it possible to skip the whole blob in O(1) rather than in at most O(~130) operations. So we need to skip it since the “length of the whole blob” obviously also includes the metadata/extra stuff.

Bastian Köcher

The Polkadot Anti-Scam Team cracks me up. 
They haven’t actually stopped a single scam, as far as I can tell. I genuinely have no idea what they’re doing over there…
Also if you pay someone to take down phishing sites you incentives them to make sure there are always phising sites.

I don’t think most people realize what kind of unsung heroes the PolkadotJS maintainers are. Keeping such a huge, complex codebase alive (especially one originally written as a one-man-show) is absolutely exhausting work.
The few times I’ve contributed to PolkadotJS, I felt a tiny piece of my soul leave my body <img src="https://emoji.discourse-cdn.com/twitter/sweat_smile.png?v=15" title=":sweat_smile:" class="emoji" alt=":sweat_smile:" loading="lazy" width="20" height="20"> It gave me just enough of a glimpse to really appreciate how mentally draining it must be to do this day in, day out. Very few people can understand that.
So, for real: thank you so much for the hard work, patience, and dedication you’ve put into PolkadotJS. Your effort has not gone unnoticed. Thanks for your service to the ecosystem! <img src="https://emoji.discourse-cdn.com/twitter/saluting_face.png?v=15" title=":saluting_face:" class="emoji" alt=":saluting_face:" loading="lazy" width="20" height="20">

Hi Alice and Bob,
Here is the ETH tx to Pain Gaming: <a href="https://etherscan.io/address/0xe76e9ea1d8fdbf742fc796058aadc7d91a83d2ca#tokentxns" class="inline-onebox" rel="noopener nofollow ugc">Address: 0xe76e9ea1...91a83d2ca | Etherscan</a>
The rest is unfortunately not mine to share. As I explained already, I was only the facilitator - I’m not a party to the contracts, invoices, or emails.

<h2><a name="p-35569-polkadot-news-1" class="anchor" href="#p-35569-polkadot-news-1" aria-label="Heading link"></a>Polkadot News</h2>
“Polkadot People Initiative: Incentives for Mass Polkadot Activation Campaign” is in the decision period <a href="https://polkadot.subsquare.io/referenda/1783" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1783</a>
The approved treasury payouts with assets addressed in XCM v3 are currently failing on Polkadot Asset Hub. Track the progress of the fix here <a href="https://github.com/polkadot-fellows/runtimes/pull/1019" class="inline-onebox" rel="noopener nofollow ugc">Add local pay module for Asset Hub Polkadot treasury paymaster with XCM V3 to V5 asset conversion by dhirajs0 · Pull Request #1019 · polkadot-fellows/runtimes · GitHub</a>
The referendum to cancel 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>
<h2><a name="p-35569-kusama-news-2" class="anchor" href="#p-35569-kusama-news-2" aria-label="Heading link"></a>Kusama News</h2>
The referendum to set KSM/DOT Asset Rate locations on Kusama Asset Hub (Post-Migration Restoration) is in the confirmation period <a href="https://kusama.subsquare.io/referenda/615" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/615</a>
Upgrading Kusama Asset Hub to fellows release v2.0.3 to enable more cross-chain use cases is now up for voting <a href="https://kusama.subsquare.io/referenda/618" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/618</a>

Radhakrishna Dasari

Polkadot Digest 27 November 2025

<aside class="quote no-group" data-username="burdges" data-post="8" data-topic="15817">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/burdges/48/172_2.png" class="avatar"> burdges:</div>
<blockquote>
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.
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’.
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.
</blockquote>
</aside>
It doesn’t seem trivial to me:
<ul>
<li>There could be multiple solutions of txs to be included with a given set of inputs.</li>
<li>If you assume pairwise swaps, you will also definitely have routes, which introduces dependencies and further increases the solution complexity</li>
</ul>
Also to note: If you treat the pairs independently and solve the block as a whole, there will be no back-running at the end of the block, so the prices of pools in relation to each other will not be in equlibrium. The protocol could perform the backrun and take the arbitrage though.
<aside class="quote no-group" data-username="burdges" data-post="8" data-topic="15817">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/burdges/48/172_2.png" class="avatar"> burdges:</div>
<blockquote>
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.
</blockquote>
</aside>
I can’t follow this thought. Hydration only from the outside looks like it has one pool with many tokens, but underneath it has one pair for each associated token and they route through one liquidity token. In my understanding this is more capital efficient, because you reduce the number of hops on a route to virtually 1 (and actually 2) and thus the total set of pairs is minimized and you have less pools that you actively need to keep in equilibrium aka non-informed flow can cancel each other out more easily.

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

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

Thanks for that. The 60.8k was indeed a typo and has been updated.
Furthermore here are the reward caps again:
max. $1k/payout delay 
max. $3k/payout cancel
<div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/3/3d1b94d5fcb81fa714748a2e487a37c1be92e849.png" data-download-href="/uploads/short-url/8IAdy7ns0dFtkuPoQEBQw3xtkSt.png?dl=1" title="Screenshot 2025-10-22 at 11.03.05" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/3/3d1b94d5fcb81fa714748a2e487a37c1be92e849_2_690x284.png" alt="Screenshot 2025-10-22 at 11.03.05" data-base62-sha1="8IAdy7ns0dFtkuPoQEBQw3xtkSt" width="690" height="284" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/3/3d1b94d5fcb81fa714748a2e487a37c1be92e849_2_690x284.png, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/3/3d1b94d5fcb81fa714748a2e487a37c1be92e849.png 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/3/3d1b94d5fcb81fa714748a2e487a37c1be92e849.png 2x" data-dominant-color="F7F6F7"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg>Screenshot 2025-10-22 at 11.03.05975×402 58.8 KB<svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div>
<div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/0/00a4119132bddba0fe9d595b5935f072b24821c5.png" data-download-href="/uploads/short-url/5FvXcuPqWDXqfUsIhpoXd6pm2V.png?dl=1" title="Screenshot 2025-10-22 at 11.03.16" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/0/00a4119132bddba0fe9d595b5935f072b24821c5.png" alt="Screenshot 2025-10-22 at 11.03.16" data-base62-sha1="5FvXcuPqWDXqfUsIhpoXd6pm2V" width="419" height="349"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg>Screenshot 2025-10-22 at 11.03.16419×349 14.3 KB<svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div>

Gabriel

Tom | Stake Plus

Treasury Guardianship

Can we at least get an idea of how much of the time was spent on actual onboarded cases and how many onboarded cases are there as opposed to time creating the templates and wiki? also to know the impact on actual cases if this bounty were to be closed given it’s lengthy lethargy. Let’s revisit this, as documents needed for a Quick Starter Packs and knowledge bases (fenced) are usually not enough as you need to interact with the authorities or agencies to actually make it work.
For us, not much has changed since our initial closing post <a href="https://polkadot.subsquare.io/posts/425" class="inline-onebox" rel="noopener nofollow ugc">Closing Bounty 62. Polkadot Legal Bounty.</a>
It wouldn’t make much sense to charge for little to no onboarded users. Moreover, this bounty seems like it won’t be able to explain much of the operations from a privacy / client-attorney point of view for obvious reasons. For OpenGov it’ll become extremely hard or impossible to attest the work done here as well.

Polkadot Legal Bounty Update

<hr>
Polkadot’s transition to JAM provides a unique opportunity to solve the “Original Sin” of smart contract blockchains: the lack of native privacy. However, simply deploying privacy protocols (like Aztec or Tornado Cash clones) as isolated Services / Parachains (manta?) will lead to fragmented anonymity sets and poor UX.
Recently I heard Gavin Wood advocate for client-side zk-proofs generation, and I agree with tihs. But it is clear that privacy requires state contention management (preventing double spends without revealing the spender) which the Account model doesn’t handle natively. When writting Noir on top of EVM this becomes clear right away, and you have to turn up to projects that do, like Aztec.
I propose that JAM must deploy a Canonized Privacy Service. This service should provide the bare-metal primitives for a Global Anonymity Set, specifically managing the UTXO/Nullifier state and Merkle Frontiers, while leaving the application logic to upper-layer services.
<h3><a name="p-35547-h-1-private-state-1" class="anchor" href="#p-35547-h-1-private-state-1" aria-label="Heading link"></a>1. Private State</h3>
The Account Model while efficient for transparency, is fundamentally hostile to privacy.
Privacy protocols like Zcash and Aztec utilize an Encrypted UTXO model managed by a Nullifier Set. State is not modified in place, it is appended. This prevents double-spende without revealing the user, etc. But implementing this on general-purpose chains is a nightmare. Developers are forced to deploy custom Merkle contracts and build complex, centralized off-chain indexers to reconstruct paths, leading to “Indexing Hell.”
<h3><a name="p-35547-h-2-jam-opportunity-for-a-global-anonymity-set-2" class="anchor" href="#p-35547-h-2-jam-opportunity-for-a-global-anonymity-set-2" aria-label="Heading link"></a>2. JAM: opportunity for a Global Anonymity Set</h3>
The transition to JAM shifts us from asynchronous chains to synchronous services. If we treat privacy as just another “App” layer, we risk two failures:
<ul>
<li>
Fragmentation: A user on “Privacy App A” is not hidden among users of “Privacy App B.” The anonymity sets remain small and statistically vulnerable.
</li>
<li>
Broken Composability: Without a shared Nullifier standard, distinct privacy services fracture the anonymity set. A shared System Service allows distinct applications to share a unified ‘Shielded Pool’ of liquidity, even if the application logic differs. Otherwise it’s back to incoherence.
</li>
</ul>
<h3><a name="p-35547-h-3-proposed-architecture-jam-privacy-system-service-3" class="anchor" href="#p-35547-h-3-proposed-architecture-jam-privacy-system-service-3" aria-label="Heading link"></a>3. Proposed Architecture: JAM Privacy System Service</h3>
A Native System Service that implements the UTXO/Nullifier logic within the CoreJAM workflow. This decouples the heavy cryptography (ZK verification) from the state management (Nullifier tracking).
<ul>
<li>Refine (Stateless Verification): This phase acts as a massively parallel verifier. It ingests client-generated Work Packages containing ZK proofs. It executes the raw verification logic on the PVM, filtering out invalid proofs without touching the global state.</li>
<li>Accumulate (Nullifier Sequencer) This phase maintains the canonical Nullifier Set and the Merkle Tree Root.
<ul>
<li>
Input: Validated Work Results from the Refine phase.
</li>
<li>
Logic: It checks for Nullifier collisions (Double Spends) and updates the Merkle Frontier.
</li>
<li>
Concurrency: To handle the parallel generation of proofs against moving state, the service must implement a State Root History (Ring Buffer), allowing proofs generated against recent roots to settle validly.
</li>
</ul>
</li>
<li>Data Lake: this service could publish encrypted note ciphertexts directly to the JAM Distributed Data Lake. This creates a canonical, high-throughput stream that wallets can sync from without bloating the scarce Accumulate state with history.</li>
</ul>
Technical Requirements: For this Service to be viable, the PVM (RISC-V) may have expose Host Functions for pairing-friendly curves (BN254 or BLS12-381). Without these specific <code>ecalls</code>, SNARK verification may exhaust Core limits (unsure), rendering the service economically nonviable.
For privacy to be a first-class citizen, the JAM implementation must expose Host Functions for EC Pairings.
<hr>
Note: Everything proposed here is admittedly above my paygrade. Contrary to <a class="mention" href="/u/polka.dom">@polka.dom</a>’s advice to be assertive, I can’t say to be an expert on these topics. I’m a simple Solidity dev with some introduction to Noir and previous work in infrastructure.
However, I care deeply about privacy, JAM, and the core values of this ecosystem. I’m bringing this forward because I’m worried we might miss a critical train, one that is essential for societies relying on truly resilient sovereign systems.
This architecture might be complete bollocks. But from I’ve started to see, having some private state management as first-class citizen will become essential for blockchain tech. It may also be the case that all of this was already considered.

There will always have the debate of anonimity.
If we want PoP in governance, it should be anonymous. 
We never saw “democratic” systems without anonymous mechanims. No one should be able to know your own voting in the end.
Otherwise, you are subject to receive active pressure on your name or auto-censor what you say or vote.
You will have pros and cons about anonymity. 
Trolls are a plague. 
Voting anonymously is a requirement.

<h2><a name="p-35529-polkadot-news-1" class="anchor" href="#p-35529-polkadot-news-1" aria-label="Heading link"></a>Polkadot News</h2>
Track the progress of enabling the Elastic Scaling feature on Polkadot Asset Hub here <a href="https://github.com/paritytech/polkadot-sdk/issues/10425" class="inline-onebox" rel="noopener nofollow ugc">[ElasticScaling] Enable ElasticScaling on AHKusama and AHPolkadot · Issue #10425 · paritytech/polkadot-sdk · GitHub</a>
Follow the discussion around Social Recovery of accounts on Polkadot that happened during this month’s Technical Fellowship OpenDev call <a href="https://x.com/polkaworld_org/status/1993215565343936709" rel="noopener nofollow ugc">https://x.com/polkaworld_org/status/1993215565343936709</a>
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 passing unanimously <a href="https://polkadot.subsquare.io/referenda/1797" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1797</a>
The funding request for “ink! Alliance — PolkaVM Rust Smart Contracts on Polkadot Hub: ink! V6 Technical Delivery” is up for voting <a href="https://polkadot.subsquare.io/referenda/1796" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1796</a>
<h2><a name="p-35529-kusama-news-2" class="anchor" href="#p-35529-kusama-news-2" aria-label="Heading link"></a>Kusama News</h2>
The referendum to set KSM/DOT Asset Rate locations on Kusama Asset Hub (Post-Migration Restoration) is projected to enter the confirmation period today <a href="https://kusama.subsquare.io/referenda/615" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/615</a>

Polkadot Digest 26 November 2025

<ol>
<li>DAP has no external revenue; it only redistributes inflation.All DAP funds still come from Polkadot’s inflation, with no real cashflow entering the system. It merely reallocates a portion of validator rewards in a different formula, without improving the network’s financial sustainability.</li>
<li>DAP addresses the supply side, while Polkadot’s problem is on the demand side.Currently, blockspace has almost no paying demand. Whether coretime is cheap or not, there is little actual usage. With demand near zero, any allocation formula cannot create adoption.</li>
<li>The timing is wrong: DAP creates an illusion of action without real ecosystem growth.Polkadot needs users, dApps, developers, and enterprise adoption—not more complex economic formulas. While the mechanism itself is not inherently flawed, implementing it under weak demand risks being a case of misplaced priorities.</li>
</ol>

dandan

Diego

Proposal: Dynamic Allocation Pool (DAP)

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)

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)

THE RIGHT TO DISAPPEAR

Deciding

Whitelist for runtime upgrade to 2.0.3

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

Confirming

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

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

[Medium Spender] Referendum #617

- 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 simple summary of the PARITY INDEX project:

*   PARITY INDEX is a new DeFi project on Kusama.
*   It lets people bet on which of two things will perform better, like a race.
*   The first "race" is between Kusama and Polkadot's market value.
*   You can buy tokens that go up in price if the underdog catches up.
*   The system rewards people who believe in the underdog early and hold their tokens.
*   It is built to help the Kusama ecosystem grow.
*   The project is currently being tested.

Preparing

Introducing PARITY INDEX: A New Kusama Defi & Entertainment Hub Built Around Ratio Markets And On Chain Rivalries. Live for testing on Paseo

- Kusama spends KSM on grants that don't get paid back.
- This idea changes grants into loans that must be repaid.
- Loans go to companies that create stablecoins (like digital dollars).
- The treasury gets paid back in stablecoins, creating savings.
- This helps pay validators steadily without relying on KSM's price.
- Stablecoin growth is easy to measure and can't be faked.
- Vote YES to make the treasury self-sufficient.
- Vote NO to keep spending KSM without getting anything back.

Wish For Change: Make Kusama Treasury Self-Financing

[Whitelisted Caller] Upgrade Kusama Asset Hub to fellows release v2.0.3

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

Executed

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

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

referenda8

fellowship1

treasury29

discussions1385