curl -H "Content-Type: application/json" \
-d '{"id":1, "jsonrpc":"2.0", "method": "system_syncState", "params":[]}' \
http://localhost:9944
{
"jsonrpc":"2.0",
"id":1,
"result":{
"startingBlock":0,
"currentBlock":3394816,
"highestBlock":3394816
}
}
!!! tip
You can use the `system_health` command to verify your node is running properly.
```bash
curl -H "Content-Type: application/json" \
-d '{"id":1, "jsonrpc":"2.0", "method": "system_health", "params":[]}' \
http://localhost:9944
```
## Commands for Managing Your Node
Use the following commands to manage your node:
=== "Docker"
- **View node logs**:
```bash
docker logs -f polkadot-hub-rpc
```
- **Stop container**:
```bash
docker stop polkadot-hub-rpc
```
- **Start container**:
```bash
docker start polkadot-hub-rpc
```
- **Remove container**:
```bash
docker rm polkadot-hub-rpc
```
=== "systemd"
- **Check status**:
```bash
sudo systemctl status polkadot-hub-rpc
```
- **View node logs**:
```bash
sudo journalctl -u polkadot-hub-rpc -f
```
- **Stop service**:
```bash
sudo systemctl stop polkadot-hub-rpc
```
- **Enable service**:
```bash
sudo systemctl enable polkadot-hub-rpc
```
- **Start service**:
```bash
sudo systemctl start polkadot-hub-rpc
```
## Ethereum RPC Compatibility
!!! note
Ethereum RPC compatibility is supported only on some chains, such as Polkadot Hub.
Ethereum RPC compatibility is provided through the `eth-rpc` adapter, which is part of [pallet-revive](https://paritytech.github.io/polkadot-sdk/master/pallet_revive_eth_rpc/index.html). This adapter translates Ethereum JSON-RPC calls into Polkadot SDK-compatible requests, enabling integration with Ethereum tools like [MetaMask](https://metamask.io/), [Hardhat](https://hardhat.org/), and [Ethers.js](https://docs.ethers.org/v6/).
### Prerequisites
Before starting the Ethereum RPC adapter:
- **Node synchronization**: Let your Polkadot Hub node finish syncing before you start the adapter. On startup, the `eth-rpc` adapter reads `pallet-revive` configuration from the node's latest block and fails to start if that block predates `pallet-revive`, for example, early in the initial sync.
- **Archive node recommended**: For full Ethereum RPC compatibility, run an archive node (`--state-pruning=archive`). The `eth-rpc` adapter may fail to query historical state on pruned nodes.
- **RPC accessibility**: The Polkadot SDK-based RPC endpoint must be accessible (default: `ws://127.0.0.1:9944`).
### Run the Ethereum RPC Adapter
You can run the Ethereum RPC adapter using Docker or as a systemd service.
=== "Docker"
Start the adapter using the official [Parity eth-rpc Docker image](https://hub.docker.com/r/parity/eth-rpc/tags):
```bash
docker run -d --name eth-rpc --restart unless-stopped \
--network=host \
-v /var/lib/eth-rpc:/data \
parity/eth-rpc:stable2609 \
--node-rpc-url=ws://127.0.0.1:9944 \
--rpc-port=8545 \
--base-path=/data \
--rpc-external \
--rpc-cors=all
```
!!! note
The `-v` flag maps the host directory `/var/lib/eth-rpc` to `/data` inside the container. The `--base-path` flag references this container path to persist the `eth-rpc.db` database across restarts.
!!! note
Check the [Docker Hub tags page](https://hub.docker.com/r/parity/eth-rpc/tags) for newer releases. Tags follow the Polkadot SDK release naming, such as `stable2609`.
=== "systemd"
1. Build the `eth-rpc` binary from the Polkadot SDK source:
```bash
git clone --branch polkadot-stable2609 --depth 1 https://github.com/paritytech/polkadot-sdk.git
cd polkadot-sdk
cargo build -p pallet-revive-eth-rpc --bin eth-rpc --release
# Move to system path
sudo mv target/release/eth-rpc /usr/local/bin/
```
!!! note
Pre-built binaries may not be available for all platforms. Building from source ensures compatibility with your system.
2. Create a systemd service file:
```bash
sudo nano /etc/systemd/system/eth-rpc.service
```
3. Add the following configuration:
```ini
[Unit]
Description=Ethereum RPC Adapter for Polkadot Hub
After=network.target polkadot-hub-rpc.service
[Service]
Type=simple
User=polkadot
Group=polkadot
ExecStart=/usr/local/bin/eth-rpc \
--node-rpc-url=ws://127.0.0.1:9944 \
--rpc-port=8545 \
--base-path=/var/lib/eth-rpc \
--rpc-external \
--rpc-cors=all
Restart=always
RestartSec=10
[Install]
WantedBy=multi-user.target
```
!!! warning
The `--rpc-external` flag exposes your RPC endpoint publicly. For production deployments, consider using a reverse proxy with authentication and rate limiting, or bind to a specific interface.
4. Start the service:
```bash
sudo systemctl daemon-reload
sudo systemctl enable eth-rpc
sudo systemctl start eth-rpc
```
### Ethereum RPC Configuration
The adapter accepts the following key parameters:
| Parameter | Description | Default |
|:---------:|:-----------:|:-------:|
| `--node-rpc-url` | Polkadot SDK-based node WebSocket URL | `ws://127.0.0.1:9944` |
| `--rpc-port` | Ethereum RPC server port | `8545` |
| `--rpc-external` | Listen for RPC connections on all network interfaces instead of only on `localhost` | Disabled |
| `--rpc-cors` | CORS allowed origins | None |
| `--eth-pruning` | Block storage strategy: `archive` for persistent on-disk DB with full historical sync, or `