SPONSORED PARTNERMEXCExplore global spot and futures marketsEXPLORE MEXC →
CHARTING PARTNERTradingViewAdvanced charts, indicators and market analysisOPEN CHARTS →
TRADING PARTNERGMX via NetNapz TradeTrade decentralised perpetual marketsSTART TRADING →INTERNET COMPUTER · ICP NETWORK GOVERNANCE
ICP Executes P-256 Signing Enablement on Fiduciary Subnet
Published: 24 October 2026 · Execution date: 22 October 2026 · Evidence checked: 24 October 2026

The Internet Computer’s Network Nervous System executed proposal 144490 on 22 October, enabling fiduciary subnet pzp6e to sign with the threshold ECDSA P-256 master key identified as ecdsa:secp256r1:key_1.
What the governance record confirms
The ICP Dashboard identifies proposal 144490 as an executed UpdateConfigOfSubnet action. It records creation on 19 October at 13:55:45 UTC, an early decision on 22 October at 12:46:54 UTC and execution two seconds later. The decoded payload shows one item under chain_key_signing_enable for subnet pzp6e.
The final tally displayed 554.29 million voting power in favour and 1.26 million against, with 92.2% participation. These figures describe the governance decision; they do not measure use of the new signing capability.
Resharing preceded enablement
A DFINITY developer wrote on 19 October that resharing the secp256r1 master key from pzp6e to backup subnet uzr34 had succeeded. The follow-on proposal then sought permission for the fiduciary subnet to produce signatures with that key.
P-256, also known as secp256r1, is widely used in conventional security hardware and identity systems. Enabling the key at subnet level gives Internet Computer canisters access to another signing configuration, subject to the network’s chain-key interfaces and each application’s implementation.
NetNapz assessment
The material change is operational: the governance-controlled configuration moved from a proposed state to executed enablement. That removes one network-level prerequisite for canisters that need threshold P-256 signatures.
Execution does not prove that wallets, identity products or financial applications have integrated the key, nor does it establish transaction demand or an economic benefit for ICP holders. Adoption, production reliability and application-level security reviews remain separate questions.
Sources and scope
Reviewed the official ICP Dashboard proposal record, which reads governance data from the chain, and the DFINITY developer update describing the preceding key resharing and enablement proposal. This report covers the governance action and stated key configuration; it does not independently test signatures or application integrations.
