Skip to content

PoS mainnet multi-signatures

Purpose and capabilities

The primary role of multi-signature wallets (multisigs) is to facilitate contract upgrades during the early stages of development. As these contracts become more robust, Polygon plans to:

  • Transition from multisigs to governance-controlled proxies.
  • Implement timelocks for added security.
  • Phase out multisigs entirely in the long term.


It’s important to note that the existing multisigs do not have the capability to censor transactions, including bridge transactions.

Active multi-signature wallets

Ethereum chain multisigs

Multisig Address \(5/9\) Multisig
Purpose To upgrade PoS and staking contracts on Ethereum.
Chain Ethereum
Rights - Update staking contracts for optimizations and upgrades.
- Address unexpected bugs in PoS contracts.
Signatories Quickswap, Curve, Polygon, Horizon Games, Cometh

Polygon commitchain multisigs

Multisig Address \(5/8\) Multisig
Purpose To update custom ChildERC20s on Polygon commitchain.
Chain Polygon commitchain
Rights Ability to upgrade custom child contracts.
Signatories Quickswap, Curve, Polygon, Horizon Games, Cometh

Custom child ERC20s mapping

Multisig Address \(4/8\) Multisig
Purpose To enable the mapping of custom ChildERC20s with Mainnet contracts.
Chain Ethereum
Rights Limited to mapping; no access to Child tokens or deposit/withdrawal rights.
Signatories Polygon

Permissionless mapping

Multisig address Permissionless mapping of standard ChildERC20 tokens (no multisig required)
Purpose FxPortal supports permissionless token mapping of standard ChildERC20 for any ERC20 token on Ethereum.
Chain Permissionless
Rights Permissionless
Signatories Permissionless

*Plans are underway to transition these functions to governance. We are currently exploring options such as Aave’s governance contracts and Compound’s timelock contracts.