Client and backend. Every class listed here is shared: the same code is compiled into your app and into your server. The package's page in the client API lists all of it, including any classes that exist only in the app.

package com.codename1.crypto.rpc

Chain network clients: EvmRpc for Ethereum JSON-RPC, EsploraClient for the Bitcoin Esplora REST API and SolanaRpc for Solana JSON-RPC, all written against one RpcTransport. On the server that is WebRpcTransport, which sends through a WebClient and shares its connection pool. Calls block the handler’s thread until the node answers.

Types

`class EsploraClient`	A Bitcoin client for the Esplora REST API, which Blockstream and mempool.space run in public and anyone can self-host: unspent outputs, balances, fee estimates and broadcasting.
`class EvmRpc`	An Ethereum JSON-RPC client, for any EVM chain: balances, nonces, fees, gas estimates, calls, broadcasting and receipts.
`class JsonRpc`	JSON-RPC 2.0 over an `RpcTransport`: what Ethereum and Solana nodes speak.
`class RpcException`	A failure the remote end reported: an HTTP status outside 2xx, or a JSON-RPC error object.
`interface RpcTransport`	The one HTTP exchange every chain client needs: send a body, read the reply.
`class SolanaRpc`	A Solana JSON-RPC client: balances, the recent blockhash a transaction needs, rent, token balances, sending and confirmation.