Komunitas Polygon (POL) Usulkan Dewan Keamanan dengan Ambang 8 dari 11 dalam Draf PIP-93

Crypto News and Tradfi News - COINOTAG · 2026-11-05T15:59:39.000Z

• Komunitas Polygon mengunggah draf PIP-93 pada 2026-11-05 dengan 11 penanda tangan dewan keamanan. • PIP-93 mensyaratkan 8 dari 11 tanda tangan untuk setiap tindakan dewan keamanan. • Peningkatan rutin akan diproses melalui multisig operasional Polygon Labs yang memerlukan persetujuan 5 dari 9 penanda tangan. Satu Dewan dengan 11 Penanda Tangan Siapa pun yang mengendalikan kunci privat di balik otoritas peningkatan jaringan dapat menjeda kontraknya, memulai ulang kontrak tersebut, atau mengirim transaksi langsung ke blockchain. Sebuah draf yang dipublikasikan di forum komunitas Polygon pada Kamis, 2026-11-05, akan mengubah kekuasaan tersebut secara mendasar bagi Polygon (POL). PIP-93, yang masih dalam tahap draf, mengusulkan penggabungan multisig yang saat ini terbagi antara dewan protokol dan dewan keamanan yang menaungi Polygon PoS serta tumpukan agregasi zkEVM menjadi satu dewan keamanan: 11 penanda tangan dari 10 organisasi di seluruh Ethereum dan Polygon, dengan setiap tindakan dewan memerlukan 8 tanda tangan. Polygon Labs akan mendapat dua kursi, sedangkan setiap organisasi peserta lainnya mendapat satu kursi. Perubahan sehari-hari akan sepenuhnya melewati dewan. Multisig operasional Polygon Labs, yang bertindak dengan persetujuan 5 dari 9 penanda tangannya, akan mengajukan peningkatan kontrak rutin dan perubahan administratif ke timelock, yaitu kontrak yang menahan perubahan yang telah disetujui selama jangka waktu tertentu dan baru dapat dijalankan setelah 7 hari. Multisig operasional itu dapat menjeda kontrak, tetapi draf tersebut tidak memberinya wewenang untuk melewati masa tunggu atau melanjutkan kontrak yang dijeda. Dewan tetap memegang wewenang khusus: membatalkan perubahan yang sedang menunggu sebelum masa tunggu berakhir, langsung menjalankan perubahan tanpa penundaan, melanjutkan kontrak yang dijeda, atau mengajukan transaksi secara langsung—masing-masing memerlukan ambang yang sama, yaitu 8 dari 11 suara. Saat ini, wewenang tersebut berada di tangan pihak yang berbeda, sehingga perubahan pada satu kontrak dapat menempuh proses yang berbeda dari perubahan pada kontrak lainnya. PIP-93 akan memberi jaringan satu jalur eskalasi dan satu ambang batas yang tercatat. Multisig hanya berfungsi jika kuncinya tetap independen, itulah sebabnya susunan anggotanya sama pentingnya dengan ambang batasnya. Bagi para pemegang token, rencana ini memindahkan wewenang nyata sebelum mereka mendapat kesempatan resmi untuk menyampaikan pendapat: belum ada pemungutan suara Snapshot yang tercatat, sehingga teks forum itu menjadi satu-satunya versi yang terdokumentasi. Perdagangan tampak tidak terlalu memperhatikan berita tata kelola tersebut, dan harga Polygon turun sekitar 3% dalam 24 jam terakhir.

• Polygon community posted the PIP-93 draft on 2026-11-05 with 11 security council signers.
• PIP-93 requires 8 of 11 signatures for every security council action.
• Routine upgrades would route through a Polygon Labs operations multisig needing 5 of 9 signers.
A Single Council of 11 Signers
Whoever controls the private keys behind a network's upgrade authority can pause its contracts, restart them, or push transactions directly onto the chain, and a draft published on the Polygon community forum on Thursday, 2026-11-05, would reshape exactly that power for Polygon (POL). PIP-93, still at the draft stage, proposes consolidating multisigs currently split between the protocol council and the security councils covering Polygon PoS and the zkEVM aggregation stack into a single security council: 11 signers drawn from 10 organizations across Ethereum and Polygon, with every council action requiring 8 signatures. Polygon Labs would hold two seats, and each other participating organization one. Day-to-day changes would bypass the council entirely. Polygon Labs' operations multisig, acting on 5 of its 9 signers, would submit routine contract upgrades and administrative changes to a timelock, a contract that holds an approved change for a fixed window, executable after 7 days. That operations multisig could pause contracts, but the draft denies it any power to skip the waiting period or resume a paused contract. The council keeps the overrides: canceling a pending change mid-wait, executing immediately without the delay, resuming paused contracts, or submitting transactions directly, each at the same 8-of-11 bar. Today those authorities sit in separate hands, so a change to one contract can follow a different path than a change to another; PIP-93 would give the network one escalation route and one recorded threshold. A multisig only works when its keys stay independent, which is why the composition matters as much as the threshold. For holders, the plan moves real authority before they get any formal say: no snapshot vote has been recorded, so the forum text is the only on-record version. Trading paid the governance news little visible attention, and Polygon price slipped about 3% over the past 24 hours.
The 8-of-11 Arithmetic
The draft lands against a recorded baseline. Under the current PIP-29 framework, an ordinary change needs 7 of 13 council members plus a 10-day timelock, while an emergency change needs 10 of 13 and can run with no waiting period at all. PIP-93 would cut the routine wait by 3 days, to 7, and replace the split thresholds with one uniform bar of 8 of 11 for everything the security council does. On disclosure, participating organizations would be named while individual signer names and addresses stay confidential. The stated reasoning is operational: impersonation attacks and physical coercion of identifiable key holders are cited as the risks of exposure, and the text concedes that accountability at the individual level weakens as a result. Whoever safeguards a seed phrase or an offline signing device carries personal risk, and the draft accepts weaker individual accountability in exchange for that reduced exposure. Implementation comes in two phases. Phase 1 rewrites the signer composition of the existing multisigs and hands routine operations, plus the power to pause contracts, to Polygon Labs' operations multisig, with no new contracts deployed. Phase 2 deploys timelock contracts on both Ethereum and Polygon and folds the remaining multisig schemes into a single structure per network, the arrangements that determine what node operators on either chain ultimately execute. The published text specifies the sequence but no dates. The seat count shrinks from 13 to 11 in the same breath. The plan follows a contentious stretch for Polygon governance, including a separate community proposal for a hard fork to recover 70.49M frozen POL, and custody trade-offs around the MATIC migration are detailed in Polygon Review 2026. A draft on a forum is as far as this has gone: no quorum, no tally, no outcome exists yet.
Set against the numbers, PIP-93 reads as a trade rather than a tightening. Routine control moves to a 5-of-9 multisig staffed by Polygon Labs and the waiting period shrinks from 10 days to 7, so ordinary changes get faster even as the seat count falls. The council's override bar of 8 of 11 works out to 72.7% of seats, marginally below the 76.9% the old emergency path demanded. What survives either way the vote goes is written into the draft itself: signer identities stay hidden, the text concedes individual accountability weakens, and eight anonymous key holders could still redirect contracts across both chains. Checking what a proposal actually does before approving it is what separates oversight from blind signing, and this design asks the market to trust organizations rather than names. Chart positioning is a separate question; Polygon technical analysis tracks the token's levels independently of the governance calendar.