Discord signs timestamp concatenated with the raw request body. Your public key from the Developer Portal verifies the X-Signature-Ed25519 header.

Are my secrets uploaded?

No. Verification uses Web Crypto in your browser. Keys and bodies are not stored or transmitted to BlancoKit.

Why does verification fail?

Wrong public key, altered body whitespace, bad timestamp, or an invalid signature hex string. Use the exact raw body bytes your server received.

Bot developer

Verify Ed25519 interaction signatures locally.

Interaction signature

Verifies Ed25519 signatures locally in your browser. Keys and bodies are never sent to BlancoKit.

Application public key (hex)

Signature (hex)

Timestamp (Unix seconds)

Timestamp is 1792937624s from now. Discord may reject stale interactions.

Raw request body

0 UTF-8 bytes

Copy your application public key from the Discord Developer Portal.
Paste the X-Signature-Ed25519 hex, X-Signature-Timestamp, and the exact raw request body your server received.
Click Verify. Nothing is sent to BlancoKit. Web Crypto runs locally in your browser.

What gets verified?: Discord signs timestamp concatenated with the raw request body. Your public key from the Developer Portal verifies the X-Signature-Ed25519 header.
Are my secrets uploaded?: No. Verification uses Web Crypto in your browser. Keys and bodies are not stored or transmitted to BlancoKit.
Why does verification fail?: Wrong public key, altered body whitespace, bad timestamp, or an invalid signature hex string. Use the exact raw body bytes your server received.