ERPC

Run validators, RPC nodes and your own apps with ERPC CLI

ERPC CLI is one command line for RPC nodes on 18 chains, validators on 13, your own apps and your ERPC account. ERPC AI runs it for you when you ask.
This page describes ERPC CLI v0.1.0-rc.4, a pre-release (Status).
Install ERPC CLI Deploy your first app
bash
curl -fsSL https://install.erpc.global | sh

What you can do with ERPC CLI

  • Run validators and RPC nodes. erpc rpc runs RPC nodes on all 18 chains and erpc validator runs validators on 13 of them, with the same verbs on every chain. Their lifecycle commands are free and need no account.
  • Run your own app on a server. erpc worker compiles your app to a native Linux binary and runs it on an ERPC VPS or a server of your own, under a hardened systemd unit, with no Docker and no runtime in between.
  • Keep an app's keys off the server's disk. Its trading key and secrets go from 1Password, your keychain or erpc's encrypted keystore straight into the worker's memory. There is no wallet.json and no .env.
  • Ask ERPC AI. erpc ai answers from ERPC's documentation and your account. With your approval it can start an hourly VPS, install your SSH key, turn off password logins and allow SSH only from your address.
  • Call RPC and receive webhooks. erpc rpc call calls Solana or Ethereum mainnet with your signed-in account, or pays per call with x402. erpc webhook POSTs RPC events to your URL.
  • Store and back up files. erpc storage and erpc backup keep your files in ERPC Global Storage, encrypted on your machine before they leave it.

Install

On macOS and Linux:
bash
curl -fsSL https://install.erpc.global | sh
On Windows, in PowerShell:
powershell
irm https://install.erpc.global/ps1 | iex
These URLs select the latest stable release. While the project has only prereleases, they select the most recently published prerelease. To pin a version, use https://install.erpc.global/v0.1.0-rc.4, or https://install.erpc.global/v0.1.0-rc.4/ps1 on Windows. Edge and client caches may delay what clients see after a release.
The installer puts erpc in ~/.erpc/bin and writes ERPC AI's skills to ~/.erpc/skills. Builds are published for Linux (x86_64, arm64), macOS (Intel, Apple silicon) and Windows (x86_64).

Install for a mainnet validator

The installer above verifies nothing. The high-assurance path checks the signed release manifest before anything runs, and it is the only path that verifies anything today, so operators of mainnet validators should use it. Every release ships a signed release-manifest.json (minisign), a CycloneDX SBOM and GitHub build provenance attestations. The steps are in Verifying a release.

Build from source

bash
git clone https://github.com/elsoul/erpc-cli
cd erpc-cli
cargo build --release
./target/release/erpc --help

Free to start

Validator and RPC node lifecycle commands are free and need no account. An account at dashboard.erpc.global unlocks the rest:
CommandNo accountWith an account
Validator and RPC node lifecycleYesYes
erpc aiYes
erpc workerYes
erpc storage, erpc backupYes
bash
erpc signup     # opens the sign-up page
erpc login      # signs this machine in; the session goes to the keychain or 1Password
erpc whoami
Sign in and keys covers where the session and your keys are kept.

How ERPC CLI keeps your keys

ERPC CLI uses 1Password for node inventory and managed signing-key backups, and supports the operating system's keychain for operator credentials. API tokens and RPC keys are named in erpc.toml by reference, never by value, and the values reach the server over standard input, never on a command line.
The node inventory lives in 1Password too. Share the vault, and everyone on your team manages the same nodes from their own machine. What stays on a node server depends on the chain: Sign in and keys has the table.

Status

ERPC CLI is in pre-release, at v0.1.0-rc.4. Its commands exist and pass their offline checks. Acceptance on real hosts is still under way: Where each chain stands and each chain's guide give the state of each chain.
Only the latest release receives security fixes, and every release so far is a pre-release. Report a vulnerability privately through GitHub private vulnerability reporting, not in a public issue.
ERPC CLI is the Rust successor of SLV. Its source is at elsoul/erpc-cli under the Apache-2.0 license.

Explore ERPC CLI

  • Sign in and keys: Sign in, choose where the session is kept, and see where each key lives.
  • erpc ai: Ask ERPC AI in your terminal, and choose what it may do.
  • RPC and webhooks: Call Solana or Ethereum mainnet, pay per call with x402, and send events to your URL.
  • erpc worker quickstart: Make HelloWorld, run it here, and deploy it to a server.
  • Import an app: Deploy an app you already have without changing its code.
  • Keys and secrets: Keep an app's trading key and secrets in 1Password, the keychain or the keystore.
  • Firewall and WAF: Lock a server down and put a WAF in front of a public API.
  • Status and billing: Watch an app, see what it costs by the hour, and back up its state.
  • When it fails: Error messages and what to do, and how to recover a server.
  • Nodes: Run validators and RPC nodes, and find each chain's guide.
  • Commands: Every command group, global options, exit codes, storage and backups.
PreviousAI & agents / ERPC AI / FAQNextSign in and keys