candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

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

system

The Kus Public Review & AMA: 2022 - Present

Struggling with User Adoption in Emerging Technologies

ETHRome 2025 x Polkadot by DevCult

DevCult

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

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

Xiscocv

"Revive" Smart Contracts: Status Update

Ink! vs Bare Rust Smart Contracts

Torsten

Intel SGX seems dead for blockchain applications

Lohann Paterno Coutinho Ferreira

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

[Kusama RFP idea] Priest Chat, A holy anti chat control idea

Rust Syndicate

Python Libraries Maintenance Continued Funding

muddles

RFC-159: Spend Canceller Track

Tommi Enenkel / Alice und Bob | Mangata

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

Ecosystem

Paseo coretime on-demand problem

Bastian Köcher

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

Ludo

Smart Contracts on Polkadot Hub: Progress Update

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

<a class="mention" href="/u/hgminerva">@hgminerva</a> can you be more specific on what is not working anymore? what exactly is happening?

Its rank 3 now ? 
I remember some time ago a talk about getting rank 2 for main implementers and rank 1 for the other devs. I havent kept up with JAM since so that might have changes since ?

Tomek Drwięga

Hopefully Gustav or previous/current Kopimism members/organizers/mods could jump into this forum thread. What it seems like is that both users needs to be members of the church(solvable with a good terms of service? Abstracted away in the background for the user) and one needs the priest status.

Eric-W3F

The Kus provides consistent high quality content. I’m not seeing anyone else doing this, besides one or two select people in the ecosystem. Losing the Kus would be loss for Polkadot’s already thin marketing and content creation landscape. The people saying the Kus is has received too much funding should look at what a content producer of this calibre is worth on market related terms, outside of Polkadot, not what they think should be compensated given the state of Polkadot. If we don’t keep high quality contributors in Polkadot, the ecosystem will suffer even more.

Clara van Staden

See this post for an update about our launch timelines: <a href="https://forum.polkadot.network/t/revive-smart-contracts-status-update/16366" class="inline-onebox">"Revive" Smart Contracts: Status Update</a>

I’ve used the Python libs earlier for data crunching and analysis, they were quite helpful.
I would love to see them continuously maintained, as I observe the last commits were done while ago!

<aside class="quote no-group" data-username="GabrielJ" data-post="3" data-topic="16339">
<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>
In case this separate track does not have treasury.spend permissions, the above delay solution would not longer work. As I mentioned on the Github post referenced above however, perhaps the introduction of a separate delay_spend call might be the best solution for maintaining the ability to delay spends.
Perhaps a separate track for void_spend and delay_spend (to be created) calls? A separate track for payout scheduling matters seems more sensible to me than the proposed solution by <a class="mention" href="/u/radha">@radha</a> since it keeps OpenGov more organized.
</blockquote>
</aside>
These are pretty good ideas. Maybe a <code>change_spend()</code> that can delay and potentially lower the amount of the spend.
We could either update the existing proposal or submit an additional one. At the moment I would tend to treat this as a separate idea.
It would be helpful to understand from a core developer how feasible changing a spend is after it has been approved.

Diego

It also doesn’t necessarily make sense to me that coretime is priced in DOT and not a DOT-backed stablecoin. If the price of DOT increases… the price of coretime is going to increase significantly. It’s not very predictable. If DOT did 30x then the minimum price of a core would be around $500+…

bill_w3f

Where did the 10 DOT minimum coretime price come from?

I’ve recently put up a forum post for discussion of the Squidsway proposal. 
If you’ve not read that, <a href="https://forum.polkadot.network/t/updated-squidsway-proposal-nov-dec-2025/16047">read it first</a>.
This forum post is aimed at data geeks in the ecosystem. 
I welcome ideas from the whole community but I’m particularly looking at you: 
Parity Data Team 
individuals and teams working on OpenGov transparency 
product team members who design and assess KPIs 
builders of the ecosystem’s various dashboards
I would like your feedback and suggestions on 
. the kind of data / insights that the Squidsway project should be generating 
. the areas in which Squidsway should be investigating
As a reminder on the kinds of data which are technically possible to ingest: 
A major USP of the Squidsway tool is the ability to ingest offchain data, particularly unstructured or loosely structured offchain data, such as texts from canonical sources (eg Polkadot Forums, Polkassembly). 
The tool will be a reindexer, using sets and tags to curate data and queries to compile data before reingestion so that commonly used properties such as ‘whale account’, ‘first-time voter’, ‘sophisticated user’ or ‘contentious referendum’ can be efficiently recombined into more detailed queries.
The kinds of data which it makes sense to reingest are those that let us aggregate individuals’ considered behaviour (such as using an extrinsic, writing a proposal) into trends. 
It makes less sense to follow long ‘threads’ on individual accounts or referenda, for example a ‘follow the money’ investigation - while this would be possible with Squidsway, the efficient ETL flow for indexing would provide no advantage on single 'threads.
Some things are encouraged uses of the Squidsway tool, for which the tool would be appropriate, but would be out of scope for the treasury-funded proposal (ie the tool and project). An example would be generating an assessment mechanism for detailed KPIs of a rollup product - this would be something appropriate for the product team themselves to use the tool to develop.
The insights the project will produce should be action-focused, allowing us to guide user behaviour through the choices we make as OpenGov, and to do this effectively and objectively.
Some examples of the level of insight which the project (using the tool) could produce:
Assessment of Polkadot Referendum 1701:
This is an example of a hard (ie on-chain) change we make in order to encourage some user behaviour. 
The actual user behaviour we seek is reasonably well-defined. 
Some of the aims are subjective and can only be proxied subjectively (eg ‘elevate the quality of governance activity’). 
Others can be proxied well (eg, ‘increase alignment within the network participants’ ≈ ‘more of the referenda submitted pass’). 
Others open new questions in definition which allow us to better iterate our aims (eg ‘Ensuring only “heavily” aligned referendums get approved’ - does this mean that more submitted referenda: ‘get high support from token-based voting’; or ‘get the support of a high number voting participants’; or ‘have more positive engagement’ ? - all of these are possible to measure and with the 3 measurements we can compare success on each of these 3 aims against each other). 
While many of these results are possible without Squidsway, the Squidsway tool should significantly reduce the time it takes to find them and encourage data-driven (rather than vibes-driven) assessment of outcomes. 
We can additionally scan for unintended consequences - for example, we may find that increasing the decision deposit significantly reduces the number of small treasury proposals, or those that concern development but not those that concern marketing, or those from first-time proponents.
Technical quality of proposal norms:
A contributing factor to voter fatigue is the proportion of proposals which don’t abide by recommended norms, such as previous forum engagement or ‘no retrospective funding’. These can necessitate an expenditure of time by OpenGov participants in repeatedly pointing out the norms. They are even more of a burden for proponents, who often don’t know which ‘norms’ really are norms, which are widely ignored, which are given importance by some voters but not others (there is often a lack of consensus even amongst big voters on norms, like ‘don’t request in DOT’).
We can define these norms and set an LLM on assessing compliance of each completed proposal with them, and the results (compared with Aye/ Nay) should allow a single set of comparators for proponents to quickly separate signal from noise, and thus improve the quality of their proposals.
Monetary policy:
Monetary policy is an area in Polkadot governance which has been given only cursory attention in the last few years, all of which has been based on assertion. With the new focus on the utility of the DOT token, we can expect more tweaks to monetary policy to become more regular.
Without a framework to measure the resulting effects, we risk repeating the same fundamental mistake we made in 2023 - assessing ROI based on hot air and argument, and thus taking many times longer to agree on the truth (in the case of 2023, significantly delaying us from stopping the bleed).
In national economies, second order measurements such as the velocity of money (the degree to which money in the economy is respent on productive activity - thus increasing GDP) are important but only measurable by proxy. On a public blockchain, we can measure, rather than infer, such measurements. 
As an example: We can measure the types of routes taken by DOT disbursed via different routes (eg Events Bounty, incentives, public goods product teams). Perhaps we find that money paid out via hackathons takes a variety of routes around the DOT ecosystem, but money paid out as marketing goes straight to exchanges. Right now, without data, we can speculate about whether that is what happens. But we don’t know. And if we don’t know, the best can we do is slowly argue our way to consensus or stalemate.
These are just a few ideas - the possibilities are extremely wide (paradoxically, this makes it difficult to drill down on specific uses) 
All suggestions welcome - whether it is a particular dataset you wish existed, an issue you feel the community should be investigating with data, or even a new direction for the tool/ project which you haven’t yet seen mentioned.

Squidsway project - seeking input on directions for the data

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)

- 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

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

Executed

[Whitelisted Caller] Referendum #622

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

TimedOut

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

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

treasury94

discussions1379