Skip to content

Commit 070e688

Browse files
authored
Revise algo note
1 parent e3a4986 commit 070e688

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/concepts/accounts/cryptographic-keys.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ To make a digital signature, you use a cryptographic key pair associated with th
1919

2020
Many [client libraries](../../references/client-libraries.md) and applications can generate a key pair suitable for use with the XRP Ledger. However, you should only use key pairs that were generated with devices and software you trust. Compromised applications can expose your secret to malicious users who can then send transactions from your account later.
2121

22-
Note: Client libraries (xrpl-py, xrpl.js) and the `rippled` CLI's [wallet_propose](../../references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose) admin RPC command can be used to generate keys. Client libraries use `ED25519` as the default cryptographic algorithm, whereas the rippled CLI uses `SECP256K1` as the default algorithm.
22+
Note: Different tools have different defaults. Many client libraries (such as xrpl.js) use Ed25519 as the default cryptographic algorithm, but `rippled`'s [wallet_propose](../../references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose) admin RPC command uses secp256k1 as the default. This means that you may get a different address if you instantiate a wallet from the same seed using a different tool, unless you specify the algorithm explicitly.
2323

2424

2525
## Key Components

0 commit comments

Comments
 (0)