Secp256k1 and cross-chain governance

Secp256k1 is the signing curve used by Bitcoin, Ethereum, and many EVM wallets. In Quorum, it exists for a pragmatic reason: governance teams are often cross-chain before their tooling is. An Ethereum-native signer should be able to participate in a Solana-controlled treasury without receiving a separate Solana authority key.

That is useful. It is not post-quantum.

What it is

Secp256k1 is a Koblitz elliptic curve commonly paired with ECDSA. Ethereum derives account addresses from the Keccak hash of a secp256k1 public key, and Bitcoin also depends on secp256k1 signatures. Quorum supports secp256k1 identities so EVM-side signers can authorize Solana multisig actions through canonical Quorum preimages.

Its strengths are all about interoperability:

• It maps naturally to Ethereum-style identity.
• It supports teams with EVM custody policies and hardware wallets.
• It helps DAO, bridge, and protocol operators avoid duplicating human authority.
• It can participate in mixed Solana/EVM governance without making Solana accounts the only identity format.

Its weakness is the same as Ed25519's: it is elliptic-curve cryptography. A quantum attacker who can solve the elliptic-curve discrete logarithm problem can recover private keys from exposed public keys.

What agencies and researchers say

Google Quantum AI's 2026 cryptocurrency analysis focused directly on ECDLP-256, the family of problems behind secp256k1 and P-256. Google estimated circuits requiring fewer than 1,200 logical qubits, and fewer than 500,000 physical qubits under its superconducting assumptions.

NIST and NSA do not frame secp256k1 as a post-quantum migration target. NIST finalized ML-DSA and SLH-DSA for post-quantum digital signatures and is developing FN-DSA from Falcon. NSA's CNSA 2.0 suite is explicitly a transition away from current public-key assumptions for national security systems.

How to use Secp256k1 in Quorum

Secp256k1 belongs in Quorum when an EVM identity is operationally meaningful: a DAO council member, an Ethereum treasury signer, a bridge administrator, or an institution that already has Ethereum custody controls. It should be paired with post-quantum approval rules for long-lived authority.

A sensible policy is to let secp256k1 members propose, co-sign, or satisfy ordinary threshold requirements, while requiring at least one Falcon or Winternitz approval for execution. That lets cross-chain teams keep their governance map intact while reducing dependence on one classical curve family.

Bottom line

Secp256k1 is a compatibility feature. It lets Quorum represent how teams actually govern across chains. The quantum-ready part comes from explicit post-quantum members and pq_threshold, not from the EVM signer itself.

References

• SEC 2: Recommended Elliptic Curve Domain Parameters
• Google Quantum AI: Safeguarding cryptocurrency
• NIST post-quantum FIPS approval announcement
• NSA CNSA 2.0 quantum-resistant algorithm requirements