What's new, what's fixed, and what's shipped in each release.
SDK security hardening release. v2.4.0 ships X3DH-style key exchange (X25519 + Ed25519, signed pre-keys, one-time pre-keys), strict server-parity tested SHA-256 + canonical JSON hashing, audited cryptographic primitives, and fixes for several edge cases in the encryption/decryption flow. Drop-in upgrade from v2.3.x — no breaking API changes.
X25519 (key agreement) + Ed25519 (signatures), with signed pre-keys and one-time pre-keys for forward secrecy@noble/curves librarynpm install @anchora/sdkanchor(), verify(), getProof()KeyManager API for X3DH key bundles (backup, recover, rotate)chainType and record statusAnchor records to public, private, or both chains in one API call. Anchora now supports Polygon (EVM), Hyperledger Fabric (private, BYO), and Hybrid mode — same Merkle root committed to both chains with independent verification. Existing customers see zero breaking changes; new fields are additive.
Public (Polygon), Private (Fabric BYO), Hybrid (both), Custom (any EVM RPC or Fabric profile)fabric-gateway SDK with auto-deployed anchora-anchor chaincodeLPOP queue consume — no duplicate batches under concurrent workerschainType, networkId, and a dualAnchor sub-object for Hybrid recordsX-Anchora-Chain and X-Anchora-Network/v1/verify returns independent verification verdicts for primary and secondary chainsblockNumber is explicit null (fabric-gateway constraint), transactionHash is raw txID, batchId is a string@anchora/sdk v2.3.0 with TypeScript types for all new fields/v1 core reference: base URL https://api.anchora.co.in/v1, Bearer token auth, MongoDB ObjectId record IDs, status enum tightened (QUEUED, BATCHING, ANCHORED, FAILED)X-Delete-Mode header to JSON body {"mode": "soft|hard"}recordId, hash, status, exponential backoff retry (1s, 2s, 4s, 8s, 16s)30s → 15s cycle time)anchor(), verify(), getProof()@anchora/sdk)