Skip to content

Commit e3a4986

Browse files
committed
fix: Document the default crypto algorithm in client libraries
1 parent 880eedf commit e3a4986

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/concepts/accounts/cryptographic-keys.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,8 @@ 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.
23+
2224

2325
## Key Components
2426

0 commit comments

Comments
 (0)