[Replacement for Referenda #2] Polkawatch Decentralization Analytics Parachain Support and Continued Operation.
[Original treasury submission, that wont pass due to not applicable root call (treasury.ApproveProposal) can be found here]
Hi Community,
We recently launched Polkawatch decentralization analytics on Kusama, and Nomination Pools support.
The community is becoming more and more aware of the need for effective decentralization in our Ecosystem.
The interest peaked with a recent deplatforming event of Solana nodes by a Network operator.
We are been contacted by other teams of our community: Wallets, Parachains, Data Scientists, etc That want access to the data and help contribute to bringing awareness to the ecosystem. Which I think is good news.
Parachains are secured by the rely chain, but they are still vulnerable to censorship. Censorship could come from dishonest collators, deplatforming from network operators or sudden regulatory changes from hosting Countries. Despite been secured by the rely chain, parachains would benefit from decentralization analytics too.
On this proposal we aim to bring parachain support for Polkawatch, on top of continued operation of the service and other minor improvements.
The proposal has been for discussion here.
We were invited to participate in AAG#11 where an interesting discussion followed
Community feedback has been incorporated to the proposal.
You can access the detailed proposal here.
Note: an extraordinary fee related to re-submission costs has been included.
Comments (4)
Proposal Passed
3
of 3Summary
0%
Aye
0%
Nay
Aye (427)0.0 PAS
Support0.0 PAS
Nay (5)0.0 PAS
Comments (4)
thanks for the support!
Unfortunately it was brought to our attention that a misinterpretation of the parameter "after", which is NOT an absolute block number but a delay expressed in blocks, implies that when passed this referenda would take years to enact. This referenda will also be cancelled.
We have also been advised to wait for next kusama runtime upgrade that includes tweaks in OpenGov that we are finding out are required.
We will file our 3rd attempt right afterwards :)
We are sorry for the inconvenience, but at the same time we are happy to participate in rolling out OpenGov even if that serves us with our little dose of Chaos.
thanks for the support!
Unfortunately it was brought to our attention that a misinterpretation of the parameter "after", which is NOT an absolute block number but a delay expressed in blocks, implies that when passed this referenda would take years to enact. This referenda will also be cancelled.
We have also been advised to wait for next kusama runtime upgrade that includes tweaks in OpenGov that we are finding out are required.
We will file our 3rd attempt right afterwards :)
We are sorry for the inconvenience, but at the same time we are happy to participate in rolling out OpenGov even if that serves us with our little dose of Chaos.