candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

ETHRome 2025 x Polkadot by DevCult

DevCult

Data storage/availability

One-click actions on Substrate based chains

<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

Parity&rsquo;s position on forum moderation

Parity's position on forum moderation

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

Tech Talk

Intel SGX seems dead for blockchain applications

Lohann Paterno Coutinho Ferreira

My Experience with ink! and Why Rust Smart Contracts Matter for Polkadot

Woodfish

Rethinking Web3: When Trustless Systems Matter

SO/DA zone

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

Python Libraries Maintenance Continued Funding

Emiel Sebastiaan | JAMdot Technologies

[RFC Draft] ZK-Whiteblow: A ZK-Primitive to Solve Treasury Collusion &amp; Accountability

Diego

[RFC Draft] ZK-Whiteblow: A ZK-Primitive to Solve Treasury Collusion & Accountability

Addressing Concerns Related to Marketing Bounty Spends for BLAST Campaign

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

Ecosystem

A Case Study in Misaligned Incentives: The Polkadot UX Bounty

swenthebuilder

&ldquo;An oracle error on the Interlay platform is preventing lending users from making withdrawals.&rdquo;

"An oracle error on the Interlay platform is preventing lending users from making withdrawals."

Where did the 10 DOT minimum coretime price come from?

Xiscocv

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>I 100% agree regarding the misaligned incentives and the need to close this bounty. I don’t think anyone did anything wrong; it’s just the course of bureaucracy in effect, where being seen as doing something is more important than the result of that thing.</p>
<p>UX audits are the perfect example of this. They were done in the name of ‘doing something of value,’ but no thought was put into whether this really offered value to anyone outside those getting a free audit—or if recipients were only accepting them to avoid ruffling feathers.</p>
<p>The Polkadot-UI library was always destined to fail. The lack of experience was an issue, but the broken dev funnel was probably the biggest problem. It really does not matter how much it got promoted inside of Polkadot; it was not needed here. Those who would have used it have the knowledge to build their own tools, taking into account their own needs.</p>
<p>In the end, this is another failed experiment that solved nothing because it had no end goal, just a vague idea of the problem Polkadot is currently facing. I hope we can all learn something from this and move forward.</p>
<p>If I had a wish list for future DevEx/UI funding programs:</p>
<ul>
<li>
<p><strong>Pay based on market value:</strong> Funding should be based on the open market—can this person command this price elsewhere?</p>
</li>
<li>
<p><strong>Real goals with metrics:</strong> We need clear targets to measure success.</p>
</li>
<li>
<p><strong>Proper stewardship:</strong> The goal should be to spend only when necessary.</p>
</li>
<li>
<p><strong>Aligned Incentives (The “Rising Tide” Model):</strong> To help the program become almost self-funding, we should lock the DOT grant at the price it is given, but only unlock the funds upon hitting metrics. This acts as a massive incentive: if the work improves the ecosystem, the token price rises, and the grant becomes more valuable. A true “rising tide lifts all boats” approach.</p>
</li>
<li>
<p><strong>Performance-based Curators:</strong> Curator pay should be based on results, finally fixing the misaligned incentives.</p>
</li>
</ul>
<p>Thanks <a class="mention" href="/u/josep">@josep</a> for taking up this initiative. I hope this perspective adds value to the discussion.</p>

dandan

<p>I sent a message to Interlay’s official Discord community, but no one has come forward to explain and resolve the issue.</p>
<p>Is anyone else experiencing the same problem?</p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/8/841dd1f5ddbb5d76e099d2aaaaa8590a492ea77c.png" data-download-href="/uploads/short-url/iQKUL9A2FD02h8T6uMWys2gF8kc.png?dl=1" title="image" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/8/841dd1f5ddbb5d76e099d2aaaaa8590a492ea77c_2_690x392.png" alt="image" data-base62-sha1="iQKUL9A2FD02h8T6uMWys2gF8kc" width="690" height="392" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/8/841dd1f5ddbb5d76e099d2aaaaa8590a492ea77c_2_690x392.png, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/8/841dd1f5ddbb5d76e099d2aaaaa8590a492ea77c_2_1035x588.png 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/8/841dd1f5ddbb5d76e099d2aaaaa8590a492ea77c.png 2x" data-dominant-color="F1F0F3"><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">image</span><span class="informations">1190×677 24.9 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><strong>Topic</strong>: OpenGov Treasury Discussion &amp; Soft Commitment for Monthly Retroactive Reimbursements for Completed Work for Python Libraries Maintenance &amp; Development<br>
<strong>Proposer</strong>: JAMdot Technologies<br>
<strong>Start Date</strong>: January 2026<br>
<strong>Funding Request</strong>: Retroactive Reimbursement capped to 12.000 EUR per month for completed work<br>
<strong>Full Proposal</strong>: <a href="https://github.com/JAMdotTech/funding/blob/25d48e58dea76424332dffa409f34ddbe8ffb389/polkadot-opengov/README.md" rel="noopener nofollow ugc">GitHub Link</a></p>
<p>This proposal discusses a continuation of the multi-year efforts of Polkascan (active in the ecosystem since 2017, recipient of multiple Web3 Foundation Grants and sustained Treasury support from 2020 to 2024. Over this period, the team designed, implemented and maintained the Python Substrate Interface (now Python Polkadot SDK), SCALE codec library and associated cryptographic FFI libraries. Or summarized: if you use Python in the Polkadot ecosystem, you are using our open-source libraries.</p>
<p>Polkascan Foundation (the legal entity) was unwound at the end of 2024 and thus discontinued seeking OpenGov Treasury reimbursements.  In June 2024 Polkascan’s founders (Emiel &amp; Arjan)  started JAMdot Technologies to create a Python Implementation of JAM Protocol. In March 2025 JAMdot Technologies took over stewardship of Polkascan’s Python Libraries to ensure its continuation.</p>
<p>This proposal seeks an OpenGov Treasury soft commitment that, starting January 2026, JAMdot Technologies can submit monthly retroactive reimbursement requests for completed work of the continued maintenance and development of Python libraries used throughout the Polkadot ecosystem.</p>
<p>The intent of this proposal is not to request funds now, but to:</p>
<ul>
<li>
<p>Confirm that the Treasury recognizes ongoing Python maintenance as a legitimate, ecosystem-critical activity;</p>
</li>
<li>
<p>Establish a predictable framework for monthly, retroactive reimbursement;</p>
</li>
<li>
<p>Ensure continuity of the long-standing work previously carried out by Polkascan; and</p>
</li>
<li>
<p>Signal that JAMdot Technologies can operate on a monthly retroactive basis for completed work without needing a full governance process for each minor maintenance reimbursement.</p>
</li>
</ul>
<p>This structure is aligned with the newly published Web3 Foundation OpenGov Guidelines: it aims to minimize proposal overhead for recurring essential work, while keeping the community fully in control of funding decisions and able to halt or adjust reimbursements if expectations are not met. Full details on this alignment can be found in appendix 2 of our proposal: <a href="https://github.com/JAMdotTech/funding/blob/25d48e58dea76424332dffa409f34ddbe8ffb389/polkadot-opengov/README.md" rel="noopener nofollow ugc">GitHub Link</a></p>
<p><strong>Metrics of our Libraries (per 10 December 2025)</strong></p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/9/9cef1d785ce36a6cb8e1679c401fa94f8fca1492.png" data-download-href="/uploads/short-url/moiMNS0L7nwwVsoDW3UJcqBAqnE.png?dl=1" title="image" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/9/9cef1d785ce36a6cb8e1679c401fa94f8fca1492.png" alt="image" data-base62-sha1="moiMNS0L7nwwVsoDW3UJcqBAqnE" width="690" height="240" data-dominant-color="F0F1F2"><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">image</span><span class="informations">1141×398 20.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>
<p>We look forward to the community feedback.<br>
Emiel Sebastiaan on behalf of JAMdot Technologies</p>

<p>It used to be like that in the past, but the problem was that there were individuals who bought all the cores when they were extremely cheap and controlled the supply, and therefore the future price. Imagine one person buying 100% of the cores at $1; afterward, they could sell the cores at whatever price they wanted. That’s why a $10 minimum was implemented as a safety measure.</p>

<h1><a name="p-36115-rfc-draft-project-zk-whiteblow-a-zk-primitive-to-solve-treasury-collusion-accountability-1" class="anchor" href="#p-36115-rfc-draft-project-zk-whiteblow-a-zk-primitive-to-solve-treasury-collusion-accountability-1" aria-label="Heading link"></a>[RFC Draft] Project ZK-Whiteblow: A ZK-Primitive to Solve Treasury Collusion &amp; Accountability</h1>
<h2><a name="p-36115-collusion-thrives-in-the-dark-lets-use-zero-knowledge-to-turn-on-the-lights-2" class="anchor" href="#p-36115-collusion-thrives-in-the-dark-lets-use-zero-knowledge-to-turn-on-the-lights-2" aria-label="Heading link"></a>Collusion thrives in the dark. Let’s use Zero-Knowledge to turn on the lights.</h2>
<p><strong>Category:</strong> Governance / Tech &amp; Engineering<br>
<strong>Tags:</strong> <span class="hashtag-raw">#ZeroKnowledge</span> <a class="hashtag-cooked" href="/c/governance/11" data-type="category" data-slug="governance" data-id="11" data-style-type="square"><span class="hashtag-icon-placeholder"><svg class="fa d-icon d-icon-square-full svg-icon svg-node"><use href="#square-full"></use></svg></span><span>Governance</span></a> <a class="hashtag-cooked" href="/tag/treasury" data-type="tag" data-slug="treasury" data-id="13" data-style-type="icon" data-icon="tag"><span class="hashtag-icon-placeholder"><svg class="fa d-icon d-icon-square-full svg-icon svg-node"><use href="#square-full"></use></svg></span><span>treasury</span></a> <span class="hashtag-raw">#Rust</span> <span class="hashtag-raw">#AntiCollusion</span></p>
<h2><a name="p-36115-the-problem-the-whale-in-the-room-3" class="anchor" href="#p-36115-the-problem-the-whale-in-the-room-3" aria-label="Heading link"></a>The Problem: The “Whale” in the Room</h2>
<p>Polkadot’s OpenGov is one of the most advanced decentralized governance systems in the world. However, like all weighted-voting systems, it suffers from the Principal-Agent Problem:</p>
<ul>
<li><strong>Concentration:</strong> High token concentration allows large holders (“Whales”) to push through Treasury proposals that may not align with the collective good.</li>
<li><strong>Opacity of Execution:</strong> Once a Treasury Referendum passes and funds are disbursed, on-chain tracking stops. We rely on “social reports” to verify if the marketing campaign actually happened or if the software was actually built.</li>
<li><strong>The Silence of Insiders:</strong> Team members, sub-contractors, or multi-sig signers often see mismanagement or fraud (e.g., funds siphoned off for personal use) but stay silent due to fear of doxxing, retaliation, or blacklisting by influential whales.</li>
</ul>
<p>Collusion becomes profitable because accountability is low. If a Whale votes to fund a crony project, and that project embezzles the funds with no consequences, the Treasury bleeds.</p>
<h2><a name="p-36115-the-proposal-whiteblowing-whistleblowing-as-a-service-4" class="anchor" href="#p-36115-the-proposal-whiteblowing-whistleblowing-as-a-service-4" aria-label="Heading link"></a>The Proposal: “Whiteblowing” (Whistleblowing-as-a-Service)</h2>
<p>I propose integrating a Byzantine-Fault Tolerant ZK-Primitive directly into the governance stack (potentially as a system parachain or a Pallet).</p>
<p>“Whiteblow” is a protocol that allows insiders to cryptographically prove financial misconduct or data mismatches regarding a funded proposal without revealing their identity.</p>
<p>It changes the game theory of collusion:</p>
<ul>
<li><strong>Current State:</strong> Looting the Treasury is safe if you have the votes.</li>
<li><strong>Whiteblow State:</strong> Looting is high-risk because any insider (dev, accountant, multi-sig holder) can anonymously prove the fraud, slash the project’s staked DOT, and claim a bounty.</li>
</ul>
<h2><a name="p-36115-how-it-works-the-architecture-5" class="anchor" href="#p-36115-how-it-works-the-architecture-5" aria-label="Heading link"></a>How It Works (The Architecture)</h2>
<p>We have built a Proof-of-Concept in Rust using the Twisted ElGamal encryption scheme on the Ristretto255 curve (the same family as Polkadot’s sr25519).</p>
<h3><a name="p-36115-the-protocol-flow-6" class="anchor" href="#p-36115-the-protocol-flow-6" aria-label="Heading link"></a>The Protocol Flow:</h3>
<p><strong>The Commitment:</strong> When a team requests Treasury funds, they must register a set of “Insider Keys” (pubkeys of team members/signers) and lock a portion of tokens (or future vesting) as a bond.</p>
<p><strong>The Detection:</strong> An insider detects a discrepancy (e.g., The on-chain report claims $100k for “Vendor X”, but the internal invoice shows $10k or a transfer to a personal wallet).</p>
<p><strong>The ZK-Proof:</strong> The insider runs a client-side Rust binary that generates a Zero-Knowledge Consistency Proof:</p>
<ul>
<li>Encrypts the discrepancy amount (Twisted ElGamal).</li>
<li>Proves the math is correct (Chaum-Pedersen).</li>
<li>Attests membership in the “Insider Set” (Schnorr/Ring Signature) without revealing which insider they are.</li>
</ul>
<p><strong>The Slash:</strong> The network verifies the proof. If valid, the smart contract automatically slashes the project’s bonded DOT.</p>
<p><strong>The Bounty:</strong> The slashed funds are split: burned (deflationary) and sent to the whistleblower’s fresh address (Bounty).</p>
<h2><a name="p-36115-why-this-fits-polkadot-7" class="anchor" href="#p-36115-why-this-fits-polkadot-7" aria-label="Heading link"></a>Why This Fits Polkadot</h2>
<ul>
<li><strong>Rust Native:</strong> The entire toolkit is built in Rust using curve25519-dalek, ensuring compatibility with Substrate and WASM runtimes.</li>
<li><strong>Treasury Efficiency:</strong> It acts as a “Decentralized Auditor.” Instead of paying Big 4 firms to audit huge proposals, we crowdsource integrity to the people closest to the data.</li>
<li><strong>Sybil Resistance:</strong> Proofs are bound to specific BountyIDs and key sets, preventing spam.</li>
</ul>
<h2><a name="p-36115-technical-deep-dive-8" class="anchor" href="#p-36115-technical-deep-dive-8" aria-label="Heading link"></a>Technical Deep Dive</h2>
<p>The core logic relies on a Non-Interactive Sigma Protocol (Fiat-Shamir).</p>
<ul>
<li><strong>Encryption:</strong> We use Twisted ElGamal to allow the network to operate on encrypted “misconduct values” (e.g., checking if Discrepancy &gt; 0) without seeing the raw data initially.</li>
<li><strong>Binding:</strong> We use a Chaum-Pedersen proof to bind the Intent (The Proposal ID) to the Evidence (The encrypted mismatch). This prevents “replay attacks” where a whistleblower tries to slash the wrong project.</li>
</ul>
<p><strong>Code Reference:</strong> You can review the cryptographic primitives and the BFT logic in our open repository: <a href="https://github.com/labormedia/zk-whiteblow" rel="noopener nofollow ugc">zk-whiteblow</a></p>
<h2><a name="p-36115-request-for-comment-9" class="anchor" href="#p-36115-request-for-comment-9" aria-label="Heading link"></a>Request for Comment</h2>
<p>Looking for feedback from the community, specifically:</p>
<ul>
<li><strong>Integration:</strong> Should this live as a standalone Parachain offering “Audit Services” to the whole ecosystem, or as a Pallet integrated into the Asset Hub?</li>
<li><strong>Economic Parameters:</strong> What is the ideal % for the Whistleblower Bounty to incentivize honesty without encouraging frivolous reports?</li>
</ul>
<p><strong>Diego Correa Tristain</strong><br>
Polkadot Blockchain Academy, Cohort 3</p>

<h2><a name="p-36112-polkadot-news-1" class="anchor" href="#p-36112-polkadot-news-1" aria-label="Heading link"></a>Polkadot News</h2>
<p>The Polkadot Builder Party hackathon full report has been published on the Polkadot forum <a href="https://x.com/Web3foundation/status/1999416664555934124" rel="noopener nofollow ugc">https://x.com/Web3foundation/status/1999416664555934124</a></p>
<p>The referendum "Advancing OpenGov’s Core: Governance Enhancements &amp; Automated Analytics, Cost Optimization, and Infrastructure Expansion – Retroactive Funding Request” has been submitted by Polkassembly <a href="https://polkadot.subsquare.io/referenda/1814" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1814</a></p>

Radhakrishna Dasari

Polkadot Digest 12 December 2025

<p>Excellent work and outcome, congrats to everyone that worked hard and contributed to make this happen and make it amazing <img src="https://emoji.discourse-cdn.com/twitter/clap.png?v=15" title=":clap:" class="emoji" alt=":clap:" loading="lazy" width="20" height="20"></p>
<aside class="quote no-group" data-username="radha" data-post="1" data-topic="16254">
<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/radha/60/9935_2.png" class="avatar"> radha:</div>
<blockquote>
<p>A comprehensive <a href="https://hackmd.io/kDVuV888R8a7OPeZhqNlXg" rel="noopener nofollow ugc">feedback analysis</a> has been shared with Parity’s DevEx team.</p>
</blockquote>
</aside>
<p>A goldmine of information/signal, thanks for compiling these.</p>

Karim | Product Engineering @ Parity

Polkadot Builder Party Hackathon Report

<p>Hello Crane, thanks for answering directly. I have a few follow up questions based on your reply.</p>
<aside class="quote no-group" data-username="Crane" data-post="11" data-topic="16247">
<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/crane/48/6535_2.png" class="avatar"> Crane:</div>
<blockquote>
<p>Curators operate without legal entity protection. They’re individuals with publicly identified addresses. When you’re distributing tournament prize pools, you’re sending funds to dozens of unknown recipients around the world without KYC. Creating a direct on-chain trail from identified curator addresses to mass distributions like that exposes those individuals to personal liability in ways that are genuinely risky.</p>
</blockquote>
</aside>
<p>You are saying the Marketing Bounty curators operate without legal entity protection. However, <a href="https://polkadot.subsquare.io/referenda/1416" rel="noopener nofollow ugc">Opengov #1416</a> is proposed, voted on and executed in March 2025 <strong>specifically to provide a legal vehicle for the Marketing Bounty</strong>, including the ability to contract and process fiat payments through the Polkadot Community Foundation.</p>
<p>It states:</p>
<blockquote>
<p>This proposal establishes an overarching framework through which the Marketing Bounty can execute formal contracts with service providers on behalf of the Polkadot DAO. The Polkadot Community Foundation will act as the legal counterparty for these standardized contracts.<br>
(…)<br>
Article 3 - Framework</p>
<ol>
<li>The objective of this framework is to create a streamlined (fast and affordable) process for providing SPs with a legal counterparty and fiat payments if they require them.</li>
<li>The MB is permitted to instruct the PCF to process fiat payments and manage contractual relationships and related administrative work (such as KYB procedures) with SPs.<br>
(…)</li>
</ol>
</blockquote>
<p>Given that framework, why was the PCF not used in this case? Based on the timeline, there does not seem to have been a time constraint. As you confirmed, <strong>the funds stayed in your personal Kraken account for 35 days</strong>, from 3 November to 8 December.</p>
<aside class="quote no-group" data-username="Crane" data-post="11" data-topic="16247">
<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/crane/48/6535_2.png" class="avatar"> Crane:</div>
<blockquote>
<p>This wasn’t to hide anything nefarious - it was to protect the Marketing Bounty curators.</p>
</blockquote>
</aside>
<p>One more point, and please correct me if I am wrong. From the earlier discussions, my understanding is that the <strong>other curators did not know this routing would be used</strong>. If that is accurate, why were the other curators not informed in advance, especially if the main purpose was to protect curators from personal risk?</p>

Bastian Köcher

<aside class="quote no-group" data-username="dhogberg" data-post="11" data-topic="16215">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://avatars.discourse-cdn.com/v4/letter/d/71e660/48.png" class="avatar"> dhogberg:</div>
<blockquote>
<p>We don’t need more cheerleading. We need honesty, market awareness, the courage to drop old vendettas, embrace competition, and react timely to change.</p>
</blockquote>
</aside>
<p><img src="https://emoji.discourse-cdn.com/twitter/100.png?v=15" title=":100:" class="emoji only-emoji" alt=":100:" loading="lazy" width="20" height="20"> <img src="https://emoji.discourse-cdn.com/twitter/100.png?v=15" title=":100:" class="emoji only-emoji" alt=":100:" loading="lazy" width="20" height="20"><br>
This should be painted on the walls!</p>

Irena Satke

Tom | Stake Plus

To the Polkadot Community: A Final Word from a Five-Year Holder

<p>Yes, I’ve seen the Excel file, but I still need to see <strong>three accredited pieces of evidence</strong>, which at the moment are missing:</p>
<ol>
<li>
<p><strong>An image or video of the supposedly malicious website</strong>, including a brief explanation of the potential risk. This is necessary to verify that the threat is real and not just a false positive.</p>
</li>
<li>
<p><strong>Emails with the hosting provider</strong> proving your involvement in taking the site down — or at least a copy of a form you submitted. Something concrete that shows actual action was taken.</p>
</li>
<li>
<p><strong>A confirmation that the site was actually removed thanks to your intervention</strong>, not simply a list of URLs for us to check ourselves.</p>
</li>
</ol>
<p>We cannot pay for a script that flags thousands of supposedly malicious websites <strong>without proper, verifiable evidence</strong>.</p>

Anti-Scam Bounty Deep Dive (Revived)

<p>Thank you very much for offering support. <a class="mention" href="/u/piewol">@PieWol</a> from W3F will reach out to you to discuss this and share the progress on conformance testing effort.</p>

danicuki

Ensuring JAM Development Sustainability: Is It Time for a Dedicated JAM Bounty Program?

<p>Congrats team.</p>
<p>I believe that the work carried out by the team behind the X account is very important.</p>
<p>The transparency and professionalism they demonstrate is very noticeable.</p>
<p>Furthermore, it is essential for maintaining cohesion between the different Spanish-speaking communities.</p>

Lorena Blockya

Polkadot Spanish X account management - Report (Aug–Nov 2025)

<p>What a sh*t show.<br>
Censorship will be the final nail in the coffin for dot. Also using a treasury funded youtuber (Jay) to discredit specific people posting in the forum is abysmal.</p>
<p>I’m out of here.</p>
<p>Maybe I’ll check back in 5 years… but I doubt much will have changed.</p>

<h2><a name="p-36049-polkadot-news-1" class="anchor" href="#p-36049-polkadot-news-1" aria-label="Heading link"></a>Polkadot News</h2>
<p>The issue with Polkadot OpenGov treasury payouts of assets like USDC/USDT using the older XCM version address is fixed and will go live in the next runtime upgrade <a href="https://github.com/polkadot-fellows/runtimes/pull/1019" rel="noopener nofollow ugc">https://github.com/polkadot-fellows/runtimes/pull/1019</a></p>
<p>Retroactive funding request for Statescan maintenance for the year 2025 has been submitted <a href="https://polkadot.subsquare.io/referenda/1813" rel="noopener nofollow ugc">https://polkadot.subsquare.io/referenda/1813</a></p>
<p>Tune in to this live stream on Dec 12th (tomorrow) at 1 PM UTC hosted by Polkadot Africa, featuring Bill Laboon, the VP of the Ecosystem at Web3 Foundation, speaking about the Polkadot Hub <a href="https://x.com/PolkadotAfrica/status/1996550050198229241" rel="noopener nofollow ugc">https://x.com/PolkadotAfrica/status/1996550050198229241</a></p>
<h2><a name="p-36049-kusama-news-2" class="anchor" href="#p-36049-kusama-news-2" aria-label="Heading link"></a>Kusama News</h2>
<p>The referendum to approve unlocking the Robonomics parachain to restore its block production is passing unanimously <a href="https://kusama.subsquare.io/referenda/622" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/622</a></p>

Polkadot Digest 11 December 2025

<aside class="quote no-group quote-modified" data-username="GabrielJ" data-post="22" data-topic="16187">
<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/gabrielj/60/6811_2.png" class="avatar"> GabrielJ:</div>
<blockquote>
<p>…anyone keen on staying anonymous can just create a new wallet… I wonder if it is really necessary?</p>
</blockquote>
</aside>
<p>It is necessary because a “new wallet” provides anonymity, but it does not provide credibility.</p>
<p>If a random fresh wallet claims a project is faking metrics, it is easily dismissed as FUD or noise. The ZK-proof allows that fresh wallet to prove: “I am a verifiable insider/signer” without revealing which one.</p>
<p>This distinction is critical for the economic correction:</p>
<ol>
<li>Game Theoretic Correction (The Reward)</li>
</ol>
<p>As you noted, currently “snitching has no reward.” To break the silence, we must pay the whistleblower.</p>
<p>• We cannot justify paying a random “new wallet” because we can’t verify their access or intent.</p>
<p>• We can pay a ZK-verified wallet because the proof guarantees they are a stakeholder. This allows us to safely automate the bounty payout, turning the “Traitor” into “The Reformer” with full Reputational Amnesty.</p>
<ol start="2">
<li>Liability &amp; Execution (The Auditor)</li>
</ol>
<p>Relying on OpenGov for execution is slow and political.</p>
<p>In this model, a neutral third party (The Auditor) or a ZK-Coprocessor bears the liability for executing the logic. They verify the encrypted ZKP (which proves insider status + fraud evidence) and trigger the halt immediately.</p>
<p>The ZKP acts as an anonymous credential, it hides identity and binds agency from ‘The Reformer’ (The Insider) to ‘The Auditor’ (The Executor).</p>

Marketing Bounty Deep Dive (Revived)

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)

Executed

Whitelist for #622

- Four To The Floor (FTTF) is a music and video network from the UK.
- It started on TV and is now a digital platform owned by artists and fans.
- Their first event, Block Music Power, is streaming live online.
- They plan to host more live events, music shows, and documentaries.
- FTTF wants to support artists and fans fairly, not take advantage of them.
- People involved can help make decisions and share in the success.
- They use special digital tools and money systems to run the platform.
- Everyone is invited to join and be part of the community.

Preparing

Wish for change: Four To The Floor x Kusama

- We want to partner with Mattereum to turn a special motorcycle into a digital token on Kusama.
- This motorcycle is a rare BMW collaboration, one of only two ever made.
- It will be the first real-world asset on Kusama, with legal protection in many countries.
- This project will help bring new technology and skills to Kusama.
- The goal is to help Kusama create stable assets and build a strong financial foundation.
- The motorcycle is provided by Decent Partners, who support creative projects.
- We will create a digital version of the bike and special artwork for the community.
- The bike can also be used for future events and promotions.

Wish for Change: Pilot the first physically-backed and guaranteed Real World Asset (RWA) on Kusama Asset Hub via a partnership with Mattereum and tokenisation of the Auto Fabrica Type 18 motorcycle

- Robonomics parachain stopped making new blocks after an update.
- The update was meant to change how blocks are made, but it didn't work as planned.
- Because of this, some services like sensors and exchanges are not working fully.
- The team has a fix ready to solve the problem.
- They need permission to unlock the parachain to apply the fix.
- Once fixed, block production will start again and everything will go back to normal.
- After fixing, they will share what happened and improve testing to avoid future issues.

[Whitelisted Caller] Referendum #622

**Parity Index: Kusama's DeFi and Entertainment Hub**

- Parity Index is a new platform on Kusama for fun finance and entertainment.
- It lets people bet on contests, like "Kusama vs. Polkadot," using tokens.
- You can support the underdog and earn rewards if they perform well.
- It uses a special system called "ratio markets" to track how close rivals are.
- You can trade using KSM, DOT, or a stablecoin called dUSD.
- Part of each trade goes into a bonus pool for loyal supporters.
- It’s being tested now and will be fully open for everyone to use.
- Future contests could include sports, movies, or other crypto rivalries.

TimedOut

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

- Kusama wants to change how it gives out money.
- Instead of giving KSM tokens away forever, it will lend them.
- The loans go to companies that make stablecoins (like digital dollars).
- These companies pay back the treasury with stablecoins.
- This builds a savings fund that doesn't depend on KSM's price.
- Validators can be paid with stablecoins, making their income steady.
- Stablecoin growth is easy to measure and hard to fake.
- Vote YES to make Kusama more independent, or NO to keep things the same.

Wish For Change: Make Kusama Treasury Self-Financing

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

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

referenda6

fellowship1

treasury24

discussions1385