You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/zkEVM/architecture/protocol/security-council.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@ In addition to the previously mentioned governance issues and security measures,
2
2
3
3
Since critical bugs or other security issues may occur, and hence warrant instant upgrades, it is good security practice to allow for emergency upgrades.
4
4
5
-
That is, instead of employing the 2-out-of-3 _Admin Multisig Contract_ and waiting for the time-delay imposed by the _Timelock Contract_, these contracts get bypassed by deploying a so-called _Security Council Multisig_.
5
+
That is, instead of employing the 2-out-of-3 _Admin Multisig Contract_ and waiting for the time-delay imposed by the _Timelock Contract_, the _Security Council Multisig_ may actvate the [_emergency state_](malfunction-resistance/emergency-state.md) to bypass such time-delay.
6
6
7
7
It is crucial, however, to emphasise that the _Security Council Multisig_ is a temporary measure, and will ultimately be phased-out once the Polygon zkEVM has been sufficiently battle-tested.
8
8
@@ -25,7 +25,7 @@ Security councils generally consist of a certain number of reputable community m
25
25
26
26
These are individuals or organizations with vested interest in the welfare of the Ethereum ecosystem, and are normally selected from among well-known Ethereum developers and researchers.
27
27
28
-
The Polygon zkEVM's Security Council is constituted of eight (8) members, four of whom are internal to the Polygon team, while the rest of the members must be from outside Polygon.
28
+
The Polygon zkEVM's Security Council is constituted of eight (8) members, two (2) of whom are internal to the Polygon team, while the rest of the members must be from outside Polygon.
29
29
30
30
The minimum requirement, even as mentioned in the L2Beat report downloadable [here](https://l2beat.com/multisig-report), is for these individuals to be adequately _knowledgeable and competent enough to make the best judgment about the actions approved by the multisig_.
31
31
@@ -44,16 +44,16 @@ Here is a list of the 8 addresses of the Polygon zkEVM's Security Council;
44
44
45
45
### Security council multisig?
46
46
47
-
The Security Council Multisig is a _multisig contract_ deployed by the Polygon zkEVM Security Council when either an_emergency state_is triggered or an _emergency upgrade_ needs to be executed.
47
+
The Security Council Multisig is a _multisig contract_ deployed by the Polygon zkEVM Security Council that allows the_emergency state_to be triggered, in the case an _emergency upgrade_ needs to be executed.
48
48
49
-
The _multisig contract_ is a _6-out-of-8_ multisig, which requires six (6) signatures of the Security Council to be attached for the contract to be successfully deployed.
49
+
The _multisig contract_ is a _6-out-of-8_ multisig, which requires six (6) signatures of the Security Council to be attached for the _emergency state_to be triggered.
50
50
51
-
There is a further stipulation that a minimum of 2 out of the 6 attached signatures must be from among the 4 members who are external to Polygon.
51
+
There is a further stipulation that a minimum of 4 out of the 6 attached signatures must be from among the 6 members who are external to Polygon.
52
52
53
53
## Conclusion
54
54
55
55
Although the ultimate goal is to move towards a totally decentralized Polygon zkEVM, employing a security council multisig is inevitable for the early stages of the zkRollup.
56
56
57
57
It is a trade-off between security and decentralization. So then, for the sake of long-term security, it is a deliberate decision to have more centralized early stages of development, in order to attain more decentralized later stages.
58
58
59
-
Although there is always a possibility for the members of Security Council to go rogue and collude, the 75% threshold together with the minimum 33% of external members’ signatures significantly reduces the risk.
59
+
Although there is always a possibility for the members of Security Council to go rogue and collude, the 75% threshold together with the minimum 66% of external members’ signatures significantly reduces the risk.
0 commit comments