Vilna's products cover different sets of networks. The Platform API covers 9 of them; the Blockchain RPC proxies 11. The VKS column shows signing support, including mainnet and test networks.
11 networks 7 with full monitoring RPC on every one
| Network | CAIP-2 id | Platform API | Blockchain RPC | VKS signing | RPC alias |
|---|---|---|---|---|---|
| Ethereum Mainnet | eip155:1 | Full | JSON-RPC | Supported | ethereum |
| Ethereum Sepolia | eip155:11155111 | Full | JSON-RPC | Supported | sepolia |
| Ethereum Hoodi | eip155:560048 | - | JSON-RPC | Supported | hoodi |
| BNB Smart Chain | eip155:56 | Full | JSON-RPC | Supported | bsc |
| BNB Smart Chain Testnet | eip155:97 | - | JSON-RPC | Supported | bsc-testnet |
| Bitcoin Mainnet | bip122:000000000019d6689c085ae165831e93 | Full | JSON-RPC | Supported | bitcoin |
| Bitcoin Testnet4 | bip122:00000000da84f2bafbbc53dee25a72ae | Full | JSON-RPC | Supported | bitcoin-testnet |
| Tron Mainnet | tron:728126428 | Full | gRPC | Supported | tron |
| Tron Nile | tron:3448148188 | Full | gRPC | Supported | tron-testnet |
| Solana Mainnet | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp | Addresses and token catalog | JSON-RPC | - | solana |
| Solana Testnet | solana:4uhcVJyU9pJkvQyS88uRDiswHXSCkY3z | Addresses and token catalog | JSON-RPC | - | solana-testnet |
Platform API. Full means addresses, transactions, activity, balances, the token catalog and notifications, through the Platform API. Transaction simulation is EVM-only, so it applies to the three eip155 rows marked Full (Ethereum Mainnet, Ethereum Sepolia and BNB Smart Chain). Addresses and token catalog means the network accepts address registration and resolves tokens; balances, transactions, notifications and simulation are not available. A dash means the network is not available in the Platform API at all. GET /blockchains returns the live list.
Blockchain RPC. The protocol for node requests is JSON-RPC over HTTPS for EVM, Bitcoin and Solana, or gRPC for Tron. Use the table's CAIP-2 id or alias in the HTTP path for JSON-RPC, or in x-chain-id metadata for gRPC. GET /chains lists current routes; a listed route alone does not establish node availability.
Alongside the CAIP-2 ids and aliases, RPC accepts tron:mainnet, tron:testnet, solana:mainnet and solana:testnet. Use gRPC for Tron node queries.
Testnets are there for development. For a chain that is not listed, write to support@vilna.io.
VKS supports mainnet and test networks. Signing requires an account format compatible with the selected network and signing nodes that support the required method.
- EVM: accounts with the
evmformat support signing foreip155networks, including mainnet and test networks. - Tron: the
tronformat supports Mainnet, Nile and Shasta. - Bitcoin:
p2wpkhandp2sh(P2SH-P2WPKH) support mainnet. Their-testnetvariants support testnet3, testnet4 and signet. The account format must match the network. - Solana: signing is not currently supported. Other values in the shared address-format enum do not by themselves establish signing support.
Signing and sending are separate steps. A signed transaction can be submitted through VKS where sending is available for the chosen network, or through a blockchain node. Node acceptance is not blockchain confirmation. See VKS.