A draft Polygon governance proposal would let Polygon Labs queue upgrades to bridge and staking contracts without gathering council signatures for every change, while a consolidated Security Council could veto them or execute changes immediately.
PIP-93, dated Nov. 2, 2026 and authored by Christopher von Hessert, would combine the Protocol Council, Polygon PoS and AggLayer multisig structures into one governance structure per network. Eleven signers from ten organizations would operate under an 8-of-11 policy on Ethereum and Polygon.
The proposal remains marked “Draft” in Polygon's repository. It is listed on the Nov. 5 Protocol Governance Call agenda, where Polygon Labs' validator-support team said more details would be presented.
The practical shift would be from affirmative council approval of each routine change to a Labs-led queue that the council must actively stop.
Under PIP-29's framework, regular configuration changes require seven of 13 council signatures and a 10-day delay; immediate changes require ten of 13. PIP-54, the earlier PoS permissions-transfer proposal, assigns contract upgradeability to the 10-of-13 route. Its scope includes validator staking, bridge deposits and withdrawals, and token escrow contracts.
PIP-93 would give a separate Polygon Labs Operations multisig, composed of security and engineering personnel, a 5-of-9 threshold to propose upgrades and administrative changes through a seven-day timelock. It could also pause contracts, but could neither bypass the upgrade delay nor unpause them.
The council could cancel queued transactions, submit changes itself, execute immediately or unpause contracts, all at 8 of 11 signatures. The seven-day window would therefore apply to Labs-proposed upgrades, not every possible upgrade. Immediate council action would require fewer signatures than PIP-29's emergency route.
Von Hessert argues that repeated signing ceremonies have become a bottleneck as bug fixes and bridge and staking upgrades accumulate. The proposed Labs route would remove the need for council signatures on every routine change, while leaving the council able to intervene.
A Smaller Council, Less Signer Disclosure
Polygon Labs would hold two council seats, with one each for Sherlock, OpSek, Hexens, Sigma Prime, Curve, QuickSwap, EthCC, L2Beat and Coinbase. The Labs seats would be held by internal multisigs rather than individuals.
The draft would replace PIP-29's publicly named membership commitment with organization-level disclosure: individual signer identities and addresses would not be published. Membership changes would require council approval under the 8-of-11 policy, replacing PIP-29's requirement that they be governed by the PIP framework.
Implementation would proceed in two phases: first changing signer sets on existing multisigs and reassigning operational and pause rights to Labs Operations, then deploying timelocks and consolidating the remaining structures. The draft says affected contract addresses would be published before execution.