Introduction

ed25519 machine is a signer. It signs the messages it publishes with Ed25519, and we used it to deploy a memecoin.

The useful part is the signature. Anyone can claim a sentence came from the machine. Only a signature that verifies against the machine's public key actually did.

The machine

The machine holds an Ed25519 keypair. The public key names the machine. The secret key is what produces signatures, and it stays on the machine.

When the machine has something to say, it writes the message and signs that exact message. Publishing the words without the signature is not the same act.

The memecoin

We deployed a memecoin with this machine. The deployment is a message the machine signed: a memecoin is being deployed, and the signer is the ed25519 machine.

The coin is that signed deployment. This documentation does not add a mint address, a supply figure, or a price. Those belong in a message the machine signed, not in a paragraph someone typed beside it.

The coin page →

Ed25519

Ed25519 is a public-key signature scheme, the EdDSA construction on Curve25519 (the twisted Edwards curve edwards25519). It is widely used because signatures are short, verification is fast, and the scheme does not need a random number at signing time.

• A public key is 32 bytes. Share it. It is how verifiers name the signer.
• A signature is 64 bytes. It is attached to one message.
• The secret key is not part of the signature. Publishing a signature does not reveal it.
• The message itself is not encrypted. Signing proves origin and that the bytes were not changed. It does not hide the text.

Ed25519 is not a blockchain and not a token. The memecoin is a separate thing the machine deployed. Ed25519 is how you check that the machine is the one that deployed it.

Signing its own messages

"Signs its own messages" means the machine is both the author and the signer. It does not prepare a statement for a person to sign afterward, and a person does not sign a statement and then attribute it to the machine.

The sequence is:

1. The machine fixes the message bytes.
2. It computes an Ed25519 signature with its secret key.
3. It publishes the message, the signature, and the public key.

The memecoin deployment followed that sequence. The machine signed the deployment message.

Verifying a signature

A check needs the same three inputs the machine published:

1. The message bytes, unchanged.
2. The 64-byte signature.
3. The machine's 32-byte public key.

Verification returns yes or no. Yes means that public key signed that message. No means the message, the signature, or the key does not belong together. A single changed character is a no.

Use the public key the machine published for itself. A signature that verifies under some other key is a signature from someone else.

Solana wallet

The nav has a Connect wallet button for Phantom, Solflare, or Backpack. Connecting asks that wallet for its public address and shows a shortened form of it. Disconnect clears it in this browser.

That address is your wallet. It is not the machine's Ed25519 key. Connecting does not deploy a coin, does not sign a machine message, and does not send funds.

What this site will not do

• It will not ask you to deposit into a conversion or a shield form. Those are not part of this project.
• It will not print a mint address, a supply, or a price that the machine has not signed.
• It will not treat your connected wallet as the machine.

Questions