Polygon Multisigs

Multisig Address5/8 multisig
0xFa7D2a996aC6350f4b56C043112Da0366a59b74c
PurposeTo upgrade POS/Plasma and staking contracts on Ethereum*
ChainEthereum
Rights
  • Update staking contracts for staking optimisations, features and upgradations
  • Be able to fix unexpected and unforeseen bugs on POS/Plasma contracts
Signatories
  • Quickswap
  • Curve
  • Polygon
  • Horizon Games
  • Cometh
Multisig Address5/8 multisig
0x355b8E02e7F5301E6fac9b7cAc1D6D9c86C0343f
PurposeTo to be able to update "custom" childerc20s if required on Polygon Commitchain*
ChainPolygon Commitchain
Rights
  • Ability to upgrade "custom child contracts" ( and not the fx portal created standard tokens mentioned below)
Signatories
  • Quickswap
  • Curve
  • Polygon
  • Horizon Games
  • Cometh
Multisig AddressPermissionless Mapping of standard ChildERC20 tokens (No Multisig Required)
PurposeUse FxPortal supports permissionless token mapping of standard ChildERC20 for any ERC20 token on Ethereum
ChainPermissionless
RightsPermissionless
SignatoriesPermissionless
Multisig Address2/5 Multisig
0x424bDE99FCfB68c5a1218fd3215caFfD031f19C4
Purpose
  • To enable the mapping of "custom" child ERC20s with Mainnet contract.
  • 60% of Dapps deployed on Polygon "want" custom child ERC20 token, which needs to be mapped with supervision.
  • Eventually this can go to Governance but this will vastly increase the time for Dapp teams who want custom ERC20.
  • You can create standard child ERC20s yourselves using Fx portal, its permissionless, no mapping required
ChainEthereum
RightsCan only do mapping, doesn't have any access to Child token, no deposit/withdrawal rights whatsoever
Signatories
  • Polygon
*To be moved to governance. Exploring Aave's governance contracts and Compound’s time lock contracts
Last updated on