Crypto agility

Fixing a broken signature scheme or an exploitable contract needs someone with the power to ship new code. That power is also the most direct form of control over a network. This table puts the two side by side: who can replace each project's code, how many signatures it takes, how long anyone gets to react, and when the code was last changed against when it was last audited.

Projects read
44
upgrade control read from chain
No upgrade delay
19
code can be replaced the moment signers approve
Upgrades, last 12 months
81
across 10 projects with a scanned history
Host chain PQ roadmap
31
a published plan, merged code or a shipped option
Project Who can upgrade Delay Upgrades 12m Last upgrade Newest audit Signatures Chain PQ position
AethirATH 2-of-3 Safe (token not upgradeable) n/a n/a n/a none published secp256k1 ECDSA roadmap, not committed
Akash NetworkAKT Token-holder vote (x/gov) 1 day n/a n/a none published secp256k1 none found
Allora NetworkALLO Token-holder vote (x/gov) 12 h n/a n/a none published secp256k1 none found
AntSeedANTS One owner account; can repoint minting (token not upgradeable) n/a n/a n/a none published secp256k1 ECDSA roadmap, not committed
Artificial Superintelligence AllianceFET Token-holder vote (x/gov, 5 days; expedited route broken); a 3-of-5 Safe holds the ERC-20 mint 5 days n/a n/a none published secp256k1 none found
AukiAUKI 4-of-6 Safe upgrades the token none 0 never upgraded 30 Oct 2024 secp256k1 ECDSA roadmap, not committed
BittensorTAO Sudo key: a 2-of-3 multisig none 73 26 Oct 2026 none published sr25519 by default for coldkeys and hotkeys code merged to a release branch, not live
Cookie DAOCOOKIE 2-of-3 Safe on Base; one account owns the Ethereum leg n/a n/a n/a none published secp256k1 ECDSA roadmap, not committed
ElizaOSELIZAOS Mint: Squads 3-of-5 vault, or the Chainlink CCIP bridge pool n/a n/a n/a none published ed25519 plan exists, not activated
FLock.ioFLOCK 2-of-3 Safe upgrades the token none 0 never upgraded none published secp256k1 ECDSA roadmap, not committed
FluxFLUX Node release (forks at heights set in code) n/a n/a n/a Mar 2025 secp256k1 ECDSA statement, no plan
GensynAI 3-of-8 Safe upgrades the rollup; token behind a 7-day timelock none n/a n/a 17 Sept 2026 secp256k1 ECDSA roadmap, not committed
GizaGIZA 2-of-4 Safe (token not upgradeable, mint spent) n/a n/a n/a none published secp256k1 ECDSA roadmap, not committed
Golem NetworkGLM Immutable n/a n/a n/a Sept 2026 secp256k1 ECDSA roadmap, not committed
GrassGRASS Mint: Squads 2-of-3 vault n/a n/a n/a 1 Jul 2024 ed25519 plan exists, not activated
HeuristHEU One owner account, no lever left (token not upgradeable) n/a n/a n/a none published secp256k1 ECDSA roadmap, not committed
Intelligent InternetFC No chain or contract found n/a n/a n/a none published n/a not checked
io.netIO Programs: Squads 2-of-3 vault; mint fixed none last deploy only 30 Jun 2026 none published ed25519 plan exists, not activated
IoTeXIOTX Node release (forks at heights set in code) n/a n/a n/a 2018 secp256k1 ECDSA roadmap, not committed
MorpheusMOR 5-of-9 Safe owns the core contracts none 2 31 Jul 2026 open secp256k1 ECDSA roadmap, not committed
NEAR ProtocolNEAR Validators signal a new release; switches at 4/5 of stake n/a n/a n/a 24 Oct 2023 Ed25519 and secp256k1 ECDSA, with opt-in ML-DSA accounts since protocol 85 opt-in PQ accounts shipped; consensus on roadmap
NillionNIL 3-of-5 Safe upgrades and mints the token none 0 17 Oct 2025 none published secp256k1 ECDSA roadmap, not committed
NosanaNOS Programs: Squads 2-of-4 vault; mint fixed none last deploy only 28 Oct 2026 10 Aug 2022 ed25519 plan exists, not activated
Nous Research One key upgrades the Psyche programs (devnet) none n/a n/a none published ed25519 not checked
NuNetNTX One account upgrades the BSC token; 2-of-3 Safes elsewhere none n/a n/a 20 Sept 2021 secp256k1 ECDSA roadmap, not committed
Oasis NetworkROSE 68% stake vote (consensus); one entity key (Sapphire) n/a n/a n/a none published ed25519 and secp256k1 none found
Ocean ProtocolOCEAN Immutable (all roles renounced) n/a n/a n/a none published secp256k1 ECDSA roadmap, not committed
Olas (Autonolas)OLAS Timelock: governor vote, or a guarded 5-of-9 Safe none n/a n/a 9 Feb 2026 secp256k1 ECDSA roadmap, not committed
OpenmindROBO 3-of-5 Safe (token not upgradeable) n/a n/a n/a none published secp256k1 ECDSA roadmap, not committed
OpenServSERV 2-of-5 Safe: blacklist and trading switch (not upgradeable) n/a n/a n/a none published secp256k1 ECDSA roadmap, not committed
Ora ProtocolORA Immutable n/a n/a n/a 13 Jul 2024 secp256k1 ECDSA roadmap, not committed
OriginTrailTRAC Council-led referendum, can be fast-tracked (NeuroWeb) n/a n/a n/a 1 Jan 2018 ed25519, sr25519 or secp256k1 ECDSA via MultiSignature research only
peaqPEAQ Sudo key: a 2-of-4 multisig none 2 6 Sept 2026 10 Jun 2024 sr25519, ed25519 or ECDSA through Substrate MultiSignature none found
Phala NetworkPHA 4-of-11 Safe upgrades the rollup none n/a n/a 1 Jun 2025 secp256k1 ECDSA roadmap, not committed
Render NetworkRENDER Squads multisig vault upgrades both authority programs none last deploy only 2 Dec 2025 open ed25519 plan exists, not activated
Sahara AISAHARA 5-of-6 Safe can pause (token not upgradeable; chain not live) n/a n/a n/a none published secp256k1 ECDSA roadmap, not committed
SentientSENT 4-of-7 Safe upgrades the token none 1 2 Nov 2025 none published secp256k1 ECDSA roadmap, not committed
Theta NetworkTHETA Node release (forks at heights set in code) n/a n/a n/a none published secp256k1 ECDSA none found
VanaVANA 3-of-7 Safe upgrades the core contracts none 3 15 Jun 2026 1 Jul 2025 secp256k1 ECDSA none found
Venice AIVVV 4-of-6 Safe upgrades staking, which mints VVV none 0 20 Aug 2025 30 Apr 2025 secp256k1 ECDSA roadmap, not committed
Virtuals ProtocolVIRTUAL One account upgrades the agent registry none 0 5 Sept 2024 24 May 2025 secp256k1 ECDSA roadmap, not committed
WalrusWAL Storage-node quorum vote, or an emergency multisig of 4+ of 8 keys none n/a n/a 3 Mar 2025 Ed25519, secp256k1 ECDSA, secp256r1 ECDSA and multisig roadmap, not committed
Warden ProtocolWARD Token-holder vote (x/gov) 2 days n/a n/a none published eth_secp256k1 statement, no plan
ZetaChainZETA Token-holder vote (x/gov); a 6-of-8 admin group for contracts 1 day n/a n/a 11 Jul 2025 eth_secp256k1 none found

Newest upgrade-control read: 30 Oct 2026. Upgrade counts come from on-chain history scans and stop at each scan's date.

How to read it

  • Who can upgrade is read from the chain: the key, multisig, module or vote that can replace the code, with its threshold. A multisig shows signer accounts, not who holds them.
  • Delay is the shortest wait the chain itself enforces between approval and new code. "None" means nothing on chain forces a wait; a team may still announce upgrades in advance.
  • Upgrades 12m counts code replacements found by scanning the chain's history: proxy implementation changes, diamond cuts, or Substrate runtime changes checked against a rising spec version. A proxy's first implementation is its deployment, so it is not counted. Solana keeps only the last deploy, so those rows show its date and no count.
  • Newest audit is the latest audit the project publishes. Code replaced after that date is code no auditor has been shown to read, which makes it a question for the project before it is ever a finding. "Open" marks a question we have put to the project and are waiting on.
  • Chain PQ position quotes the host chain's own stated post-quantum plan, if any. It states intent, and deployed behaviour can differ.

Damaging facts are read a second way before they appear here, for example a multisig address re-derived from its signers. The full method and every open lead are in the integrity board rows these facts feed, and in each project's research record via the API.

A dated snapshot, not live advice. This is not financial advice.