Kusama issue #1: Treasury burn, Kappa Sigma Mu and the richest collective you've never heard of

Hi guys, I am briefly stepping into the discussion. We are iterating our society dApp and will move to the Beta phase in a few weeks.

I would like to understand how what we are building can support the future of the Kusama Society.

Here is the current landing page of our society dApp. We have made the tradeoff of building an extremely flexible product, reducing the amount of complexity, including inevitably removing some interesting game theory mechanics we look forward to integrating in the future.

The goal was to make a product that is as least opinionated as possible and easy to use, with the idea of iterating faster with real users first.

I will be attending Decoded next week. We can catch up with anyone around.

With Brad, we would love to book 1-1 demos for gathering feedback from existing KSM society members.

Please email us anytime at brad (at) jur (dot) io and ale (at) jur (dot) io, and we will be happy to jump on a call.

Thank you!

1 Like

Referendum 246: burn society pot, using setBalance to leave 1000 KSM

“Do we want 1% of Kusama’s issuance sitting around when we could be burning it?” @AlistairStewart

@bill_w3f i cannot access my PA account as am travelling.

Referendum 246 is very simple:

Use forceSetbalance to reduce Society pot to 1000 KSM from 137,000 KSM.

This would effectively burn 1% of Kusama supply.

1000 KSM should be ample to continue the economic game surrounding KappaSigmaMu given continuing receipt of the treasury burn.

Whether or not that continues may be the subject of a future referendum and runtime upgrade.

@Pheeb responding here to your Polkassembly comment.

Is a root track referendum the correct way to signal this?

Yes. It focuses attention.

The proposer understands the process. He is deliberately subverting. Why?

What do you mean “the process”? This is “Open”gov in action.

He won’t post the deposit because some one will call Referendum_Killer(246) on it and he knows that.

I haven’t posted the deposit because I do not have 3,333 KSM, if I did, I would.

I am a mere plankton, swimming amongst whales, learning how to drive the good ship Kusama.

Further, if someone did call Referendum Killer, that would essentially set a precedent that would blow up Kusama governance and OpenGov (Polkadot) in general.

People just wouldn’t want to add the deposit so unless we are on track to commit an early onchain Hari-Kari, things will be fine.

It is NOT an opportunity to express an on-chain view on whether we want to change another entities balance (ie. steal 99% of funds)

The society cannot access that pot by design. If they could, that would make this discussion even more interesting.

The purpose of this proposal is to be divisive and waste time.

I am merely a humble and unpaid Kusama civil servant putting into action this comment by an esteemed member of the W3F.

“Do we want 1% of Kusama’s issuance sitting around when we could be burning it?” @AlistairStewart.

The funds are already effectively burnt either way so the out-come doesn’t matter. Not wasting any more time on this.

Have a good week-end.

Society’s (currently) inaccessible funds still count towards issuance.

forceSetBalance would burn the tokens and reduce Kusama’s supply by 1%.

Quite different.

This idea has come up in several other OpenGov discussions, and I’d like to once again point out that OpenGov is not a case law system; that is, previous decisions are not precedents with authority for future decisions.

To be absolutely clear I am making no reference to case law or law or anything remotely connected.

I am simply talking very simply about how a precedent (some not seen before behaviour) informs the social psychology of the group.

Hence, a decision like this, would blow up OpenGov.

The simple fact is that people consistently over complicate what are incredibly blunt designs despite the relative complexity of the technology.

People are very predictable in social groups, especially when you add in tokens.