Funding an on-chain Decision Deposit Sponsor
Hello everyone, I wanted to open a discussion about helping disenfranchised individuals in the ecosystem by giving them recourse to submit large decision deposits without coming up with the funds themselves. This obviously has some flaws but I believe we can experiment with something on Kusama to see exactly how it pans out. Worst case, the ecosystem can create referendum killers/ cancellers in the event this decision deposit sponsor abuses its power. Here's the outline: ### Problem There are many well-intentioned individuals in the ecosystem that would like to try bold experiments on Kusama, but lack the necessary funds to place large decision deposits on the more powerful openGov tracks. This bottlenecks experimentation on the network, limiting it to the whims of whales who may not have the creativity or understanding to push innovation on Kusama. Pushing a powerful referendum into the decision period should be expensive to prevent malicious attacks, but it inherently prevents highly reputable and good users who don't have tens of thousands of dollars from pushing new and exciting ideas without winning the whim of a whale. ### Proposed Solution I propose funding a multisig-managed governance proxy whose signatories consist of a good number of ecosystem agents with super majority threshold. Here are the technical steps: 1. Create a pure proxy account 2. Add the multisig as a `governance` proxy to the proxied account 3. Remove the pure proxy creator as an `any` proxy, ensuring only the multisig can only make governance calls. 4. Fund the proxied account with 3,334 KSM from the treasury (or some other amount) This configuration ensures that only governance actions could be taken with these Treasury funds. The social layer of the signatories ensures that these governance actions should only ever be placing decision deposits. If the ecosystem approves and funds this initiative, we would test it by placing the decision deposit on a `root` track referendum that would schedule a `balances.forceTransfer` of the 3,334 KSM back to the Treasury in 6 months time (or sooner), effectively limiting the timeline of this experiment. ### Alternative Solution One more permanent and decentralized solution would be to develop on-chain capability that would allow users to crowdloan toward a referendum's decision deposit. This is ideal, however there is currently no Fellowship RFC seeking to implement this and is not part of the development direction of the Polkadot SDK afaik. I don't know how difficult it would be to develop something like this but chances are that it would take many months to launch in a Fellowship runtime upgrade. ### Pros & Cons |**Pros**|**Cons**| |:---|:---| |
- Gives decision deposit recourse to the disenfranchised
- Leverages ecosystem experts
- Community focused
- Experimental in nature, just as Kusama intended
|
- Negates ref killer deterrence
- Recentralization into a council
- Users can already, and should, appeal to large holders for DDs
- Might be a misappropriation of Treasury funds
| ### Feedback Needed - How much KSM should this decision deposit placer be funded with? I recommend 3,334 to allow only one `root` referendum at a time - Who should be the signatories? Here are some potential candidates off the top of my head (not exhaustive by any means): - Leemo - Jay - Will | Paradoxx - Tom | Stakeplus - 0xTaysama - Claudio | Kryptoschain - Yung Beef - Moonbearer - Other Chaos DAO members - Shawn Tabrizi - Gabriel - Tommi/ Alice Und Bob - Ryan/ Phunky - Tommi/ Hitchhooker - Raul Romanutti - How do we qualify a signatory? Account identity/age/nonce/openGov participation? - What should the multisig threshold be? 50%? 66%? 75%? 100%? - Is this a good experiment for Kusama? - What are the security concerns? Are there any since openGov can vote NAY on anything malicious? - When should the forceTransfer referendum be scheduled? In 3 months? 6 months? 9 months? Not at all? Any other feedback would be appreciated. Let's do some experimenting folks! Adam
Comments (2)
I think this is good startup point. We could experiment for 48 weeks with setup forceTransfer(perhaps also some block to deposit after certain amount of blocks not to stuck funds). Barely non of the current gov UI:s support anon proxies and I just wonder how feasible the votiing as multsiig with current tools would be. Could imagine it being quite stepheavy clicking in polkadot.js so we would need to write probably own voting script to enable +50% participation. I think the best way to do this would be deploying second society on kusama and doing the work of adding those missing functions for asset management. We could create some rules(ex. https://hackmd.io/@gavwood/ByEiaFgZ8) that would guarantee that syndicate would have some skin in the game when approving root calls as well as allow broader participation. but yeah pallet(https://github.com/paritytech/polkadot-sdk/blob/master/substrate/frame/society/src/lib.rs) still lacks asset management functions to function as multisig so we either need to code those or get started with multisig setup.
I want to revive this discussion by providing a tangible implementation for this idea.
I've rallied 4 individuals (including myself) to manage this DD sponsor. Those individuals are:
Eduardo Cardoso
EkQWFRUHmSt8qCwmgYv8TNSaFu1Xo5DaDAHBZbZZFxXMwDr
Professional with extensive experience (more than 20 years) and award-winning projects. BizDev with creative approach and specialist in content, product planning, brand, technology and media, among other subjects related to innovation in Communication, Branding, Design and Advertising. Resume link.
Rafael Yahlomi
EY8GTvBftdX9FgcwNAEcShiLzGuWbFcgueFweQdpatz7cYK
PhD. in economics (distinction in Asset pricing),12 years quant developer (R, Python), 4 years nodes operator, Validator/Collator on multiple DOTSAMA projects (Polkadot 1kv, Kusama 1kv, Moonbeam & Moonriver). LinkedIn.
Tommi Niemi
EtommijqrHDFWFvBxP515oUbkXx9vK2qohzrmwpCXbU7Yx2
Tommi, ecosystem validator for around 3 years and IBP infrabuilder for South East Asia at Rotko Networks, is a full-stack developer. Maintains open Proxmox Ansible rolebooks for running blockchains(Unlabored).
Adam Steeber
GqC37KSFFeGAoL7YxSeP1YDwr85WJvLmDDQiSaprTDAm8Jj
B.S of Economics from the University of Minnesota, Twin Cities: August 2017. 7 years of sales and marketing experience. 4 years of business & project management: CTO/ CFO of Steeber Solutions LLC. At least 1 year of FT experience in media, content creation, and social media management.
Started in the Kusama ecosystem in April of 2021 as an independent validator, receiving enough organic nominations (outside of TVP) to be elected in the active set. Expanded into RMRK technology and was inducted in the TVP in fall of 2021. Went full time into the ecosystem at the beginning of December 2021. Earned expertise in RMRK 2.0.0 development working on numerous projects. Moved on to data developments on Kusama with a Treasury-funded Chainlink integration. Currently an overall ecosystem agent, working for the betterment of Polkadot and Kusama both technically and socially.
I recommend a 4/4 threshold for this multisig, which gives us this address: EXo39uH9JZFu7Sijc79RmQUoWkamK25EEzpjCdikhrqW8sX
We'll create a governance pure proxy using this multisig and go on chain with a Treasury proposal to see if this idea can become a reality.