[Nakamoto] Capping Signer Weight #159
Replies: 3 comments 5 replies
-
This is only dicussing the cap on the signing weight; stackers can still stack an arbitrary amount of stacks. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Some comments on this. First, I want to acknowledge that the 69% limit just introduces one hop that someone needs to jump i.e., if there really is just a single signer then that party can delegate/transfer to a new address and boot up a new signer on a different IP, appearing as 2 signers to the network. So this limit check should be thought of more as a "reasonable default setting" than some hard cap that malicious parties can't bypass. So with that in mind, I think a 25% limit can be more reasonable than 69% as the "reasonable default setting". There are two reasons for this: In the grand scheme of things, I'd say this is not a very critical decision that we need to make. As I said earlier, this is really about picking "reasonable defaults", so I listed some arguments for why 25% might be better but I can be happy with the current default of 69% as well -- thanks! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This is a discussion post around capping signer voting weight such that any individual signer can only have voting power of some fraction of the system.
Relevant Draft SIP: SIP-021 #155
SIP Economics: economics.md
The signing threshold for signing a block and voting is currently planned to be 70%. The initial proposition was to cap the signing power at 69% but has evolved to capping the signing power at 25%.
Note that any cap implemented for the signers should be clearly communicated to members of the system.
Beta Was this translation helpful? Give feedback.
All reactions