Goal: TSN Governance Tooling

[outerlook]

TSN Governance Tooling

What is this?

• governance here = manage streams officialization from centralized operators (us?)
• tools that help our team inspect TSN to take actions (see contracts, see official streams)
• tools that help our team apply governance decisions (execute officialization procedures)

What this is not?

• won't decide on how to vote to accept a stream
• won't establish how to decentralize governance
• won't manage any stream data that is unrelated to the system contract, except inspecting a contract itself

What this might be?

• Web User Interface
• CLI
• JS SDK

Soon, we'll create a Spec document to provide more details

[outerlook]

following #199 (comment) (@rsoury)

This issue was created to track a future goal of managing governance. We're currently in a centralized step where we trust all streams, and we don't need to say whether some data has TSN-ensured quality or not.

[rsoury]

Don't develop Governance interface from scratch.

• https://www.agora.xyz/ (open source)
• https://tally.xyz/ (closed source)
• https://snapshot.org/#/ (a little dated now, and votes are all off-chain)

I recommend deploying to Arbitrum as this seems to be the primary chain of TRUF token - @zolotokrylin to confirm

Each new stream addition, removal, etc. Should fit a proposal in governance.
Discord, etc. to coordinate call to voting.
Finally, for now, once votes and proposals are settled, Truflation (or the Stream Owner/Deployer) should manually manage Stream allocation to TSN Governance.

In a following issue, we can use a Kwil Oracle to detect proposals that have passed in favour, and then require a human to simply submit a procedure transaction to confirm.

We do not want to fully automate this, as governance attacks are still a think - see latest on Compounds Governance Attack.

[outerlook]

To better understand the scope of this goal, I agree with not building the voting process and UI from scratch. But should we touch on the voting system right now? Or just developing UI/CLI to manage this aspect:

Truflation (or the Stream Owner/Deployer) should manually manage Stream allocation to TSN Governance.

I initially had in mind provide tooling to

1. see what streams are official
2. revoke or grant official status to streams

Which is less scope. But if voting is important with the same priority, merging the scope is OK, too

[zolotokrylin]

governance here = manage streams officialization from centralized operators (us?)

Why is this important now? I can see how it might be helpful in the future (long, mid, or long term), but not within next 6 month or even more.
Is our business problem that we have too many streams, and most of them are bad quality, and our customers are struggling to identify and separate good from bad? And even if this problem exists (which I think it doesn't), why can't we just do it in a centralized way?

[zolotokrylin]

Let's schedule a call to discuss this.
Does tomorrow at 21:30 Hong Kong time work well for you?

[rsoury]

@zolotokrylin and @outerlook - It is correct to determine that this issue is not a current priority.

It is only a priority once third-party streams are created, and we need to establish an officialization process.

Re meeting, can we do 22:00 HK time?

[rsoury]

@zolotokrylin -- Following up, can we move to 22:00 HK? I may need to join 30 mins later otherwise.

[zolotokrylin]

It is correct to determine that this issue is not a current priority.
It is only a priority once third-party streams are created, and we need to establish an officialization process.

Let's have it centralized for now.
As we will not work on this anytime soon, let's push the call regarding this topic and have it sometime.

Could you please take a look here instead:

• Goal: 99.9% TSN Reliability #415