Skip to content

Commit c9fe2cd

Browse files
Merge pull request 0xPolygon#330 from 0xPolygon/fix/zkevm-council-update
Fix zkEVM Secity Council Info
2 parents ea4b27c + 40ada6c commit c9fe2cd

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/zkEVM/architecture/protocol/security-council.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ In addition to the previously mentioned governance issues and security measures,
22

33
Since critical bugs or other security issues may occur, and hence warrant instant upgrades, it is good security practice to allow for emergency upgrades.
44

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.
66

77
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.
88

@@ -25,7 +25,7 @@ Security councils generally consist of a certain number of reputable community m
2525

2626
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.
2727

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.
2929

3030
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_.
3131

@@ -44,16 +44,16 @@ Here is a list of the 8 addresses of the Polygon zkEVM's Security Council;
4444

4545
### Security council multisig?
4646

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.
4848

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.
5050

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.
5252

5353
## Conclusion
5454

5555
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.
5656

5757
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.
5858

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

Comments
 (0)