import * as sr25519 from '@scure/sr25519';import { randomBytes } from '@noble/hashes/utils.js';const seed = randomBytes(32);const secretKey = sr25519.secretFromSeed(seed);const peerSecretKey = sr25519.secretFromSeed(randomBytes(32));const msg = new Uint8Array([1, 2, 3]);const signature = sr25519.sign(secretKey, msg);const publicKey = sr25519.getPublicKey(secretKey);const
HDKD
import * as sr25519 from '@scure/sr25519';import { randomBytes } from '@noble/hashes/utils.js';const seed = randomBytes(32);const cc = randomBytes(32);const parentSecret = sr25519.secretFromSeed(seed);const parentPublic = sr25519.getPublicKey(parentSecret);// hardconst hardSecret = sr25519.HDKD.secretHard(parentSecret, cc);const hardPublic = sr25519.getPublicKey(hardSecret);// softconst softSecret =
VRF
import * as sr25519 from '@scure/sr25519';import { randomBytes } from '@noble/hashes/utils.js';const seed = randomBytes(32);const msg = new Uint8Array([1, 2, 3]);const secretKey = sr25519.secretFromSeed(seed);const publicKey = sr25519.getPublicKey(secretKey);const signature = sr25519.vrf.sign(msg, secretKey);const isValid = sr25519.vrf.verify(msg, signature, publicKey);
Import schnorrkel / polkadot keypairs
fromKeypair() expects the 96-byte schnorrkel "half-Ed25519" layout:
secret.to_ed25519_bytes() || public.to_bytes().
This is the same format used by schnorrkel Keypair::to_half_ed25519_bytes().
The example below uses the same test vector shown in schnorrkel's
Keypair::from_half_ed25519_bytes() docs.
import * as sr25519 from '@scure/sr25519';import { hexToBytes } from '@noble/hashes/utils.js';const pair = hexToBytes( // secret.to_ed25519_bytes() '28b0ae221c6bb06856b287f60d7ea0d98552ea5a16db16956849aa371db3eb51' + 'fd190cce74df356432b410bd64682309d6dedb27c76845daf388557cbac3ca34' + // public.to_bytes() '46ebddef8cd9bb167dc30878d7113b7e168e6f0646beffd77d69d39bad76b47a');const normalized = sr25519.fromKeypair(pair);const publicKey = sr25519.getPublicKey(normalized.subarray(0, 64));
Merlin and Strobe
We implement only the parts of these protocols that sr25519 requires.
Migration from @polkadot/utils-crypto
most derive methods in original return {publicKey, privateKey}, we always return only privateKey,
you can get publicKey via getPublicKey
privateKey is 64 byte (instead of 32 byte in ed25519), this is because we need nonce and privateKey can be
derived from others (HDKD), and there would be no seed for that.
Security
The library has been audited:
at version 2.2.0, in Apr 2026, by ourselves (self-audited)
If you see anything unusual: investigate and report.
Low-level operations are done using noble-curves and noble-hashes.
Consult their README for more information about constant-timeness, memory dumping and supply chain security.
A few notes:
Bigints are used, which are not const-time, but our elliptic curve cryptography
implementation ensures algorithmic const-time for high-level items, which is more important
Secrets are zeroized, but this is pointless, since at some point they are converted to bigints,
and bigints cannot be zeroized in JS. Even zeroization of uint8arrays provides no guarantees.
Speed
Benchmark results on Apple M4:
secretFromSeed x 493,827 ops/sec @ 2μs/opgetSharedSecret x 1,135 ops/sec @ 880μs/opHDKD.secretHard x 54,121 ops/sec @ 18μs/opHDKD.secretSoft x 4,108 ops/sec @ 243μs/opHDKD.publicSoft x 4,499 ops/sec @ 222μs/opsign x 2,475 ops/sec @ 403μs/opverify x 955 ops/sec @ 1ms/opvrfSign x 442 ops/sec @ 2ms/opvrfVerify x 344 ops/sec @ 2ms/op
Comparison with wasm:
secretFromSeed wasm x 21,615 ops/sec @ 46μs/opgetSharedSecret wasm x 6,681 ops/sec @ 149μs/opHDKD.secretHard wasm x 16,958 ops/sec @ 58μs/opHDKD.secretSoft wasm x 16,075 ops/sec @ 62μs/opHDKD.publicSoft wasm x 16,981 ops/sec @ 58μs/opsign wasm x 16,559 ops/sec @ 60μs/opverify wasm x 6,741 ops/sec @ 148μs/opvrfSign wasm x 2,470 ops/sec @ 404μs/opvrfVerify wasm x 2,917 ops/sec @ 342μs/op