> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xkey.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Networks overview

> Chains and cryptographic curves supported by 0xkey.

0xkey's enclave supports multiple cryptographic curves. Chain-specific transaction construction, broadcast, and policy integration roll out per ecosystem.

## Current support

| Ecosystem                                                                    | Status           | Notes                                                                                                                           |
| :--------------------------------------------------------------------------- | :--------------- | :------------------------------------------------------------------------------------------------------------------------------ |
| **EVM** — Ethereum, Polygon, Arbitrum, Base, Optimism, and compatible chains | **Supported**    | Phase 1 primary path; in-enclave parsing for legacy + type 1/2/3/4; `viem` and `ethers.js` integration                          |
| **Solana (SVM)**                                                             | **Partial**      | Ed25519 signing + in-enclave parsing for legacy + V0; on-chain broadcast (`sol_send_transaction`) is **Coming soon**            |
| **Bitcoin, Cosmos, Aptos, Sui, Tron, Sei, TON, XRP, Stellar, Doge**          | **Address only** | Address derivation works inside the enclave; signing via raw payload only; no in-enclave transaction parsing or policy contexts |
| **Stacks, Movement, IOTA, Hyperliquid, Tempo, Spark**                        | **Coming soon**  | No address derivation or parser yet                                                                                             |

## Capability tiers

| Tier                                    | Meaning                                                                                      | Status                                                                                                        |
| :-------------------------------------- | :------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------ |
| **L1 — Curve signing**                  | Sign a payload with a private key                                                            | **Supported** (secp256k1, P-256, Ed25519)                                                                     |
| **L2 — Address derivation**             | Derive addresses from `addressFormat`                                                        | **Supported** for all listed chains in the table above                                                        |
| **L3 — In-enclave transaction parsing** | Parse the unsigned tx inside the enclave so the policy engine sees fields                    | **Supported** for EVM and Solana, plus EIP-712; **Coming soon** for everything else                           |
| **L4 — Fine-grained policy contexts**   | Apply CEL policy conditions on parsed fields (e.g. `eth.tx.to`, `solana.tx.instructions[*]`) | **Supported** for EVM + Solana + EIP-712; **Coming soon** elsewhere                                           |
| **L5 — On-chain broadcast**             | Submit the signed transaction to a chain RPC                                                 | **Coming soon** (Phase 1 ships a mock for `eth_send_raw_transaction`; high-level send activities error today) |

## 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](/networks/ethereum)

## Solana

In-enclave parsing of legacy + V0 messages and Ed25519 signing are available, with policy contexts for `solana.tx.*`. The high-level `sol_send_transaction` broadcast activity is not wired yet.

→ [Solana guide](/networks/solana)

## 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](/0xkey/roadmap).

→ [Roadmap — chain support](/0xkey/roadmap)