devoracles.

NewsOracle Networks

Financial Institutions Begin Testing Quantum-Resistant Digital Signatures for Blockchain Assets

For oracle operators and Web3 infrastructure teams, the substantive concern is not the pilot itself but the cryptographic transition it signals at the custody layer beneath cross-chain attestation…

Financial Institutions Begin Testing Quantum-Resistant Digital Signatures for Blockchain Assets

-regional pilot convened by the Responsible Fintech Institute with custody infrastructure provider Safeheron began testing post-quantum digital signature schemes for blockchain-based asset transfers on August 24, operating on a dedicated NEAR testnet. The exercise evaluates wallet creation and on-chain transaction signing under NIST's ML-DSA-65 standard, one of the parameter sets within FIPS 204. For oracle operators and Web3 infrastructure teams, the substantive concern is not the pilot itself but the cryptographic transition it signals at the custody layer beneath cross-chain attestation, bridge validation, and threshold-signed oracle feeds.

Cryptographic Substrate: MPC over ML-DSA-65

The technical centerpiece is an MPC protocol in which transaction signing is distributed across multiple parties such that no single device or institution reconstructs a complete private key in one location. Safeheron's implementation layers this threshold-signing model with ML-DSA-65, the parameter set finalized within NIST FIPS 204 in August 2024 and currently believed to remain secure against an adversary possessing a large-scale quantum computer. That guarantee, however, remains contingent on correct implementation and continued cryptographic review, a dependency the organizers have acknowledged rather than dismissed. Bison Bank and DK Bank execute wallet generation and transfer flows inside a shared application environment, with transactions settling against the quantum-resistant NEAR testnet rather than the public mainnet. No transaction volumes, performance benchmarks, or test schedules have been disclosed, which constrains any assessment of signing latency or throughput under realistic institutional workloads and leaves the protocol's liveness characteristics unmeasured.

Governance Topology and Observer Roles

Regulator participation follows a phased integration model rather than direct execution. Abu Dhabi Global Market, Bhutan's Gelephu Financial Services Office, and the Malta Financial Services Authority enter as observers in phase one, with engagement levels calibrated to each institution's mandate and jurisdiction. A subsequent governance workstream will examine operational resilience, oversight, and cross-border interoperability — precisely the concerns that govern oracle network attestation paths and the cross-jurisdictional legal weight of cryptographic signatures. The architecture mirrors a familiar oracle pattern: distributed nodes producing attestations, with regulators occupying an observer role that can transition into enforcement authority as the system matures. Results drawn from a controlled testnet, however, cannot by themselves establish that the signing stack is ready for live institutional use, a caveat the organizers have placed at the center of the announcement.

Open-Source Trajectory and What Oracle Architects Should Track

Safeheron has indicated the protocol will eventually be released as open-source software, and the consortium plans a whitepaper covering the research, protocol design, and test findings. Neither artifact carries a confirmed publication date, which means independent reviewers cannot yet inspect the implementation or reproduce the benchmarks. As Responsible Fintech Institute Chairman Chia Hock Lai put it, no single bank, vendor, or regulator solves this alone. The relevant question for oracle network architects is whether threshold-signing libraries compatible with ML-DSA-65 will reach the same maturity tier as current ECDSA-based MPC stacks, and on what timeline. Until those libraries become composable with existing oracle nodes, bridge relayers, and decentralized sequencers, the pilot remains an isolated test environment rather than a production-ready transition path — a preparedness exercise worth monitoring, but not yet a forcing function for protocol upgrades in decentralized data infrastructure.