Skip to main content
0xkey’s enclave supports multiple cryptographic curves. Chain-specific transaction construction, broadcast, and policy integration roll out per ecosystem.

​
Current support

​
Capability tiers

​
EVM

EVM is the primary Phase 1 integration path. Use @0xkey-io/viem or @0xkey-io/ethers to drop 0xkey signing into any EVM workflow. Broadcast must be performed by your own infrastructure today — 0xkey returns a signed transaction, not a transaction hash. → Ethereum integration guide

​
Solana

In-enclave parsing of legacy + V0 messages and Ed25519 signing are available, with policy contexts for solana.tx.*. Custodial sol_send_transaction (self-paid + fee sponsorship via sponsor: true) is Supported — platform fee-payer as account_keys[0], user as the second signer. → Solana guide · Sponsored Solana sends

​
Tron

In-enclave parsing of the Tron raw_data protobuf and secp256k1 signing are available, with policy contexts for tron.tx.* (including contract[0].* field-level conditions). Custodial tronSendTransaction builds, signs, broadcasts, and monitors both native TRX and TRC-20 transfers server-side; you can still construct and broadcast transactions client-side (e.g. with TronWeb) if you prefer. → Tron guide · Gasless Tron transactions

​
Other chains

For chains in the Address only row, the enclave can derive addresses and sign raw payloads, but it cannot parse the transaction or apply field-level policies. Build and serialize the transaction client-side, then call sign_raw_payload. There are no dedicated docs pages for these chains in Phase 1 — track the work on the Roadmap. → Roadmap — chain support