-
Notifications
You must be signed in to change notification settings - Fork 59
O> Attack Governance Model #135
Comments
https://docs.google.com/document/d/1EW0H833BsBZV9hWQC7cl3_KucMbckQfPpVQtEK3JOuQ/edit?usp=sharing This a first draft i wrote, we would be need some volunteers to test these postulations. Edit: I just realised this issue was for the governance committee which am not part of. Since the links is here already I would leave it for as a note. Except there is a need to remove it. |
@dckc yes, I even wrote it for this issue initially, to be honest. Oke so for everyone else: a week ago @traviagio and I made an analysis of the "attack vectors" that we currently see exposed (or can easily imagine) in the Coop governance structure. The document can be found here: Analysis of attack vectors: https://docs.google.com/document/d/1qHQIuzj83VeZjusy6AvK7PAoKrg0CKP2SQTtNYv_3GI/edit?usp=sharing Main findings:
|
@Phistr90 be sure to explain why when you reopen an issue. |
@dckc This has just been resolved and addressed as well as analysed in regards to attack vectors of the bounty system. I might be wrong here, in this case please point me to the extensive attack vector analysis. |
Phil's POV "a critical part of the security of the whole platform. one has to avoid that the coop ends up being a SPOF due to political centralization & centralization of development decisions as well as centralization of staking coins. after all the coop has a jurisdiction and that might be an SPOF as well. I know it sounds weird at this point but maybe more restrictions of the coop's power might be better for the overall platform security. also it is much harder to restrict the power of the coop later on."
The text was updated successfully, but these errors were encountered: