Solana compatibility
What deploys unchanged, and what is different on Kyvro.
TestnetVerified Oct 15, 2026
On this page
Build target#
Kyvro runs unmodified Agave, so it is a Solana-compatible SVM: build with the standard Solana toolchain (Rust SBF or Anchor) and deploy the same bytecode. Existing Anchor and SPL programs deploy unchanged — only the RPC URL, cluster identity, program IDs and explorer links change.
No chain ID, ever
Kyvro is identified by its genesis hash, not a number. If a library demands a numeric chain ID, that is a bug to route around — never a value to invent.What works#
| Feature | Supported |
|---|---|
| Anchor programs, deployed unchanged | Yes |
| SPL Token, Token-2022, Associated Token Account and Memo at their Solana addresses | Yes |
| Solana CLI, SPL Token CLI, web3.js and Kit against the Kyvro RPC | Yes |
Standard RPC methods (getSlot, getBlock, getTransaction, getAccountInfo, simulateTransaction…) | Yes |
| Upgradeable programs with transparent upgrade authorities | Yes |
| EVM tooling (Solidity, Foundry, Hardhat, ethers, MetaMask-style setup) | No |
The requestAirdrop RPC method | No |
| Gossip with Solana clusters (by design — Kyvro is its own network) | No |
EVM-style debug_* / trace_* methods | No |
| Oracles, bridges and price feeds | No |
Caveats#
- Test tokens come from the faucet only.
requestAirdropandsolana airdropare disabled — see test tokens and faucet. - Simulate, then read the explorer. Without trace APIs, preview transactions with
simulateTransactionand debug from program logs on the explorer. - Single validator. Finality follows one validator, and restarts halt the chain — see slots and commitment.
- tKUSD is not USDC. Same 6 decimals, but no issuer, no backing, no dollar value. Identify tokens by mint address, never by symbol.
Something wrong or missing on this page? Send developer feedback.