EVM, Solana & Cosmos adapters.
Three ecosystems, one interface.
Eraivo's adapters translate one chain-agnostic interface into the native mechanics of EVM, Solana, and Cosmos, and a registry lets new chains join without breaking existing code.
Each adapter encapsulates the calldata format, signing scheme, fee model, and event shape of its ecosystem, then exposes them through the shared interface.
Application code stays the same; the adapter does the chain-specific work underneath.
Supported chains are registered, not hard-coded into application logic. Adding a chain is a registry change.
This keeps multi-chain coverage extensible without forcing integrators to refactor each time the ecosystem grows.
Which ecosystems are covered?
EVM, Solana, and Cosmos, through unified adapters.
How do adapters stay consistent?
They normalize calldata, signing, fees, and events to one interface so application code does not branch per chain.
Can new chains be added?
Yes, through the adapter registry without breaking existing integrations.