Elysia Tools
Navigation
Workflow Playbook
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.
Hubs
This workflow is for developers, security reviewers, and release writers who need a clear key-material record rather than a vague collection of crypto outputs. Decide first whether the deliverable is a BIP39 mnemonic or an asymmetric key pair. The three tools on this page support related tasks, but they do not establish an automatic mnemonic-to-key-pair derivation chain.
Use mnemonic-bip39-generator for a 12-to-24-word BIP39 phrase and its validation signals. Use key-pair-generator for the supported general RSA or ECC pair formats. Use ed25519-x25519-keygen-signature-verifier for modern curve material, signing, or verification. Select Ed25519 for signatures and X25519 for key agreement; do not force one operation onto the other.
Prepare a record template before running a tool. It should have a label, algorithm, encoding, public key, intended use, and review date. It must not have a private key, mnemonic, derived seed, or secret seed text. Treat generated secret material as sensitive: do not upload it, paste it into this article, or leave it in application and audit logs.
For a mnemonic, confirm the requested word count and checksum when validation is available. For a key pair, confirm that the selected tool returned the expected public and private components, then retain only the public component. If a signature check is part of the review, use matching Ed25519 inputs and keep X25519 on the key-agreement path.
The final acceptance check is procedural as well as cryptographic: the record contains only public material, the algorithm and encoding are unambiguous, failures were resolved rather than hidden, and a second reviewer can understand the result without seeing a secret. For token-specific concerns, see auth-token-security; for the broader signature and trust context, see key-generation-signature-verification.
Workflow playbook
Choose the mnemonic path, the general RSA/ECC key-pair path, or the Ed25519/X25519 path. Before running a tool, prepare the public-record fields and mark every private or seed value as excluded from uploads, articles, and logs.
Use the BIP39 tool only when a mnemonic is the intended artifact. Check the word count, checksum, entropy, and seed output as appropriate, but treat the mnemonic and derived seed as secrets that must not enter the public record.
For a general RSA or ECC pair, use the key-pair generator and select the required format. For modern curve material, use the Ed25519/X25519 tool with random or deliberately controlled deterministic input; keep the private half local and never copy it into documentation or logs.
Copy the public key, algorithm, encoding, label, and review date into the approved record. If a signature check is needed, use Ed25519 sign and verify with matching inputs; do not use X25519 as a signing operation, and do not retain private output in the record or telemetry.
Use the BIP39 tool when the artifact is a 12-to-24-word mnemonic that needs entropy or checksum validation. Use the key-pair or curve tool when the artifact must contain a public/private asymmetric pair; do not describe the mnemonic output as an automatically derived key pair.
Choose the general key-pair generator for supported RSA or ECC formats. Choose the Ed25519/X25519 tool for modern curve material: Ed25519 is the signing and verification path, while X25519 is for key agreement rather than message signing.
Record a stable label, algorithm, encoding, public key, and review date. Exclude private keys, mnemonic words, derived seeds, secret seed text, signatures that expose sensitive inputs, and any raw secret copied from a tool result.