Polygon Multisigs
Capabilities
The primary function of the multisigs is to enable contract upgrades in the [current] early phases of development.
As the contracts secured by the multisigs become battle-tested, Polygon will introduce the following optimizations and changes:
- move from multisigs to governance-controlled proxies;
- introduce timelocks;
- eventually remove all multisigs.
To be clear, the current multisigs cannot censor transactions like bridge transactions.
Multisig Address | 5/9 multisig 0xFa7D2a996aC6350f4b56C043112Da0366a59b74c |
---|---|
Purpose | To upgrade POS/Plasma and staking contracts on Ethereum* |
Chain | Ethereum |
Rights |
|
Signatories |
|
Multisig Address | 5/8 multisig 0x355b8E02e7F5301E6fac9b7cAc1D6D9c86C0343f |
---|---|
Purpose | To to be able to update "custom" childerc20s if required on Polygon Commitchain* |
Chain | Polygon Commitchain |
Rights |
|
Signatories |
|
Multisig Address | Permissionless Mapping of standard ChildERC20 tokens (No Multisig Required) |
---|---|
Purpose | Use FxPortal supports permissionless token mapping of standard ChildERC20 for any ERC20 token on Ethereum |
Chain | Permissionless |
Rights | Permissionless |
Signatories | Permissionless |
Multisig Address | 4/8 Multisig 0x424bDE99FCfB68c5a1218fd3215caFfD031f19C4 |
---|---|
Purpose |
|
Chain | Ethereum |
Rights | Can only do mapping, doesn't have any access to Child token, no deposit/withdrawal rights whatsoever |
Signatories |
|