Integration Guide: How to migrate from ECDSA to ML-DSA-65 in your blockchain project

[Babayagga-bite]

Migrating from ECDSA to ML-DSA-65

This guide shows how to replace ECDSA transaction signing with quantum-resistant ML-DSA-65 using the EPR-2 QaaS API.

Step 1: Generate a quantum-safe wallet

curl -X POST http://localhost:8080/api/qaas/wallet/keygen \
  -H "Content-Type: application/json" \
  -d '{"network": "mainnet", "label": "my-node-wallet"}'

Save signing.publicKey (your identity on-chain) and signing.privateKey (in a secure vault).

Step 2: Sign a transaction

const tx = {
  from: "qbc1q...",
  to:   "qbc1q...",
  amount: "1000000",
  nonce: 1,
  chainId: "my-chain-1"
};

const { txHash, signature } = await fetch("http://localhost:8080/api/qaas/tx/sign", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ transaction: tx, privateKey: signingPrivateKey }),
}).then(r => r.json());

Step 3: Verify on the receiving side

const { valid } = await fetch("http://localhost:8080/api/qaas/tx/verify", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ transaction: tx, signature, publicKey: signingPublicKey }),
}).then(r => r.json());

console.log("Signature valid:", valid); // true

Key differences from ECDSA

Property	ECDSA (secp256k1)	ML-DSA-65 (FIPS 204)
Public key	33 bytes	1952 bytes
Signature	64 bytes	3293 bytes
Quantum resistant	❌ No	✅ Yes
NIST standard	Legacy	FIPS 204 (2024)

The larger key and signature sizes are the tradeoff for quantum resistance. For most blockchain use cases (L2 rollups, state channels, cross-chain bridges), this is fully acceptable.

---

Questions? Comments? Post below! 👇