Add openGov track to facilitate posts on Kusama's X account #70
Conversation
| ), | ||
| ``` | ||
|
|
||
| I also recommend restricting permissions of this track to only submitting remarks or batches of remarks - that's all we'll need for its purpose. I'm not sure how |
There was a problem hiding this comment.
This doesn't work, but the track origin also could not really call anything problematic.
|
|
||
| ## Drawbacks | ||
|
|
||
| The main drawback to this change is that it requires a lot of off-chain coordination. It's easy enough to include the track on Kusama but it's a totally different |
There was a problem hiding this comment.
While reading this, why not post onto subsocial? I assume that this should probably work using a XCM message? We could then just have some kind of mirror from subsocial to twitter if wanted.
There was a problem hiding this comment.
This is a very clever solution! I wonder if @siman could provide insight here or recommend a good way to do this.
|
An idea that "fits [better] into the Kusama narrative" would be:
|
This is also an option, albeit gov1-ish. The ecosystem would just need to agree on, or be made aware of, the structure and timing of the election. How might we rally candidates to run? How might we facilitate this election? |
| and the community becomes totally autonomous in the management of Kusama's X posts. | ||
|
|
||
| This solution does not cover every single communication front for Kusama, but it does cover one of the largest. It also establishes a precedent for other communication channels | ||
| that could be offloaded to openGov, provided this proof-of-concept is successful. |
There was a problem hiding this comment.
| that could be offloaded to openGov, provided this proof-of-concept is successful. | |
| that could be offloaded to OpenGov, provided this proof-of-concept is successful. |
| This change might also be outside the scope of the Fellowship/openGov. Perhaps the best solution for the X account is to have the Treasury pay for a professional | ||
| agency to manage posts. It wouldn't be decentralized but it would probably be more effective in terms of creating good content. | ||
|
|
||
| Finally, this solution is merely pseudo-decentralization since the X account manager would still have ultimate control of the account. It's decentralized insofar as |
There was a problem hiding this comment.
The API keys and recovery information could live in an enclave. The enclave would then need to run a light-client listen for remarks.
Its a bit risky though, since if the enclave messes up then the account access is lost.
But technically it would be possible to make it fully trustless (% modulo Intel CPU backdors in the enclave 😉).
| ## Unresolved Questions | ||
|
|
||
| - Who will develop the tools necessary to implement this feature? How do we select them? | ||
| - How can this idea be better implemented with on-chain/substrate features? |
There was a problem hiding this comment.
I think in the past i saw something from Phala that advertised to make social media posts from their blockchain. Dont know how it works.
| This change also introduces on-going costs to the Treasury since it would need to compensate people to support the tools necessary to facilitate this idea. The ultimate | ||
| question is whether these on-going costs would be worth the ability for KSM holders to make posts on Kusama's X account. | ||
|
|
||
| There's also the risk of misconfiguring the track to make referenda too easy to pass, potentially allowing a malicious actor to get content posted on X that violates X's ToS. |
There was a problem hiding this comment.
Should maybe check that having a DAO-controlled account is not against TOS 🙃
There was a problem hiding this comment.
What if we make it a DAO-controlled phone with access to the Twitter app? I think I might have something... :P
|
|
||
| The overall motivation for this RFC is to decentralize the management of the Kusama brand/communication channel to KSM holders. This is necessary in my opinion primarily | ||
| because of the inactivity of the account in recent history, with posts spanning weeks or months apart. I am currently unaware of who/what entity manages the Kusama | ||
| X account, but if they are affiliated with Parity or W3F this proposed solution could also offload some of the legal ramifications of making (or not making) |
There was a problem hiding this comment.
Also no clue who manages it. Can ask around a bit.
The underlying assumption here is obviously that the Kusama Tokenholders are entitled to manage it though.
This RFC proposes adding a trivial governance track on Kusama to facilitate X (formerly known as Twitter) posts on the @kusamanetwork account.