Key Facts
- Category
- Security & Validation
- Input Types
- select, textarea
- Output Type
- json
- Sample Coverage
- 4
- API Ready
- Yes
Overview
The Ed25519 / X25519 Keygen and Signature Verifier allows you to generate secure cryptographic keypairs, sign messages, and verify signatures. You can generate Ed25519 keys for digital signatures or X25519 keys for Diffie-Hellman key agreement, using either random generation or a deterministic seed text, with output encoded in Base64 or Base58.
When to Use
- •When you need to generate Ed25519 keypairs for signing API requests or SSH authentication.
- •When you need to generate X25519 keypairs for secure key agreement protocols.
- •When you need to sign a message or verify an existing Ed25519 signature using Base64 or Base58 encoded keys.
How It Works
- •Select the operation (Generate, Sign, or Verify) and choose the algorithm (Ed25519 or X25519).
- •Choose your preferred encoding format, either Base64 or Base58.
- •Provide optional seed text for deterministic key generation, or input the required keys, message, and signature for signing and verification operations.
- •Run the tool to compute and output the cryptographic results in structured JSON format.
Use Cases
Examples
1. Generate Deterministic Ed25519 Keys
Security Engineer- Background
- A security engineer needs to generate a reproducible Ed25519 keypair for a CI/CD pipeline without storing the private key permanently.
- Problem
- Generating the exact same keypair on demand using a secure seed phrase.
- How to Use
- Set the operation to 'Generate', select 'Ed25519' as the algorithm, choose 'Base58' encoding, and enter the seed text.
- Example Config
-
Operation: Generate, Algorithm: Ed25519, Encoding: Base58, Seed Text: 'my team release signing seed 2026' - Outcome
- The tool outputs the deterministic public and secret keys in Base58 format.
2. Verify an Ed25519 Signature
API Developer- Background
- An API developer receives a webhook payload along with a Base64-encoded signature and needs to verify its authenticity.
- Problem
- Confirming that the payload was signed by the holder of the corresponding public key.
- How to Use
- Set the operation to 'Verify', select 'Ed25519' and 'Base64' encoding, then input the public key, the payload message, and the signature.
- Example Config
-
Operation: Verify, Algorithm: Ed25519, Encoding: Base64, Message: 'payload-data', Public Key: '...', Signature: '...' - Outcome
- The tool verifies the signature and returns a JSON response confirming whether the signature is valid.
Try with Samples
base64, textRelated Hubs
FAQ
What is the difference between Ed25519 and X25519?
Ed25519 is optimized for digital signatures, while X25519 is designed for Diffie-Hellman key agreement.
Can I sign messages using X25519?
No, message signing and verification operations in this tool are supported for Ed25519 only.
What does deterministic key generation mean?
It means the tool will always generate the exact same keypair when you provide the same seed text.
Which encodings are supported for the keys and signatures?
The tool supports Base64 and Base58 encodings for inputting and outputting keys and signatures.
Does this tool support BIP39 mnemonic phrases?
No, the seed text option uses a custom hashed input for deterministic generation, not the BIP39 standard.