Skip to content

Commit b4d3ae2

Browse files
committed
tiny docs fixes
1 parent cb08b88 commit b4d3ae2

File tree

1 file changed

+11
-3
lines changed

1 file changed

+11
-3
lines changed

docs/docs/streamr-network/security/quantum-security.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,21 +17,29 @@ To activate the whole quantum secure stack, simply configure ML-DSA identities o
1717
```
1818
const streamr = new StreamrClient({
1919
auth: {
20-
publicKey: '...', // hex encoded ml-kem-87 public key
21-
privateKey: '...', // hex encoded ml-kem-87 private key
20+
publicKey: '...', // hex encoded ML-DSA-87 public key
21+
privateKey: '...', // hex encoded ML-DSA-87 private key
2222
keyType: 'ML_DSA_87'
2323
}
2424
})
2525
```
2626

2727
## Generating ML-DSA keys
2828

29-
To generate ML-DSA keys, see `MLDSAKeyPair.generate()` or use CLI tool:
29+
You can generate the ML-DSA-87 keys using a suitable tool or library of your choice, or use tooling available on Streamr. For example, using the Streamr CLI tool:
3030

3131
```
3232
streamr identity generate --key-type ML_DSA_87
3333
```
3434

35+
Or programmatically using the `MLDSAKeyPairIdentity` class that ships with the Streamr SDK:
36+
37+
```
38+
const identity = MLDSAKeyPairIdentity.generate()
39+
const publicKey = await identity.getUserId()
40+
const privateKey = await identity.getPrivateKey()
41+
```
42+
3543
## Enforcing quantum security
3644

3745
In order to tighten up the quantum security and refuse the use of any non-quantum algorithms, you may additionally set the following configuration:

0 commit comments

Comments
 (0)