candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

A real-world Polkadot wallet drain &amp; why we now need

A real-world Polkadot wallet drain & why we now need

Seeking Input: Developer Skill Pathways for DotCodeSchool

Testnets: Paseo “officially” becomes the Polkadot testnet; temporary Passet Hub chain for smart contracts testing

Rebecca Turner

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:

Corax CoLAB

Welcome to the Polkadot Forum 👋

Getting started: Read this first

Polkadot Forum Super Admin

Questions about staking DOT

A place for long-term, deep thinking on Polkadot technology.

Tech Talk

Ideal Labs | Updates &amp; Next Steps

Carlos M

Ideal Labs | Updates & Next Steps

Dedot Now Supports pallet-revive and ink! v6 through Ink!ubator 2.0

Thang X. Vu

PAPI and Runtime Upgrades: Making DApps Truly Resilient

Bastian Köcher

Governance discussion about the future of Polkadot and Kusama.

Governance

Bitcoin Reserve for the Polkadot Treasury

tacolopo

The Future of Decentralized Voices — Our Plan to Retune DV

bill_w3f

Initial Coretime Pricing

Diego

Everything that’s going on in the ecosystem, and what you wish would be going on in the ecosystem.

Ecosystem

From Zero to a Community: How We Started in Polkadot Americas

Polkadot Americas

We Took Over Consensus 2025 — And the Ecosystem Showed Up Big

José Rabasso

We need a more efficient job market for the ecosystem

Welcome to the Ambassador Category! Please use this space to discuss anything and everything related to the Polkadot Ambassador Programme.

Ambassador Programme

:television: Polkadot x Discovery Channel: Rare Opal Amulet Proposal Discussion

📺 Polkadot x Discovery Channel: Rare Opal Amulet Proposal Discussion

Official statement of the Advisory Board of the Polkadot Ambassador Fellowship

Lucy Coulden

Hispanic Chapter of Polkadot Ambassadors Manifesto

Thank you so much, Florentina, for your thoughtful words and support. It really means a lot to us. Knowing that you felt welcomed and inspired reminds us why we’re doing this to build a truly inclusive and decentralized Dotsama community that connects people across the entire continent. We’re excited to keep growing together!

Hello everyone. this is my take on Consensus and Where I think we should also expand our focus to kick-start Business development.
I did attend/staffed the Polkadot booth at this event to see the attendance and how things where moving. The booth was well staffed and most of the people in the booth where busy with the attendance. While there I did guided some businesses to look at the technology for their own benefits. The attendance was mainly Crypto natives or where interested in the technology mainly crypto$.
I do believe that Targeting Web3 is a most, this is where most of the early adopters and power users are, so servicing this market was fulfilled.
After reflecting and looking at the attendance at Consensus 2025 Toronto, I did attended WebSummit 2025 in Vancouver, and it blew my expectations away, in terms of attendance and hunger for the technology itself, this was a huge event with hundreds of teaching sessions with lots of attendees, in most cases full rooms packed with people. This is putting me in the path of thinking that Polkadot needs to be represented in this Massive event with most of the developers using Web2 technologies and with no knowledge of decentralized Web3 technologies. This will be a big undertaking in terms of servicing this market, the booth staffing needs to change, Technology messaging needs to also change to target this demographic properly, teaching sessions would be a big component of this. I’m putting a team together to tackle this and will commit to run it for a full year. Partnering with the PBA and creating a way to funnel most developers there will be of upmost importance along with bringing Visionaries to many Panels to talk about the technology and its possibilities in today’s market conditions.
The booth staffing will consist mainly of Business people with a high degree of knowledge of how Businesses work in today Web2 tech stack, they will be able to paint the Picture of their Businesses taking advantage of the Web3 tech stack, along with highlighting the savings of doing so. we also plan to have a close room for presentations in the booth with small groups of 10 people at he time.
If we want mainstream developers to start using the technology stack this is the best opportunity i see to do so, and if we are effective, i can foresee creating enough of a critical mass to launch the Polkadot teck into the forefront of all Crypto-technology industry.
I hope to be working with the smart agents in the ecosystem to achieve this.
Jose No-Name

I honestly don’t understand the so-called “recruitment difficulties.” All of my friends are in tech-related fields, with 7 to 8 years of studies like many people in France and yet they earn around €2,000 a month. That’s what you get with one of the most generous social systems in the world, but one that fails to reward real skills appropriately.
Meanwhile, the Polkadot ecosystem offers eye-watering compensation: I’ve been reading OpenGov proposals daily for months I’ve seen $1,000 per day gigs, €20,000 monthly salaries, and €800 for just a few hours of freelance work.
Polkadot also has a massive presence in Asia, where wages can be up to four times lower than in France. So how are we still talking about talent shortages?
More and more people are starting to believe that some project leaders are simply pocketing the majority of the funds, offering interns €500 per month offers that are, unsurprisingly, being rejected.
The real question is: do we really lack qualified people, or do we just refuse to pay them what they’re worth?
“I Stopped Trusting Systems” GW

Laura Brown

The usual strategy: no one is paid by Polkadot, no one is funded by the treasury, Jam isn’t funded by Polkadot either all his DOTs were magically printed out of thin air. Honestly, the Fed should ask us for a tutorial on how to print magic money.Thank you for your questions <a class="mention" href="/u/cpiccard">@cpiccard</a> they’re always really interesting to read.

Overdue for Results

I don’t see the logic here - nor do I think “the community” can be represented by a blogpost response, as the vast majority of DOT holders are aloof to these discussions. How could it possibly make sense to devalue your currency by selling it for a different one? Why would anyone buy DOT if Polkadot is itself selling it? How does this not incentivize people to also sell their DOT for BTC?

Zhoueddie

Dear community,
At Ideal Labs, we’ve been heads-down advancing key components of our protocol including the trustless Drand bridge, randomness subscription management, indexer module, and consumer mechanisms such as the new Consumer pallet and the !ink IDN-Client library for retrieving randomness. We’re also excited to share that our audits have been officially completed. Full details can be found in <a href="https://drive.google.com/file/d/1ZuhEpz7yic-OdfNAiEaWtMAyqyNu4LFY/view?usp=sharing" rel="noopener nofollow ugc">Progress Report #4</a>.

Heyhey, thanks for your comment I agree and I think papi, dedot and reactive-dot do a good job in providing the logic wagmi offers. Especially reactive-dot with e.g. <code>useAccounts</code>, <code>useMutation</code>, …
This initiative is more on the component side while it would rely on hooks from other libraries and only add or compose new ones when needed. That said, I think there is room for collaboration and synergies but moving hooks to a hooks library and maintain them separately would surely be better imo.

niftesty

Alberto

UX Bounty - Request for Feedback: A Unified UI Component Library

Thanks <a class="mention" href="/u/birdo">@Birdo</a> for starting this thread, and I agree Polkadot indeed needs to simplify dapp development and enable faster, more expressive ways to build. Looking at other ecosystems such as Base, mini dapps is indeed showing strong developer adoption!
<h3><a name="p-30380-hackathons-1" class="anchor" href="#p-30380-hackathons-1"></a>Hackathons</h3>
Building on your first next step to start with market research on mini apps, I’d also suggest we tie that research back into the hackthons that are now being organised around the Hub. We can provide builders with curated mini-dapp ideas and primitives, collect feedback to better understand what’s working and what’s not, and even continue conversations with strong builders and get their apps into wallets or the Polkadot app. Great teams are organising hackathons and the latest surveys contain tremendously valuable information into where we need to improve (tooling, documentation, onboarding, etc.) (MAKE THIS PUBLIC!).
And to <a class="mention" href="/u/karim">@karim</a>’s point about identifying the right developer audience, why don’t we start with hackathon devs. From there we can discover what types of developers are excited to build on Polkadot, what resonates with them, and what friction they face.
(E.g. 16th of July there is a hackathon in Berlin organised by webzero)
<h3><a name="p-30380-incentives-and-revenue-models-2" class="anchor" href="#p-30380-incentives-and-revenue-models-2"></a>Incentives and revenue models</h3>
Building on <a class="mention" href="/u/karim">@karim</a>’s feedback around incentives and <a class="mention" href="/u/alex-itooin">@alex-itooin</a>’s ideas on revenue models, I think there are a few promising directions we could explore:
<ul>
<li>Builder incentives at the protocol level—such as smart contract fee sharing.</li>
<li>Subscription-based models—enabling dapps where users pay recurring fees instead of per interaction. This could offer more predictable income and better UX.</li>
</ul>
These are ideas we’re actively exploring for Pop Network, as we believe mechanisms like these are essential not only to incentivise developers to launch and maintain dapps on Polkadot, but also to attract new developers to the ecosystem in the first place.
To be competitive, a chain must offer state-of-the-art features that match or exceed what’s available in other ecosystems. Without that, it’s hard to justify the switch or investment from developers building elsewhere.
<h3><a name="p-30380-pop-cli-ai-templates-onboarding-3" class="anchor" href="#p-30380-pop-cli-ai-templates-onboarding-3"></a>Pop CLI: AI, Templates &amp; Onboarding</h3>
On the topic of AI that <a class="mention" href="/u/alex-itooin">@alex-itooin</a> raised—that’s exactly the kind of functionality we’re working to bring into Pop CLI. In our <a href="https://polkadot.polkassembly.io/post/3252" rel="noopener nofollow ugc">upcoming proposal</a> (please provide feedback), we’ll be introducing:
<ul>
<li>AI-assisted developer workflows (e.g. “I want to build a token swap app” → scaffolded project).</li>
<li>Frontend scaffolds to go from zero to dapp instantly.</li>
<li>Tutorials and video content to onboard and support developers more effectively.</li>
</ul>
This closely aligns with <a class="mention" href="/u/liminal">@liminal</a>’s analysis of what scaffold-eth did well. With Pop CLI, we aim to bring a similar experience to Rust-based developers on Polkadot—lowering the barrier to entry by providing resources and building community.
Daan | R0GUE

Daan van der Plas

Alex

Mini Apps on Polkadot

<h2><a name="p-30385-polkadot-news-1" class="anchor" href="#p-30385-polkadot-news-1"></a>Polkadot News</h2>
A proposal for a framework for “Mini Apps” has been posted on the Polkadot Forum. <a href="https://forum.polkadot.network/t/mini-apps-on-polkadot/13359" class="inline-onebox">Mini Apps on Polkadot</a>
Referendum 1608, proposing that the Polkadot Community Foundation launch the Polkadot Payment Card, is passing with 99% in favor. <a href="https://polkadot.polkassembly.io/referenda/1608" class="inline-onebox" rel="noopener nofollow ugc">Polkassembly - Referendum #1608</a>
Referendum 1614, proposing funding for the Polkadot Ambassador Fellowship, is currently failing with 0.1% in favor. <a href="https://polkadot.polkassembly.io/referenda/1614" class="inline-onebox" rel="noopener nofollow ugc">Polkassembly - Referendum #1614</a>
<h2><a name="p-30385-kusama-news-2" class="anchor" href="#p-30385-kusama-news-2"></a>Kusama News</h2>
Referendum 536, proposing funding for “Kusama (ft. Polkadot) x Arcadia: The Spider”, is currently failing with 1.5% in favor. <a href="https://kusama.polkassembly.io/referenda/536" class="inline-onebox" rel="noopener nofollow ugc">Polkassembly - Referendum #536</a>
Referendum 537, proposing a novel locking mechanism for staking rewards via WFC, is passing with 97.9% in favor. <a href="https://kusama.subsquare.io/referenda/537" rel="noopener nofollow ugc">https://kusama.subsquare.io/referenda/537</a>

Polkadot Digest 16 Jun 2025

The issue I see with this is that those individuals will still need to follow every ref posted to determine if they have applicable domain expertise or not. Or what if their expertise is just 1 component of the ref, where do we/they draw the line?
I think it’s a minimal amount of work to know if something is at least partially relevant to you. But 1) we assume they are not going to vote on everything - it’s OK if things fall through the cracks for DV-Lights and 2) we are not going to be checking on every vote. We simply don’t have the resources. Of course they are going to vote only on things that are interesting to them, and we can expect they will also vote on things that are out of their expertise.

Has anyone explored how merchandise like <a href="https://polkadotbarstore.com/" rel="noopener nofollow ugc">Polkadot CHocolate Bars</a> contributes to building and promoting the Polkadot ecosystem? In what ways do you think branded products help increase community engagement and awareness of Polkadot’s interoperability and innovation within the blockchain space? Would love to hear your thoughts on the impact of ecosystem-related merchandise beyond just the technology!

magisk zip

Polkadot Ecosystem Featuring Polkadot Bar

This would be awesome from the opal idea and it being on discovery would be cool too 
Feel like the NFTs should like get a reward attached; like giving the opal it’s own token under the polkadot chain (like a memecoin) which will be given to the holders
Just my idea on it

Thank you for sharing. I don’t think it’s aggressive; it’s high time everyone rolled up their sleeves, accepted reduced pay, and tightened their belts.
For the past five years, many venture capitalists have struggled to make so much as a single profit, enduring one loss after another. Meanwhile, other actors in the systemsenior executives, managers, or what’s commonly called “the community”collect comfortable, undeserved salaries each month, regardless of their performance.
This glaring inequality brings to mind the irony of the famous line attributed to Marie‑Antoinette under the Ancien Régime: “Let them eat cake!”a perfect illustration of the powerful’s total disconnect from the people’s misery.
When the gap widens between the losses borne by the majority and the sterile gains pocketed by a minority, anger simmers; the analogy with the out‑of‑touch queen has perhaps never been more fitting.
However, as an avid reader of OpenGov discussions on PolkaAssembly, I’ve noticed a shift over the past week. 
DAOs are becoming increasingly mindful of project funding costs and their actual effectiveness within the ecosystem. 
Yes, times are tough but this kind of scrutiny is often necessary before we can enter a golden age. 
Thank you to everyone who has significantly increased their vigilance with the shared goal of reducing costs and maximizing impact.

Anaelle LTD

Create « Ministry of Transparency »

I love the idea, the community in Argentina is huge.
Is this event already confirmed? Or is it still subject to the proposal approval? 
Could you share the treasury proposal link with us if there’s already one?

Juan | Ideal Labs

Sub0 + Decoded = sub0 symbiosis - A new, highly experiential Polkadot flagship conference

We’re thrilled to announce that <a href="https://docs.dedot.dev/" rel="noopener nofollow ugc">Dedot</a> has officially added support for pallet-revive &amp; ink! v6 interaction in the latest version (<a href="https://github.com/dedotdev/dedot/releases/tag/v0.13.0" rel="noopener nofollow ugc">v0.13.x</a>)! This significant milestone expands Dedot’s contract compatibility to support both WASM and RISC-V based execution environments, providing developers with flexible deployment options while maintaining the familiar developer-friendly approach that Dedot is known for.
With this integration, Dedot now offers comprehensive smart contract support across multiple execution environments within the Polkadot ecosystem, enabling developers to choose the most suitable runtime for their specific use cases while enjoying a consistent development experience.
We want to give a huge shoutout to the <a href="https://use.ink/inkubator/" rel="noopener nofollow ugc">Ink!ubator 2.0 program</a> for their amazing support and funding, and a special thanks to <a class="mention" href="/u/alexd10s">@alexd10s</a> from R0GUE for being such an incredible help throughout this integration!
<h3><a name="p-30323-important-notes-1" class="anchor" href="#p-30323-important-notes-1"></a>Important Notes:</h3>
<ul>
<li>
Backward Compatible: This new integration is fully backward compatible with pallet-contracts and previous ink! versions (v4, v5)
</li>
<li>
Unified Interface: We’re using a unified interface for both pallet-revive and pallet-contracts under the <code>dedot/contracts</code> package. Dedot automatically detects the ink! version from the contract metadata to perform initial validation and interact with the corresponding pallet interfaces:
<ul>
<li>ink! v4 &amp; v5 → pallet-contracts (WASM-based execution)</li>
<li>ink! v6 → pallet-revive (RISC-V based execution)</li>
</ul>
</li>
<li>
Address Format Changes: There are slight breaking changes in interfaces/API to support both EVM addresses (20 bytes) and Substrate addresses (32 bytes), depending on the ink! contract version you’re interacting with:
<ul>
<li>ink! v4 &amp; v5 contracts use Substrate addresses (32 bytes)</li>
<li>ink! v6 contracts use EVM addresses (20 bytes)</li>
</ul>
</li>
</ul>
<h2><a name="p-30323-getting-started-now-2" class="anchor" href="#p-30323-getting-started-now-2"></a>Getting started now</h2>
Here’s what you can do to start interacting with ink! v6 now in Dedot:
<ol>
<li><a href="https://docs.dedot.dev/ink-smart-contracts/generate-types-and-apis" rel="noopener nofollow ugc">Generate types &amp; APIs for ink! v6 using dedot cli</a></li>
<li><a href="https://docs.dedot.dev/ink-smart-contracts/deploy" rel="noopener nofollow ugc">Deploy contracts &amp; calculate contract address</a></li>
<li><a href="https://docs.dedot.dev/ink-smart-contracts/queries" rel="noopener nofollow ugc">Send contract queries</a></li>
<li><a href="https://docs.dedot.dev/ink-smart-contracts/transactions" rel="noopener nofollow ugc">Sign and submitting contract transactions</a></li>
<li><a href="https://docs.dedot.dev/ink-smart-contracts/storage" rel="noopener nofollow ugc">Retrieve contract storage via Storage API</a></li>
<li><a href="https://docs.dedot.dev/ink-smart-contracts/events" rel="noopener nofollow ugc">Listen to &amp; work with fully-typed contract events</a></li>
<li><a href="https://docs.dedot.dev/ink-smart-contracts/handle-errors" rel="noopener nofollow ugc">Handling errors</a></li>
</ol>
Some examples to interact with ink! v6 contracts in Dedot repository:
<ul>
<li><a href="https://github.com/dedotdev/dedot/blob/987267eac0d87ed9c8e3888ca4f3fb3f7bce0714/examples/scripts/inkv6/interact.ts" rel="noopener nofollow ugc">Interact with flipper contract</a></li>
<li><a href="https://github.com/dedotdev/dedot/blob/987267eac0d87ed9c8e3888ca4f3fb3f7bce0714/examples/scripts/inkv6/psp22-storage.ts" rel="noopener nofollow ugc">Interact with PSP22 contract</a></li>
</ul>
<h2><a name="p-30323-conclusion-3" class="anchor" href="#p-30323-conclusion-3"></a>Conclusion</h2>
We’d love for you to give it a try and let us know what you think! Your thoughts and experiences mean the world to us and really help shape how we continue improving this integration.
<ul>
<li>Drop us a line about any issues on our <a href="https://github.com/dedotdev/dedot/issues" rel="noopener nofollow ugc">GitHub repository</a></li>
<li>Come chat with us in our <a href="https://t.me/JoinDedot" rel="noopener nofollow ugc">Telegram community</a> - we love hearing from you!</li>
<li>Contact me directly on Telegram at <a href="https://t.me/realsinzii" rel="noopener nofollow ugc">realsinzii</a> if you want a direct discussion!</li>
</ul>
<hr>
<a href="https://dedot.dev/" rel="noopener nofollow ugc">Dedot</a> - Delightful JavaScript/TypeScript client for Polkadot &amp; Polkadot SDK-based blockchains

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

Treasury Proposal: KusamaHub 2' Proposal for Continued Operations and Development

Dotcast: brand development and content production for the Spanish speaking community.

Treasury proposal: Sol2Ink Milestones 3 & 4 development (WASM smart contracts)

4 Month Funding for Cryptozilla YouTube channel 

New backend for polkassembly

Nova Wallet 4th Proposal: Multistaking dashboard, Staking Nomination Pools, WalletConnect v2, New Assets tab UI, Community Requested Features, Reimbursement for delivered features

KusaMint - Extension and Further Funding Q2-3 2023

Green Bay Dollar Advertising Campaign - the First Encointer Implementation in the USA

Treasury Proposal - Funding for development of Database Analytics and RPC Endpoint monitoring

Forging New Frontiers: Sonar Music Festival's 30th Anniversary Unveils First-ever Sonar+D DAO Collaboration with Polkadot

- **Kusama Dark Hole**: A special account that burns tokens to help reduce inflation.  
- **Problem**: Kusama has high inflation and lost ways to burn tokens.  
- **Current Issues**:  
  - No more token burns from the Society pallet.  
  - Coretime market isn’t working well (cores are full, renewals too cheap).  
  - Hard for new developers to start parachains.  
- **Solution**: Add a "Dark Hole" pallet to AssetHub that burns tokens forever.  
- **Future Plans**: Could let some burned tokens fund other projects later.  
- **Goal**: Help control inflation and support Kusama’s growth.

Deciding

WFC: DarkHole Pallet - General purpose burn mechanism

- A proposal suggests adding new tools for DAOs (Decentralized Autonomous Organizations) in AssetHub.  
- It focuses on technical upgrades without telling W3F or DVs how to operate.  
- The goal is to help DAOs work better on-chain.  
- New tools would include:  
  - A voting system for DAO decisions.  
  - A way to manage DAO memberships.  
  - A system to organize and control DAOs.  
  - Custom settings for DAO governance.  
- These tools were tested on Kreivo and worked well.  
- Adding them to AssetHub will give DAOs more power, especially with future smart contracts.

Counter WFC: More tools for DAOs in AssetHub

- Some people want to lower Kusama's inflation like Polkadot did.  
- Lowering inflation on Polkadot didn’t make the token price go up as expected.  
- It also made staking rewards smaller, which could hurt Kusama users.  
- Instead, the idea is to lock some staking rewards so they can’t be sold right away.  
- Locked tokens can still be used for staking or voting.  
- The community can vote on how much to lock.  
- Validators would still get full rewards.  
- This idea fits Kusama’s experimental nature.

Develop a mechanism to lock a percentage of staking rewards as set out in the details of this referendum

- **Kusama & Polkadot x Arcadia**: A special project called "THE SPIDER."  
- **Interactive Proposal**: A fun online link to explore the idea.  
- **Written Proposal**: A detailed document explaining the project.  
- **Arcadia’s Web**: Uses art to connect people, not just data.  
- **Spider Installation**: Tells an old story about a web linking cultures.  
- **Live Experience**: A dancefloor where people help weave the web together.  
- **Web3 Culture**: Shows how technology can bring people closer.  
- **Not Just Ads**: A real, exciting event celebrating Web3 in the streets.

Kusama (ft. Polkadot) x Arcadia: THE SPIDER

- Acuity Index helps make dapps fully decentralized  
- It was funded by Web3 Foundation grants  
- Needs updates for latest Polkadot runtimes  
- Adds important new features  
- Requesting 256 KSM (~$4000)  
- Part of the "Small Spender" track  
- Originally named "Hybrid"  
- More details in the full proposal link

Full proposal: [https://index.acuity.network/proposals/1/](https://index.acuity.network/proposals/1/)

`Track: Small Spender`

`Value: 256 KSM (~4000 USD)`

Acuity Index was originally called Hybrid and was funded by two Web3 Foundations grants.

It solves a critical issue in the Polkadot ecosystem - it enables dapps with rich functionality to be fully decentralized.

This proposal is to update Acuity Index to fully index the latest Polkadot runtimes and to implement important features.

Full proposal: [https://index.acuity.network/proposals/1/](https://index.acuity.network/proposals/1/)

Acuity Index: new features and update to latest Polkadot runtimes

- Polkadot is focusing on resilience and strong on-chain governance.  
- Current Decentralized Voices (DV) groups rely too much on centralized tools.  
- Polkadot can use DV to create strong, on-chain political parties.  
- Kusama Asset Hub needs upgrades to support better DAO tools.  
- Kreivo’s technology can help make these upgrades.  
- New DVs should have clear goals and use only on-chain tools.  
- A step-by-step plan will help transition to resilient DAOs.

Preparing

WFC: Use Decentralized Voices Cohort #5 to drive the evolution of resilient on-chain political parties..

- Proposal to raise validator commission from 10% to 15% for better earnings  
- Current earnings: ~$158/month per validator (10% commission)  
- Proposed earnings: ~$238/month per validator (15% commission)  
- Goal: Help validators cover costs and stay secure  
- Ideal earnings should be $300-$500/month for sustainability  
- Matches Decentralized Nodes programme’s max commission  
- Previous increases: 3% → 10%  
- More proposals may follow to adjust rewards further

Executed

Increasing the Validator minimum commission from 10% to 15%

Rejected

Vote Nay - Validator Min Commission Increase - Wrong Track

- Asking for 333 KSM to fund community activities for over a year  
- Funds used for staking rewards and refunding deposits on Kusama  
- Account was funded by Treasury 6 months ago, but needs more now  
- No outbound transfers—most fees go back to the Treasury  
- Supports validators and referenda on Kusama  
- Managed responsibly with transparent spending  
- Request is near the upper limit of funding  
- Account balance shown in a graph for transparency

Tip for an account used for Referendum Deposit Clean-up and Validator Payout Bot

&nbsp;
&nbsp;
There was a security risk and the proposal was processed externally.
No further occurrences with this.
Thank you..

Kusama

referenda9

treasury23

discussions1370