feat(gov): open gov sudo(root) in picasso

[dzmitry-lahoda]

Required for merge:

• pr-workflow-check / draft-release-check is ✅ success
• Other rules GitHub shows you, or can be read in configuration

Makes review faster:

• PR title is my best effort to provide summary of changes and has clear text to be part of release notes
• I marked PR by misc label if it should not be in release notes
• Linked Zenhub/Github/Slack/etc reference if one exists https://github.com/ComposableFi/Private-Issues-/issues/94
• I was clear on what type of deployment required to release my changes (node, runtime, contract, indexer, on chain operation, frontend, infrastructure) if any in PR title or description
• Added reviewer into Reviewers
• I tagged(@) or used other form of notification of one person who I think can handle best review of this PR
• I have proved that PR has no general regressions of relevant features and processes required to release into production
• Any dependency updates made, was done according guides from relevant dependency
• Clicking all checkboxes
• Adding detailed description of changes when it feels appropriate (for example when PR is big)

[github-actions]

Pull reviewers stats

Stats of the last 30 days for composable:

	User	Total reviews	Time to review	Total comments
	dzmitry-lahoda	26	8h 11m	12
	blasrodri	20	1h 58m	6
	mina86	17	12h 56m	64
	kkast	11	3h 17m	7
	RustNinja	11	1h 31m	2
	vmarkushin	5	7h	2
	JafarAz	3	9h 25m	0
	0xBrainjar2	2	3d 17h 35m	6

[github-actions]

# run Composable node
nix run "github:ComposableFi/composable/refs/pull/4086/merge" --allow-import-from-derivation --extra-experimental-features "flakes nix-command" --no-sandbox --accept-flake-config --option sandbox relaxed

# run local Picasso DevNet (for CosmWasm development)
nix run "github:ComposableFi/composable/refs/pull/4086/merge#devnet-picasso" --allow-import-from-derivation --extra-experimental-features "flakes nix-command" --no-sandbox --accept-flake-config --option sandbox relaxed 

# CosmWasm on Substrate CLI tool
nix run "github:ComposableFi/composable/refs/pull/4086/merge#ccw" --allow-import-from-derivation --extra-experimental-features "flakes nix-command" --no-sandbox --accept-flake-config --option sandbox relaxed 

# run cross chain devnet with Dotsama and Cosmos nodes 
nix run "github:ComposableFi/composable/refs/pull/4086/merge#devnet-xc-fresh" --allow-import-from-derivation --extra-experimental-features "flakes nix-command" --no-sandbox --accept-flake-config --option sandbox relaxed 
# or same with docker
nix build "github:ComposableFi/composable/refs/pull/4086/merge#devnet-xc-image" --allow-import-from-derivation --extra-experimental-features "flakes nix-command" --no-sandbox --accept-flake-config --option sandbox relaxed \
&& docker load --input result && docker run -it --entrypoint bash devnet-xc:latest -c /bin/devnet-xc-fresh 

About nix

[github-actions]

stale-pr

[github-actions]

stale-pr

[dzmitry-lahoda]

cc @kkast . closing this. please reopen or start when when you really will start.

[kkast]

OpenGov implementation:

New instance of balances pallet to control Gov Token

2 tracks: Sudo track and Whitelist track

On both composable and picasso:
½ Of native council can add/remove preimage to whitelist
1/3 of native council can cancel, 1/2 of native council can kill referendum
Native council is acting as fellowship on polkadot & kusama

On picasso: any pica holder can create referendum: to create they need submission deposit equal to 500k pica. then depending on referenda they need different deposit in pica for root they need 500k Pica, for whitelist they need 50k Pica.

On composable: only member of native council can create referenda because we dont have LAYR token released. Thus Submission and Deposits are 0 on composable.

Because pokadot.js page is using native token balances pallet, support curve on referenda page is going to be off. To get real support we need to check opengovbalances total issuance and support value for referenda in Referenda.ReferendumInfoFor
https://github.com/polkadot-js/apps/blob/master/packages/page-referenda/src/useReferenda.ts#L145

For convocation voting pallet: VoteLockingPeriod is 0 so that tokens wont be locked after referenda and could be claimed immediately after.

Next stages during the release:
Taking into account that for migration 9.43 balances existential deposit must be non zero, we should mint 1000000000001 gov token per every holder. In this case voting will be easy in the ui (will specify 1) and after migration wont need to change tokens amount. Also with this many tokens ed can always stay unused but the approval or support curves wont be affected.

Tracks’ Curves for Sudo and Whitelist are the same as for Kusama&Polkadot https://guide.kusama.network/docs/maintain-guides-polkadot-opengov/#whitelisted-caller

Resources:
Explains how curve works https://moonbeam.network/announcements/opengov-moonriver/

[dzmitry-lahoda]

we need tech collective to cancel once without slashing?

[kkast]

composable:
submit origin: anyone from any collective
cancel origin: 1/3 tech collective
Kill origin: 1/2 council
submission deposit and decision deposits are 0

picasso:
submit origin: anyone from any collective
cancel origin: 1/3 tech collective
Kill origin: 1/2 council
submission deposit is 1 pica(from 500k) and and decision deposits for root track is 50000 pica and 5000 for whitelist track.

[dzmitry-lahoda]

approved

[github-actions]

stale-pr

[kkast]

approved