NEVM JSON-RPC
NEVM exposes Ethereum JSON-RPC for accounts, contracts, logs and transaction receipts. The public endpoints below accept reads without a wallet or API key.
Endpoints and wallet settings
| Network | Chain ID | Native currency | Public RPC | Explorer and wallet discovery |
|---|---|---|---|---|
| Syscoin NEVM mainnet | 57 · 0x39 | SYS | rpc.syscoin.org | Block explorer · Chainlist |
| Tanenbaum NEVM testnet | 5700 · 0x1644 | tSYS | rpc.tanenbaum.io | Block explorer · Chainlist |
Choose Tanenbaum to deploy a first contract. A wallet can import the network from Chainlist or use the values above. Test accounts can request gas through the community’s Syscoin NEVM Testnet faucet. Pali and MetaMask setup · Tanenbaum faucet instructions
For an application on a zkSYS Edgechain, connect to Genesis testnet at rpc-zk.tanenbaum.io, chain ID 57057 (0xdee1). Chainlist lists it as zkTanenbaum Testnet. Genesis has a separate faucet, explorer and batch RPCs. Genesis commands and settings · Genesis on Chainlist · Genesis faucet
Read the chain
This batch returns the chain ID and current block height. Match the results by request ID. On Tanenbaum, request 1 returns 0x1644 and request 2 returns the height in hexadecimal.
RPC=https://rpc.tanenbaum.io
curl -fsS "$RPC" -H 'Content-Type: application/json' --data '[
{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]},
{"jsonrpc":"2.0","id":2,"method":"eth_blockNumber","params":[]}
]'
| Task | JSON-RPC method | Parameters |
|---|---|---|
| Read a public address’s native SYS balance (wei) | eth_getBalance | ["0x…address", "latest"] |
| Read a contract view | eth_call | [{"to":"0x…contract","data":"0x…ABI_encoded_call"}, "latest"] |
| Read a transaction’s outcome and event logs | eth_getTransactionReceipt | ["0x…transaction_hash"] |
| Fetch a block with transaction hashes | eth_getBlockByNumber | ["latest", false] |
Replace the abbreviated addresses and hashes with their full hex values. A transaction receipt supplies blockHash, status and logs once the transaction is mined. For UTXO balances, outputs and SPT transfers use Blockbook REST or Syscoin Core RPC.
For deployment, use Foundry or Hardhat. For the managed client and its version pairing, see Syscoin Geth. For general method semantics, see the Ethereum JSON-RPC reference.