Automatic

Three sampled Polygon PoS ownership slots retained a legacy timelock while separate Protocol Council signing infrastructure was deployed. Role queries connect the legacy Safe to that timelock. A source reproduction identifies its executable rules, a historical receipt dates the minimum-delay change, and a recent transaction shows three zero-delay operations through the route. The July 2026 and October snapshots distinguish the Council’s existence from its control of these particular contracts.

The sampled contract rights give appointment, consultation and review a specific object. An appointed body’s mandate must be connected to the actions it can authorize and the constraints affected participants can invoke. Staked-POL signaling supplies a documented advisory route; a separate Treasury announcement reallocates organizational responsibilities without completing its implementation map. The records support comparisons of public mandates, configured authority and observed action. Other privileges and responses to disagreement remain unresolved.

A council can have named members, published selection criteria and deployed signing infrastructure before it controls a particular contract. A contract can retain the same owner address while the institution authorized to act through that address changes. Neither a governance label nor an address, taken alone, resolves who can do what.

Delegating specialized decisions to a small body can be reasonable: participants may want expertise, operational continuity and rapid responses to faults. The relevant questions concern its mandate, appointment, conflicts, removal, reasons for decisions and opportunities for review. Those questions become answerable only after the executable office has been identified. A public commitment to consultation attached to one route does not automatically constrain another.

Polygon’s Protocol Council makes this problem unusually inspectable. Its proposals name signers, thresholds, timelocks, contract addresses and proposed transfers. A separate signaling framework gives staked-POL holders and delegates a role in regular system-contract proposals. These artifacts permit a comparison between the institution described and the rights configured, without treating Polygon PoS as governed through one mechanism.

The scope here is selected system-smart-contract authority. Polygon’s governance documentation separately describes client upgrades through ecosystem and validating-stake consensus, and a Heimdall governance module for consensus parameters (Polygon Developer Documentation n.d.b). Treasury administration is another distinct domain. The findings below do not classify the chain as a whole.

Polygon’s October reference page still listed the legacy Ethereum Safe as the active PoS/staking upgrade multisig (Polygon Developer Documentation n.d.a). A label identifies the route to inspect; the contract responses supply the sampled state.

An ownership slot is one edge in an authority graph; the next edge here is the timelock’s role configuration. The new queries establish that the legacy Safe held both PROPOSER_ROLE and EXECUTOR_ROLE. The two sampled Council Safes held neither role. The zero address did not hold the executor role, and the timelock itself held TIMELOCK_ADMIN_ROLE. These checks identify a positive route from one Safe through a timelock to three sampled owners. They do not enumerate every role holder or exclude every alternative path.

The explorer’s verified-source response identifies a TimelockController-derived contract. Compiling its exact multi-file source with Solidity 0.8.7 reproduces all 11,395 runtime bytes returned by the block-pinned RPC call. That implementation gates scheduling through the proposer role and execution through the executor role, with open execution when the zero address holds that role. The returned state does not satisfy the open condition. The compiler comparison connects the queried roles to the sampled executable code (Blockscout 2026a).

PIP-54’s table describes the legacy Ethereum route as having a two-day timelock (Polygon 2024d). The legacy timelock returned a zero minimum delay. A historical transaction locates the parameter change: at block 20,606,116, on 25 August 2024, the contract emitted MinDelayChange(172800, 0). Matching transaction, receipt and block responses from two services confirm the dated transition. The receipt establishes when this parameter changed (Blockscout 2026b). The reasons for the change and any separate procedural waiting requirement remain unresolved. A proposal table therefore cannot substitute for the configuration and history of the route being evaluated.

On 13 October 2026, a transaction called the legacy Safe. Its MultiSend payload scheduled and executed three timelock operations in the same transaction, each with a zero delay. Their operation identifiers, targets and payloads reconcile between transaction input and the successful receipt. One operation targeted the sampled StakeManagerProxy and two targeted GovernanceProxy. The external transaction sender was a relay address, distinct from the Safe through which authorization operated. The transaction establishes an observed use of the route (Blockscout 2026c). It contains no contested signal, Council rationale or evidence that affected participants could revise the decision.

PIP-29 established a thirteen-member Council design with a seven-signature regular route and ten-day timelock, alongside a ten-signature emergency route without the ordinary delay. It published selection principles concerning technical competence, security, resilience, value alignment and limited Polygon Labs influence (Polygon 2023).

PIP-54 then proposed direct transfers of specified Polygon PoS ownership and operational rights into Council routes. PIP-68 proposed another kind of change: replace signers and signature policy in the existing legacy Safes while preserving their addresses (Polygon 2024d; Polygon 2025b). These are institutionally different operations. One changes the contract holding a right. The other can change who acts through an existing contract without changing that contract’s address.

At the newly captured repository revision, both proposals still carried Peer Review status. The three sampled ownership slots retained the legacy timelock, and the legacy Ethereum Safe still reported five of nine. PIP-54 proposed different ownership destinations, and PIP-68 proposed seven of thirteen. This establishes a bounded discrepancy between two published designs and the sampled configuration. It does not show that nothing changed elsewhere or that a proposal’s status reliably records every implementation transaction.

The Council itself did change. PIP-67 replaced signer positions in 2025 and converted two individual Polygon Labs seats into organizational multisigs. PIP-77 replaced three members in 2026 while retaining the two Labs organizational seats (Polygon 2025a; Polygon 2026a). The October Council Safe owner sets matched PIP-77. A deployed Council and an unrealized transfer on particular sampled surfaces are compatible observations.

Appointment also requires its own evidence. PIP-67 says incoming members were approved by existing Council members. PIP-77 describes recertification less precisely. These documents support an inquiry into incumbent participation in selection; they do not establish an identical procedure for every appointment. Fixed terms, general conflict rules, a public recall route and independent review are not clearly specified in the reviewed PIPs. Relevant agreements or off-chain institutions may supply further provisions.

PIP-50 describes an off-chain signaling sequence for regular system-contract proposals. The ordinary PIP process and Council consensus precede staked-POL holder and delegate signaling. The proposal then returns to the Council for confirmation and execution, or a decision not to execute (Polygon 2024b). It does not describe token voting as a substitute for Council authorization, and it does not place emergency proposals under the same sequence. This collection establishes the captured PIP’s design; it does not establish the current availability or use of the Governance Hub.

Lack of automatic execution does not settle whether consultation constrains authority. An advisory vote may prompt reconsideration, impose reputational costs, trigger an appeal or inform a later appointment. Conversely, a visible vote may leave affected participants without an effective response when the executing body declines to follow it. Neither outcome can be inferred from the interface alone.

The research task is to join the stages. For a disputed proposal, record the eligible population, signal and quorum, Council response, reasons, transaction or non-execution, delay and any subsequent challenge. Compare the route through which participants expressed a preference with the route through which the decision became operative. This would distinguish acknowledgment from answerability and answerability from a power to revise or remove the decision-maker. No such contested-decision sample is claimed here.

PIP-40 described a Labs-operated Proposer Safe and a Community Treasury Board Executor Safe with separate approval functions, stating that Labs could not distribute funds without the Board’s approval (Polygon 2024a). A 9 January 2026 forum announcement described the Board becoming advisory, the Foundation setting strategy, and Labs handling daily execution and publishing biannual reports (Polygon 2026b). That documentary account leaves relevant wallet controls, activation transactions and surviving approval constraints unidentified. It does not complete an on-chain map of Treasury power: a reporting commitment concerns explanation and review, while an execution role concerns the capacity to move funds.

Walch (2017) and De Filippi and Wright (2018) motivate close attention to operative control beneath decentralizing vocabulary. Tracing a disputed action requires identifying the officeholder, how that actor was selected and what the office authorizes. The inquiry then follows the constraints that can prevent, delay, revise or review the action, and the route through which an affected participant can invoke them.

The IETF supplies a useful comparison of institutional arrangements around technical expertise. Its documented nomination, confirmation, terms, recall and appeal provisions show how appointed technical offices can be surrounded by procedures for selection and challenge (IETF 2000; IETF 2020; IETF 2022). RFC 9389 updates NomCom eligibility under RFC 8713; the comparator must be read with its update chain (IETF 2023). These provisions concern different offices and institutional populations. They do not govern upgrade keys or reproduce Polygon’s financial incentives, and their existence is not a score for either system.

The comparison nevertheless sharpens the Polygon questions. A published signer list makes the key configuration inspectable. A term or recall rule addresses continued occupancy. A signal exposes a preference. A required response makes its treatment reviewable. An executable delay may create an opportunity to react, but only on the route to which it applies. These are different institutional functions, and one cannot silently stand in for another.

Mapping the executable office attaches those questions to a particular capacity. An announced Council cannot be credited with a right it has not been shown to hold, while a familiar address cannot establish unchanged institutional control. Dated documents, configuration and action allow both relations to be investigated.

The study compares a July observation at Ethereum block 25,539,164 with finalized block 26,215,899, hash 0x17c96e7aba1dfd887aefa4d53302ea87544ffd6acc0922da05ab11c4bd027d33, captured on 17 October 2026 in Toronto. Two RPC services returned matching results for all thirty-one October request IDs; agreement does not establish independent upstream infrastructure. Sampling is purposive: PIP-54 names the three Ethereum contracts, each exposes an ownership view, and the associated Safe and timelock views permit a tractable route reconstruction. The sample is not a census of PIP-54 rights, Polygon-chain privileges, proxy-admin slots or validator governance. Role tests cover named candidate addresses; no complete role-member enumeration was performed.

At the same October block, all three sampled Safes returned an empty enabled-module list with completed pagination and a zero transaction-guard slot. Their fallback-handler slots were nonzero, and the legacy Safe reported version 1.4.1 while the Council Safes reported 1.3.0. These checks narrow the sampled execution map without identifying every contract-owner route, signer controller or privilege. Public key and address records do not identify legal persons or independent organizations.

Source capability, configured authority and exercised authority remain separate. The role result and additional Safe checks improve the configuration map. The two recovered action receipts identify successful uses of the legacy route and the dated delay change. They do not identify the legal or organizational controllers of every signing key, reconstruct all prior authorization changes or show how an incumbent responded to opposition. The Treasury and signaling material is documentary evidence with narrower implementation coverage.

The next empirical step extends these transaction records into a small sample joining appointment and mandate records, signals, reasons and executed changes. That would test how the arrangements work under disagreement. Completing every possible control edge is necessary for a whole-system claim, but the bounded comparisons above can already show where published institutional descriptions and specific configurations diverge.

The Protocol Council’s existence, the configuration of a Safe and the exercise of a particular right are separate facts. At the October snapshot, the sampled ownership slots still named the legacy timelock, the legacy Safe held proposer and executor roles, and separate Council infrastructure matched the documented membership. A historical receipt dates the legacy delay’s reduction to zero, and a recent transaction uses that setting for three operations. These findings locate a specific route and show its use without turning it into Polygon’s whole governance structure.

Appointment, consultation, reasons, review and removal acquire practical meaning through the offices to which they apply. For a disputed proposal, the next comparison should join the signal and Council response to the route that made the decision operative, then identify how affected participants could seek revision. That would test the institutions surrounding the observed capacity under disagreement.