PairKeyDeveloper quickstart →

THE PROTOCOL, IN MOTION

Your rules. A real signature.

Choose your authority. Pick a chain. Watch two signers produce one verifiable signature.

MULTIPLE SOURCES MULTICHAIN SIGNING
Connecting to the backend…Checking the hosted v2 signing service.

ONE REQUEST. TWO SIGNERS.

Follow the signature.

LIVE BACKEND

Choose a message and follow its approval and signature.

AUTHORITY / SOLANA

Your Solana account

Authorizes the exact message and derived key.

Waiting

INDEPENDENT SIGNER / A

Waiting

Checks identity and current policy independently. Signs jointly with B.

Receipt pending

INDEPENDENT SIGNER / B

Waiting

Checks identity and current policy independently. Signs jointly with A.

Receipt pending

ASSEMBLE & VERIFY

One valid signature

Signing contributions combine. The full private key is never assembled.

Waiting

CHECK IT YOURSELF

Verify the signature.

Ask the service to recompute signature verification. Edit the message to test a mismatch; use the Rust verifier for independent receipt checks.

Public key & signature inputs

A completed signature will appear here.

USE YOUR SIGNATURE

Your application takes it from here.

Verify it off-chain, share it with a relying application, or use an appropriate chain-specific transaction flow. A message signature is not a transaction and does not need to be broadcast.

Separate key shares. Independent authorization checks. Joint threshold signing.

THE AUDIT TRAIL

Your next operation starts here.

Waiting for a request.

    Signature, signer receipts & chain evidence
    No result yet.

    Hosted v2 · Solana devnet control plane · Development signer processes · TEE deployment status →. Message signing only. FROST Ed25519 for Solana and NEAR, DKLS23 ECDSA for EVM, FROST RedPallas for Zcash, and FROST secp256k1 (BIP-340) for Bitcoin. These messages are not chain-native transactions or NEP-413 / Orchard / BIP-322 wallet formats.