Skip to main content

JSON-RPC reference

PressChain V3 exposes an Ethereum-compatible JSON-RPC interface. Existing EVM tooling can perform network reads, contract calls, log queries and signed transaction submission when configured for the PressChain network. Canonical public testnet endpoint:
Current Chain ID:
Hexadecimal Chain ID:

Request format

Requests are sent with HTTP POST and content-type: application/json.

Verify chain identity

A V3 testnet client should expect 0x498B64A, allowing for case differences in hex output.

Current block

The result is a hexadecimal quantity. Convert with a bigint-capable parser when the value is used programmatically.

Read a transaction receipt

A null result can mean the transaction is not yet included or is unknown to that node. That is different from a receipt whose status indicates execution failure.

Read contract state

Use eth_call with encoded ABI data:
Use an ABI library rather than hand-encoding selectors unless you are building low-level tooling.

Methods commonly used by applications

Observability

Log RPC method, duration, endpoint class and error code. Do not log private keys, seed phrases or sensitive signing material. For submitted transactions, persist the transaction hash as soon as it is known. If a browser times out afterward, the hash gives the application a recovery path without creating a duplicate write.

Scaling reads

RPC is excellent for authoritative reads and verification. High-volume search, sorting and aggregation belong in an indexer or projection layer. A good PressChain application uses both: projections for product speed, RPC and contracts for authority.