Overview

The RPC server uses JSON-RPC 2.0 to facilitate communication between the Porto SDK and the blockchain. The RPC is responsible for building, simulating and sending intents to the contracts on behalf of a user.

Execution is paid for in one of the fee tokens accepted by the RPC on a given network. You can get the supported fee tokens for a chain by querying wallet_getCapabilities.

The RPC server has passthrough to a standard Ethereum node.

Endpoints

The RPC server has multiple endpoints, one for each chain/environment.

Each endpoint has passthrough to Ethereum RPCs for the corresponding network.

Local Development

To run the RPC Server locally, you can use the following command:

curl -sSL s.porto.sh/docker | docker compose -f - up -d

Once complete, the RPC Server will be available at http://localhost:9200:

cast block-number --rpc-url http://localhost:9200
cast rpc --rpc-url http://localhost:9200 wallet_getCapabilities "[31337]"

Account management

Accounts are managed through the RPC using the following methods:

Account creation

In order to facilitate account discovery, account creation is split into two steps:

• wallet_prepareCreateAccount: Generate an account and a corresponding address.
• wallet_createAccount: Create the account on chain.

Accounts are created using PREP, which proves that neither the RPC server nor the user knows the underlying private key for the EOA.

wallet_prepareCreateAccount also returns a series of digests that must be signed with the admin keys of the account. These signatures are used to register the key and account in an on-chain registry, allowing users to discover their accounts using their keys later on.

Account upgrade

Upgrading an existing EOA is split into two steps:

• wallet_prepareUpgradeAccount: Prepares an account for upgrade.
• wallet_upgradeAccount: Upgrades the account on chain.

Account information

• wallet_getKeys: Get all keys attached to an account.
• wallet_getAccounts: Get all accounts a key is attached to.

For more details on how accounts work, see the Account documentation.

Intent execution

Intents are executed in two steps. First, wallet_prepareCalls is called to simulate the call and estimate fees. A context is returned with the built intent, which also includes a quote signed by the RPC server, which expires after some time. The built intent is verified and signed by the user's key, and the quote plus the signed intent is sent to the RPC server with wallet_sendPreparedCalls.

The RPC server will validate that the quote is still valid, that the intent was signed, and will then include it in a transaction on the destination chain. wallet_sendPreparedCalls returns an opaque identifier that is the equivalent of a transaction hash. To get the status of an intent, plus any transaction receipts for the intent, you must use wallet_getCallsStatus.

Passthrough

The RPC server passes through known Ethereum JSON-RPC methods to an underlying network of nodes for the corresponding chain. For example, you can query the block number or chain ID:

cast chain-id --rpc-url https://base-sepolia.rpc.ithaca.xyz
 
# 84532

cast block-number --rpc-url https://base-sepolia.rpc.ithaca.xyz
 
# 30568194