candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

The Kus Public Review &amp; AMA: 2022 - 2025

Gonzalo Etse

The Kus Public Review & AMA: 2022 - 2025

ETHRome 2025 x Polkadot by DevCult

DevCult

Data storage/availability

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

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

Multix Sunset Announcement (Jan 1, 2026)

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

Lu Dete

"Revive" Smart Contracts: Status Update

Runtime release notification for v2.0.4 [20.12.2025]

Anaelle LTD

Whether you’re new to Polkadot’s Governance or an OpenGov OG, this is the place for you to get involved and join the discussion.

Governance

Polkadot 2026 Turkey Business Development and Ecosystem Growth Plan – Istanbul-Based

RFC-0161: Discussion Phase for OpenGov Referenda

Hi looking for help on token economics understanding

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

Ecosystem

Ink!: Status, Context, and Why It Matters for Polkadot

ink!alliance

Overpass: DOT Gateway to Ethereum

Sergej Sakac

Decentralised Identifiers (DIDs)

Kacper Szarkiewicz

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

<aside class="quote no-group" data-username="radha" data-post="6" data-topic="16454">
<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>
e closed on January 1st and trail of events showing how dysfunctional the current setup is for ecosystem projects and teams. I guess it also somehow (unintentionally) implied how W3F personnel are partying and vacationing without putting efforts to mitigate the issue.
</blockquote>
</aside>
Hi, It seems that you took my comment as if it was coming from Multix team. Just for clarity, I have no affiliation to Multix at all. I’m only a neutral polkadot user for several years, a bit confused with the current state.
Edit: edited out extra unnecessary comment.

muddles

Sad to see this post became a DOT price discussion, as if one of the few relevant (personally) and minor uses of treasury money would move the price move in any way or form. I thought price discussion wasn’t relevant in this forum.
Proof of Personhood can’t come soon enough to mitigate anons derailing discussions.
Personally, the KUS has been one of the only consistently useful info sources for Polkadot users in recent years, more than many more official channels. Really sad to see it go; I’m concerned it’ll speed up the attention drop around Polkadot in the Web3 space. At least for me, it might be so. Hopeful the actual products mentioned win us over!

We do not wish to do things solely to gain favor with certain circles.
We want to continue development for Polkadot with a more productive infrastructure.
By the way, rest assured, we have a very strong network within the Turkish ecosystem.
Once we make the first pilot offer, they will see how strong the positive feedback will be if it is accepted.
By the way, yes, Hungary and Europe are not as influential as Turkey.

hahaha, I am not even going to pretend I understood your reply to your second response on question 1. <img src="https://emoji.discourse-cdn.com/twitter/grinning_face.png?v=15" title=":grinning_face:" class="emoji" alt=":grinning_face:" loading="lazy" width="20" height="20"> However, I will take your word for it, as it is over my head, right now. <img src="https://emoji.discourse-cdn.com/twitter/rofl.png?v=15" title=":rofl:" class="emoji" alt=":rofl:" loading="lazy" width="20" height="20"> Appreciate 1st reply, totally understood that response!

Tommi Enenkel / Alice und Bob | Mangata

Is there any documentation or tutorial on using Revive to upgrade an existing Substrate‑based blockchain?

This post provides an overview of the current status of ink!, its role in the Polkadot ecosystem, and the associated risks. It is a purely informational update for ecosystem stakeholders, summarising the present state of ink! and the decentralised yet cohesive and strategically aligned work carried out by the ink! community and the Alliance.
<h2><a name="p-36501-h-1-current-status-1" class="anchor" href="#p-36501-h-1-current-status-1" aria-label="Heading link"></a>1/ Current Status</h2>
Over the past year, the ink! Alliance has been highly active across delivery and ecosystem technical advancement, with many successes, to name a few:
<ul>
<li>
Migrating ink! from Wasm to PolkaVM (pallet-revive)
</li>
<li>
Upgrading core tooling, documentation, and a full <a href="https://use.ink/" rel="noopener nofollow ugc">use.ink</a> and brand update
</li>
<li>
Making significant contributions to <a href="https://github.com/use-ink/ink-alliance/issues/24" rel="noopener nofollow ugc">PolkaVM</a>, <a href="https://github.com/use-ink/ink-alliance/issues/23" rel="noopener nofollow ugc">pallet-revive</a>, and <a href="https://github.com/use-ink/ink-alliance/issues/74" rel="noopener nofollow ugc">alloy-rs</a>
</li>
<li>
Providing ongoing direct developer support
</li>
<li>
Delivering ink! ↔ Solidity ABI compatibility
</li>
<li>
Supporting the Web3 Summit and the Buenos Aires hackathons
</li>
<li>
Mentoring at the PBA in Bali
</li>
</ul>
Despite this progress, ink! v6 is not yet in production. It is currently in an unoptimised beta state and depends on:
<ul>
<li>
A security audit and remediation (auditor identified, but work currently paused due to uncertainty of funding for ink!)
</li>
<li>
The production launch of PolkaVM on the Hub
</li>
</ul>
The dependency for PolkaVM is bidirectional:
<ul>
<li>
PolkaVM requires a production-ready smart contract language
</li>
<li>
ink! v6 requires PolkaVM to run
</li>
<li>
Adoption can only begin after production launch
</li>
</ul>
Status Summary: Before ink! v6 can be safely used with pallet-revive / PolkaVM, audit remediation is still required.
Source 1: <a href="https://polkadot.polkassembly.io/referenda/1796#comment-jEO5zfS4aqOUMlSsPZCD" rel="noopener nofollow ugc">Polkassembly Referendum 1796: Alliance Clarification 1</a>
<h2><a name="p-36501-h-2-historical-context-why-v5-v6-2" class="anchor" href="#p-36501-h-2-historical-context-why-v5-v6-2" aria-label="Heading link"></a>2/ Historical Context: Why v5 ≠ v6</h2>
Addressing conjecture, ink! v5 did not fail due to the language.
It operated in an ecosystem context where success was structurally constrained:
<ul>
<li>
Fragmented liquidity
</li>
<li>
No native-ink! platform to deploy on
</li>
<li>
No unified Hub
</li>
<li>
Low on-chain economic activity
</li>
<li>
Weak brand capital
</li>
</ul>
ink! v6 operates in a fundamentally different environment, both within Polkadot &amp; based on the macro Rust adoption trends:
a. Polkadot Unification / Cryptoeconomic Alignment
<ul>
<li>
A unified, production-grade Hub
</li>
<li>
Shared liquidity
</li>
<li>
PolkaVM
</li>
<li>
DOT-native programmability
</li>
</ul>
b. Macro Web3 Rust adoption trend
<ul>
<li>Rust is now onboarding Rust developers 30% faster than Solidity for the top 20 blockchains</li>
</ul>
<div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/0/042f682957ee1865c75b43c086352a1015e79f9d.jpeg" data-download-href="/uploads/short-url/B1tFX1PmH9cvhrqN9v9jjW3QL3.jpeg?dl=1" title="image" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/0/042f682957ee1865c75b43c086352a1015e79f9d_2_690x446.jpeg" alt="image" data-base62-sha1="B1tFX1PmH9cvhrqN9v9jjW3QL3" width="690" height="446" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/0/042f682957ee1865c75b43c086352a1015e79f9d_2_690x446.jpeg, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/0/042f682957ee1865c75b43c086352a1015e79f9d.jpeg 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/0/042f682957ee1865c75b43c086352a1015e79f9d.jpeg 2x" data-dominant-color="604B94"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg>image888×574 114 KB<svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div>
This is not an argument against Solidity. Solidity remains critical infrastructure. It is just the necessary evidence that Rust is now the fastest-growing onboarding funnel in Web3.
Therefore, we can’t judge v6’s success based on v5 outcomes.
Source 2: <a href="https://polkadot.polkassembly.io/referenda/1796#comment-05tLwtVBD2Nu063V8H7Y" rel="noopener nofollow ugc">Polkassembly Referendum 1796: Alliance Clarification 2</a> 
Source 3: <a href="https://forum.polkadot.network/t/rust-solidity-data-doesn-t-lie/15683">Polkadot Forum: Rust &gt; Solidity: Data Doesn’t Lie</a>
<h2><a name="p-36501-h-3-ink-as-the-direct-rust-dot-pathway-3" class="anchor" href="#p-36501-h-3-ink-as-the-direct-rust-dot-pathway-3" aria-label="Heading link"></a>3/ ink! As The Direct Rust → DOT Pathway</h2>
ink! is:
<ul>
<li>
Rust
</li>
<li>
A smart contract eDSL/framework (analogous to FRAME for runtimes)
</li>
<li>
The only PolkaVM-compatible smart contract language at Hub launch
</li>
</ul>
Smart contracts are the market mechanism that allows utility, experimentation, and value creation to emerge permissionlessly on-chain.
Prioritising smart contract enablement therefore prioritises:
<ul>
<li>
Open participation
</li>
<li>
Low barriers to entry
</li>
<li>
Bottom-up innovation
</li>
</ul>
Economic theory and historical evidence strongly suggest that competitive, open markets tend to be more productive and innovative than centrally planned systems.
Supporting evidence for this can be seen in the recent Polkadot Builder Party winner selection, where projects built with ink! were strongly represented and outperformed Solidity-based submissions.
<div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/d/de1f4577330b1a12252db9d8ccd5c8da88a2c6ac.jpeg" data-download-href="/uploads/short-url/vGYZOsBhmzeqFbPtn5EhMEAAqaU.jpeg?dl=1" title="image" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/d/de1f4577330b1a12252db9d8ccd5c8da88a2c6ac_2_690x446.jpeg" alt="image" data-base62-sha1="vGYZOsBhmzeqFbPtn5EhMEAAqaU" width="690" height="446" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/d/de1f4577330b1a12252db9d8ccd5c8da88a2c6ac_2_690x446.jpeg, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/d/de1f4577330b1a12252db9d8ccd5c8da88a2c6ac.jpeg 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/d/de1f4577330b1a12252db9d8ccd5c8da88a2c6ac.jpeg 2x" data-dominant-color="5043A9"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg>image888×574 94.1 KB<svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div>
ink! delivers better DevX vs Bare Rust without sacrificing performance:
Benchmarks comparing ink! vs Bare Rust show that ink! significantly reduces boilerplate, improves safety, and maintains comparable (or better) performance.
<ul>
<li>
~3× less code, ~45% boilerplate eliminated
</li>
<li>
Comparable gas usage, smaller binaries, fewer instructions
</li>
<li>
Strong compile-time safety and built-in testing
</li>
</ul>
This makes ink! more productive, maintainable, and accessible for most developers, while still allowing low-level Rust where maximum control is required.
Source 4: <a href="https://forum.polkadot.network/t/ink-vs-bare-rust-smart-contracts/16156">ink! vs Bare Rust Smart Contracts</a>
<h2><a name="p-36501-h-4-concrete-efficiency-safety-and-capability-to-drive-privacy-on-polkadot-4" class="anchor" href="#p-36501-h-4-concrete-efficiency-safety-and-capability-to-drive-privacy-on-polkadot-4" aria-label="Heading link"></a>4/ Concrete Efficiency, Safety, and Capability to Drive Privacy on Polkadot</h2>
A recent example shows ZK Noir circuits generated natively in ink! v6 (PolkaVM-backed).
From the implementers:
<blockquote>
“The result is a verifier contract that achieves ~25% gas savings, 45% smaller binary size, and full Rust type safety compared to Solidity alternatives; all while being completely self-contained and requiring zero external dependencies once deployed.”
</blockquote>
<blockquote>
Type Safety is a Superpower: Rust’s compile-time guarantees caught numerous subtle bugs in field arithmetic and proof handling that would have been runtime failures in Solidity.
</blockquote>
Even in an unoptimized beta setting, ink! demonstrated better performance and stronger safety guarantees, while remaining interoperable with Solidity via ABI compatibility.
Source 5: <a href="https://devpost.com/software/ivf" rel="noopener nofollow ugc">Polkadot Builder Party: iVF Project</a>
<h2><a name="p-36501-h-5-developer-experience-as-onboarding-infrastructure-5" class="anchor" href="#p-36501-h-5-developer-experience-as-onboarding-infrastructure-5" aria-label="Heading link"></a>5/ Developer Experience as Onboarding Infrastructure</h2>
Beyond tooling, the ink!ubator has strategically prioritised Monsters ink!, which:
<ul>
<li>
Gamifies onboarding for first-time developers
</li>
<li>
Helps newcomers take their first steps with ink! &amp; Polakdot
</li>
<li>
Mints a unique NFT on course completion, introducing asset ownership in a low-friction way
</li>
</ul>
Monsters ink! uses state of the art image and 3d generation models to create personalized, evolving monsters that grow as the users progress through the curriculum, serving as both their companion and their proof-of-knowledge onchain card.
This positions ink! not only as smart contract infrastructure, but as an emerging decentralized DevRel surface for the ecosystem.
<div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/8/83899dc23aa409f61418f9d17e407885e6936df3.jpeg" data-download-href="/uploads/short-url/iLDobrw5MEobwylYgIITTWTSD6z.jpeg?dl=1" title="image" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/8/83899dc23aa409f61418f9d17e407885e6936df3_2_690x362.jpeg" alt="image" data-base62-sha1="iLDobrw5MEobwylYgIITTWTSD6z" width="690" height="362" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/8/83899dc23aa409f61418f9d17e407885e6936df3_2_690x362.jpeg, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/8/83899dc23aa409f61418f9d17e407885e6936df3_2_1035x543.jpeg 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/8/83899dc23aa409f61418f9d17e407885e6936df3_2_1380x724.jpeg 2x" data-dominant-color="211949"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg>image1920×1008 87.6 KB<svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div>
Source 6: <a href="https://www.loom.com/share/e99c88107dd94df9ab271f57060d555d" rel="noopener nofollow ugc">Monsters ink! Milestone 2 Loom</a> 
Source 7: <a href="https://github.com/use-inkubator/Grant-Milestone-Delivery/pull/28#issuecomment-3681675921" rel="noopener nofollow ugc">Monsters ink! Milestone 2 Delivery</a>
<h2><a name="p-36501-h-6-the-risk-to-innovation-6" class="anchor" href="#p-36501-h-6-the-risk-to-innovation-6" aria-label="Heading link"></a>6/ The Risk To Innovation</h2>
ink! is currently unfunded.
<ul>
<li>
Core contributors have worked unpaid for ~4 months
</li>
<li>
Development and support has now been paused as a result
</li>
<li>
Required audits and remediation cannot be completed
</li>
</ul>
This is not about promoting ink! in isolation.
It is about whether Polkadot launches the Hub with:
<ul>
<li>
A Rust-native smart contract path
</li>
<li>
A viable Rust developer funnel
</li>
<li>
Production-ready, audited tooling aligned with Polkadot’s innovative and decentralised identity
</li>
</ul>
<h2><a name="p-36501-h-7-closing-thoughts-7" class="anchor" href="#p-36501-h-7-closing-thoughts-7" aria-label="Heading link"></a>7/ Closing Thoughts</h2>
The ink! Alliance has initiated discussions with Web3 Foundation and Parity. At present however, development, support and operations are paused due to lack of funding and there is no confirmed timeline for continuation. This is an important consideration for teams building with ink! v6 on testnet, and we feel it is essential to be transparent about the current situation.
FAQ: Clarifying Next Steps For Builders
a. What does “paused” mean in practice?
“Paused” means that there is currently no funded, active development capacity for ink!. This includes:
<ul>
<li>
No guaranteed engineering work on ink! v6
</li>
<li>
No formal maintenance, roadmap execution, or feature delivery
</li>
<li>
No assured responsiveness for GitHub issues, pull requests, or community support channels
</li>
</ul>
The code remains open source and available, but there is no resourced team actively stewarding day-to-day development at this time.
b. What should I do if I’ve already built with ink! expecting to deploy on Polkadot Hub?
Objectively: ink! may be funded, we are just uncertain as of this moment and need to discuss more with Parity and the W3F.
If you have built with ink! in anticipation of deploying to the Polkadot Hub:
<ul>
<li>
Your work is not invalidated
</li>
<li>
ink! v6 remains technically aligned with PolkaVM, however, your contracts are not compatible with the current version of Revive on Paseo AssetHub or intended for Mainnet release - This cannot be rectified without further funding for development
</li>
<li>
However, production readiness is not guaranteed without resumed operations, development, and audit remediation
</li>
</ul>
Teams should treat ink! v6 as experimental until such a time that development resumes and production criteria are met. Planning assumptions should be updated accordingly.
c. When will we know more about the funding of ink!?
At a minimum, updates on funding will follow once Parity and Web3 Foundation return from the holiday period. The ink! Alliance will resume discussions with them at that point and will keep the community informed as conversations progress. At present, no specific timeline or outcome can be guaranteed.
We firmly believe in ink! and in the work delivered to date, both by our community members and the Alliance participants stewarding the language.
That work reflects careful long-term prioritisation, adaptability, strategic relevance, and rational coherence. The ink! Alliance remains committed to progressing ink! v6 toward production readiness and will continue to explore viable paths to resume development and bring this work to completion, however, as it stands, that future is less than certain for the Hub.

Yeah, one of the biggest benefits would be access to Ethereum’s DeFi.
I’ve just reached out. Depending on the status of the DeFi bounty, this could potentially be supported by it.

I was involved in the project at Deloitte Switzerland from the very beginning, and we collaborated with Polimec and Kilt. I left the project a long time ago, and shortly afterwards, as you can see, it became unavailable. 
I’m not sure if it can still be used, the wallet is unavailable: <a href="https://chromewebstore.google.com/detail/bflldjbbpcjgooclhpmhdhioebmnnkcm/error" rel="noopener nofollow ugc">https://chromewebstore.google.com/detail/bflldjbbpcjgooclhpmhdhioebmnnkcm/error</a> 
and service too: <a href="https://kyc-credentials.com/home" rel="noopener nofollow ugc">https://kyc-credentials.com/home</a>

Leonardo | WinterStamp

I also find it curious that Coinstudio is a <a href="https://polkadot.subsquare.io/treasury/bounties/31" rel="noopener nofollow ugc">curator on this other bounty</a> where it is being paid $350 per month. Could someone please clarify why this individual is being paid $3,400 per month from the IBP Bounty?

Lack of Transparency in IBP Bounty Payments - Coinstudio curator

bill_w3f

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)

Deciding

Whitelist for runtime upgrade to 2.0.4

- A big update called Revive is coming to a blockchain network.
- It lets people use smart contracts, which are like tiny computer programs.
- Developers can use the same tools they already know from Ethereum.
- The network is getting faster by changing how it handles more activity.
- Block times (how fast new data is added) will soon be much quicker.
- This update is planned to start on December 29th, 2025.
- It helps the network do more things at once.

Upgrade Kusama System to the v2.0.4 release

- Kusama's token supply and inflation are too high, hurting its price and popularity.
- A past update that lowered rewards briefly helped the price go up.
- The proposal suggests making Kusama more like Bitcoin to fix this.
- It wants to cut new token creation in half every four years starting in 2026.
- It plans to limit the total number of Kusama tokens to 21 million.
- It also aims to remove the minimum fee for validators.
- These new rules would be permanently written into the system's code.

Preparing

[WFC] Halving, maximum supply and zero minimum commission rate 

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

TimedOut

Wish for change: Four To The Floor x Kusama

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.

Treasury Guardian On-Chain Demo

Kusama

referenda3

fellowship1

treasury24

discussions1379