PairKey
Get started →DOCS / SIGNING SCHEMES
Signing schemes
PairKey targets chain-native signatures from one programmable authority. The destination selects a signature scheme and a separately derived public key; the two signers hold shares and produce one verifiable signature.
Target chain-to-scheme map
| Chain | Signing scheme | Derived key and intended use |
|---|---|---|
| Solana | FROST Ed25519 | Ed25519 public key for messages and Solana transaction signatures. |
| EVM | DKLS23 ECDSA · secp256k1 | Ethereum address for messages, typed data and EVM transactions. |
| Zcash | FROST RedPallas | Orchard SpendAuth verification key for Zcash spending authorization. |
| NEAR | FROST Ed25519 | NEAR-format Ed25519 public key for messages and transaction authorization. |
| Bitcoin | FROST secp256k1 · BIP-340 | X-only Schnorr public key for Taproot signing. |
These are the intended chain and scheme pairings, not a claim that every transaction format or production deployment is complete. See Security & status for current implementation and rollout boundaries.
Solana · FROST Ed25519
Two signers jointly produce a standard Ed25519 signature under a Solana public key. The target covers exact message bytes and canonical Solana transaction messages; programs and accounts can govern whether a request is authorized.
EVM · DKLS23 ECDSA
DKLS23 jointly produces a secp256k1 ECDSA signature whose public key maps to an Ethereum address. The target covers personal messages, typed data and chain-specific transaction payloads, with replay domains and chain IDs handled by the applicable format.
Zcash · FROST RedPallas
RedPallas is the signing scheme for Orchard SpendAuth. The target is authorization within a complete Zcash spending flow; a signing key alone is not a shielded address, note witness or transaction proof.
NEAR · FROST Ed25519
NEAR uses Ed25519 public keys for account access. PairKey derives a NEAR-specific key even though Solana uses the same signature scheme. The target includes messages and properly constructed NEAR transactions with the required account, nonce and permission context.
Bitcoin · FROST secp256k1
FROST secp256k1 produces BIP-340 Schnorr signatures for x-only Taproot keys. The target is BIP-341 transaction signing; message-signing formats require their own defined payload and verification rules.
From approval to chain use
An authority approves an exact request, both signers check the rules, and PairKey returns the derived key, signature and receipts. An application supplies the correct chain-specific payload and separately handles transaction construction, submission and confirmation. The interactive demo illustrates message signing; the target scheme map above also describes planned chain integrations.