Ed25519 / X25519 Keygen and Signature Verifier

Generate Ed25519 or X25519 keypairs from random or deterministic seed text, then sign or verify messages

This tool is built for modern key workflows. Generate Ed25519 keys for signatures, X25519 keys for key agreement, use random generation or deterministic seed text, and work in base64 or base58. Message signing and verification use Ed25519 only.

Example Results

1 examples

Generate deterministic Ed25519 keys from seed text

Use memorable private seed text to get the same Ed25519 keypair again later, then share the public key in base58 or base64

{
  "result": {
    "algorithm": "ed25519",
    "seedSource": "deterministic"
  }
}
View input parameters
{ "operation": "generate", "algorithm": "ed25519", "encoding": "base58", "seedText": "my team release signing seed 2026" }

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

Generating deterministic Ed25519 keypairs from a custom seed phrase for reproducible deployments.
Signing API payloads or configuration files using an Ed25519 secret key.
Verifying the authenticity of a received message against a public key and signature.

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, text

Related 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.

API Documentation

Request Endpoint

POST /en/api/tools/ed25519-x25519-keygen-signature-verifier

Request Parameters

Parameter Name Type Required Description
operation select Yes -
algorithm select Yes -
encoding select Yes -
seedText textarea No -
message textarea No -
secretKey textarea No -
publicKey textarea No -
signature textarea No -

Response Format

{
  "key": {...},
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}
JSON Data: JSON Data

AI MCP Documentation

Add this tool to your MCP server configuration:

{
  "mcpServers": {
    "elysiatools-ed25519-x25519-keygen-signature-verifier": {
      "name": "ed25519-x25519-keygen-signature-verifier",
      "description": "Generate Ed25519 or X25519 keypairs from random or deterministic seed text, then sign or verify messages",
      "baseUrl": "https://elysiatools.com/mcp/sse?toolId=ed25519-x25519-keygen-signature-verifier",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

You can chain multiple tools, e.g.: `https://elysiatools.com/mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp`, max 20 tools.

If you encounter any issues, please contact us at [email protected]