Package com.codename1.crypto.rpc


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. In an application that is NetworkTransport, over the NetworkManager; the backend has its own over its WebClient. Calls block; from the EDT they wait with invokeAndBlock.
  • Class
    Description
    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.
    An unspent output.
    An Ethereum JSON-RPC client, for any EVM chain: balances, nonces, fees, gas estimates, calls, broadcasting and receipts.
    JSON-RPC 2.0 over an RpcTransport: what Ethereum and Solana nodes speak.
    The application's RpcTransport: each request goes through the NetworkManager queue as a ConnectionRequest, waiting with addToQueueAndWait, so a call from the EDT keeps the UI responsive.
    A failure the remote end reported: an HTTP status outside 2xx, or a JSON-RPC error object.
    The one HTTP exchange every chain client needs: send a body, read the reply.
    A Solana JSON-RPC client: balances, the recent blockhash a transaction needs, rent, token balances, sending and confirmation.