**My Investigation into Kusama's OpenGov Parameters**

Okay, so the user is wondering if Kusama's OpenGov decision deposits, and potentially other track parameters, were bumped up, just like they were on Polkadot. I've already done some groundwork, it seems, fetching track data for both Polkadot and Kusama (step_1 and step_2) and maybe even poking around the Polkadot Forum (step_3).

The "DATA ADEQUACY ISSUE" is clear: We *know* the *current* track parameters for both networks, but we're missing the crucial historical link for Kusama – specifically, the referendum or change that triggered any increases. We *do* know Polkadot's referendum 1701 was the culprit there.

My goal now is to track down the Kusama equivalent. I need to find the referendum or discussion that modified those track parameters.

Here’s my plan:

1.  **Prioritize Search:** I'm going to hit Polkassembly and Subsquare hard, searching for Kusama referenda using keywords like "parameters," "deposit," "increase," and "track." I expect to find some hits here.
2.  **Backup Plan:** I can also search the Polkadot Forum, but I'll focus on terms related to "Kusama OpenGov parameters increase."
3.  **Check Tracks Only if Needed:** I'll revisit the track data on Kusama if the search results don't pan out, but the issue's focus is on the *history* of parameter changes, not the current values themselves.

Let's start by searching Polkassembly for Kusama referenda and focusing on keywords like "parameters" or "deposit." That's the most likely path to success. I can leverage Polkassembly's search endpoint or simply list and iterate through the referenda directly, if that's more effective. I'll also try Subsquare.




**My Approach to Finding the Kusama OpenGov Discussion**

Okay, here's how I'm going to approach this. The user wants to "discuss" the "Kusama OpenGov decision deposit increase," so I need to find the community's thoughts. My main target is to uncover relevant discussions, opinions, and related content.

First thought? **`forum-search`** is the obvious starting point. It's built for exactly this: finding discussions based on specific keywords. I'll use "Kusama OpenGov decision deposit increase" as the search query. It's the most direct and precise way to target the information.

Now, I'm thinking about the supporting options. **`forum-topic-detail`** is key *after* I find something. If the search turns up a specific topic ID, then this is how I will dig into the details of the discussion. And, just in case the search doesn't get exactly what's needed right away, **`forum-tag-topics`** might be useful as a backup or as a filter after the primary search. If there are relevant tags like "kusama" or "governance," I can use those to refine the search.

But, given the prompt, I need to generate the *query*, so the focus is search.

So the primary method is `forum-search`. I'm going with that. The user wants the Kusama discussion, and `forum-search` will get it.




**My Approach to Determining if Kusama's OpenGov Decision Deposit Was Increased**

Okay, so the user wants to know if Kusama's OpenGov parameters, specifically the decision deposit, were increased, mirroring a change on Polkadot. My thinking here is to directly compare the *current* state of these parameters between the two chains, and then investigate whether any *historical* changes occurred on Kusama.

Initially, I tried a few different sources – Subsquare, Polkadot Forum, and Polkassembly – but some failed or didn't provide the information I needed (Subsquare returned "N/A", Polkassembly timed out). Given this, I'm going to lean heavily on Subscan, which is generally reliable for on-chain data.

Here's my refined plan:

1.  **Retrieve Current Polkadot Track Parameters:** I'll use Subscan's `POST /api/scan/referenda/tracks` endpoint to fetch the current OpenGov track parameters for Polkadot. This gives me a baseline.
2.  **Retrieve Current Kusama Track Parameters:**  Similarly, I'll use Subscan's `POST /api/scan/referenda/tracks` to get the current OpenGov track parameters for Kusama. This is where I'll get the comparison.
3.  **Search for Kusama Referenda:** To determine if there was an increase (which implies a *historical* change), I need to look for a Kusama referendum that modified these parameters. Although Subsquare’s `GET /gov2/referendums` doesn't have a specific search parameter (that I could find), I'm going to look for any referendum titles. I was going to use Subsquare’s `GET /gov2/tracks`, but I’ll use Subscan for on-chain data.
4.  **Consider Wiki:** Just in case, I should quickly scan the Polkadot Wiki for any mention of this change.

Essentially, I'll compare the current values to try and see if they *are* higher, and if they are, hunt for the referendum that caused this increase. Subscan's track endpoint looks like the most direct way to get the *current* values. I will stick to Subscan for the on-chain data, because Subsquare returned "N/A."




**Analyzing OpenGov Decision Deposits: Current State and Historical Change**

Okay, so the user's question focuses on "OpenGov decision deposits" for Polkadot and Kusama, specifically whether there's been a "recent increase." This is a good, targeted question; it implies they're looking for a change in parameter values, not just the general mechanics.

My thought process starts by sifting through the schemas available. I see a few key ones that jump out: `wiki-governance-guides` is the foundational text for OpenGov; it’s the place to start for the overall conceptual understanding of tracks, origins, and voting.  Then, I have several schemas that get into the weeds of "Decision Deposits," like `wiki-learn-learn-polkadot-opengov-10` and `wiki-learn-learn-polkadot-opengov-14`, and also `wiki-learn-learn-polkadot-opengov-origins-11`, which gives specific values for Kusama.

The problem, as I see it, is none of these schemas *directly* track historical changes – no time-series data here.  They give the current state, definitions, and logic, but to know if there's been a recent increase, I'd need to compare this current data with historical values.

My strategy is to combine information from several schemas. I'll lean heavily on `wiki-governance-guides` because it sets the broad OpenGov context.  Then, to directly address the user's question about Decision Deposits, I'll include sections of `wiki-learn-learn-polkadot-opengov-14` (which explains that the level of privilege determines the decision deposit),  `wiki-learn-learn-polkadot-opengov-10` (which mentions the Polkadot submission deposit of 42 DOT), and `wiki-learn-learn-polkadot-opengov-origins-11` (which provides those Kusama-specific values, like the 3333.33 KSM for the Root origin). Ultimately, the user is looking for an answer to a value that changes, so these supporting pieces directly address that.




**Analyzing OpenGov Deposit Increases**

I'm currently focused on the implications of the Polkadot OpenGov deposit increase. I'm exploring whether the Kusama parachain saw similar adjustments to its own OpenGov decision deposits and how this might reflect on the underlying network design philosophy. Are the increases uniform, or differentiated to account for the unique network characteristics? I'll need to research the recent Kusama governance proposals.


**Comparing Kusama's OpenGov Response**

I've initiated a direct comparison between Polkadot and Kusama's OpenGov track parameters, as of March 25, 2026. My focus is on determining whether Kusama followed Polkadot's lead in adjusting decision deposits. I'm cross-referencing recent Kusama referenda (indices 618-642) to pinpoint any relevant increases. I'm also planning a Polkadot Forum search for discussions about Kusama OpenGov changes. Currently, I've gathered Polkadot track parameters as a point of reference. I will start the same for Kusama. My search for specific Kusama referenda related to the deposit increase failed (timed out), so I've refocused on the referenda indices.


**Examining Kusama Deposit Values**

I'm now focusing on specific deposit values for Kusama's OpenGov tracks. I've noted the current Root deposit at 3,333.33 KSM, and the Treasurer track at 33.33 KSM. I've also identified a 10x increase on the Treasurer track compared to its original value. This is useful for comparison, as is the 666.66 KSM Wish-for-Change deposit. I'm cross-referencing this with Polkadot's Wish-for-change adjustments and the historical context provided by the Wiki.


**Confirming Kusama Deposit Changes**

I've confirmed that Kusama did indeed adjust its OpenGov decision deposits. Specifically, the Root track now has a 3,333.33 KSM deposit, the Treasurer track requires 33.33 KSM, and Wish for Change is at 666.66 KSM. I'm now comparing these values directly with Polkadot's corresponding deposits, and I've reviewed the Planck conversions to ensure an accurate comparison between DOT and KSM values.




**Calculating Deposit Values**

Okay, I'm making headway on the Polkadot and Kusama OpenGov deposit values. I have the DOT and KSM prices and the Polkadot Planck deposit values, so I'm focusing on the USD conversion now. I'm moving onto Kusama deposits next, aiming for a direct comparison.


**Converting Planck to USD**

I've got the Kusama decision deposit values in Planck from Step 3, and I'm converting them to USD equivalents using the current KSM price of $4.42 and the fact that 1 KSM equals 10^12 Planck. I have a firm grasp on the values now and have incorporated the DOT equivalents for further cross-referencing.


**Calculating Kusama Deposits**

Now, I'm diving deeper into specific Kusama deposit values. I have the Planck figures from Step 3, and I've converted them to KSM amounts and, subsequently, USD equivalents. The conversion is based on the KSM price of $4.42. I've broken down each track's deposit requirement and have it all meticulously documented. I am now proceeding with Polkadot values.


**Refining Kusama   Polkadot Values**

I'm now cross-checking and refining calculations, focusing on clear formatting and accurate citations, and verifying Planck conversions, especially for the Polkadot Root and Kusama Root tracks. I've re-examined the USD calculations for both DOT and KSM values, and also performed some Treasurer track checks. The numbers seem correct.


**Verifying USD Deposit Values**

I'm now cross-checking all calculations against current DOT and KSM values. My goal is to ensure the USD deposit values for various Polkadot and Kusama tracks are accurate. I'm focusing on "Big Spender", "Whitelisted Caller", "Wish For Change" and "Referendum Killer" tracks. I am using the current DOT price of $1.38 and KSM price of $4.42, to get the USD equivalents.


