# Key Material Generation and Public-Key Recording

Generate or validate a BIP39 mnemonic or create an asymmetric key pair, then record only public material while keeping private material out of uploads, articles, and logs.

> Canonical page: https://elysiatools.com/en/hubs/key-material-generation-and-recording

- **Keywords:** BIP39 mnemonic generation, asymmetric key pair, public key record, private key handling, Ed25519 X25519

## Frequently asked questions

### Should I run the mnemonic generator and a key-pair generator together?

Only when the project needs two separate artifacts. The BIP39 tool creates or validates a mnemonic and seed-related output; the key tools create asymmetric material. This workflow does not claim that the tools derive the same key pair from the same phrase.

### Can I paste the private key or mnemonic into the article or an application log?

No. Keep private keys, mnemonic words, derived seeds, and secret seed text outside uploads, articles, and logs. Record only the public key and non-secret metadata in the approved public record.

### When should I choose Ed25519 instead of X25519?

Choose Ed25519 for signing and signature verification. Choose X25519 for key agreement. The curve tool rejects signing or signature verification when the selected algorithm is X25519.

### What should I do when validation or generation fails?

Do not record the result. Recheck the BIP39 word count and checksum, or align the selected algorithm, operation, encoding, and key input. Repeat with non-production material and investigate any secret that may have reached a log before continuing.

## Related content

- [Credential and JWT Security Workflow](https://elysiatools.com/en/hubs/auth-token-security): Generate or validate password credentials and inspect JWT security signals without treating key pairs as passwords.