As we navigate OpenGov, we re finding new things: it seems this referendum #2 wont enact succesfully, because the call we used (treasury.ApproveProposal) will only be enacted successfully with root origin, which is the case.
We will need to resubmit this proposal:
on Treasurer track (same one)
with the call treasury.Spend (including the amount in KSM for the allocation)
The proposal has now been resubmitted 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.
Threshold
To those that supported this invalid proposal:
We have been informed that this will not pass due to invalid calls.
However feel free to change your vote to NO, just in case.
We have Voted NO to this proposal too.
We also appreciate if you support replacing proposal.