RPC & compatibility

Both interfaces use the node’s canonical account state, but they are not interchangeable in every detail.

Concern	Ethereum interface	Legacy Tolar interface
Address representation	20-byte, 0x-prefixed	Historical 25-byte representation
Transaction submission	eth_sendRawTransaction	tx_sendSignedTransaction
Balance	eth_getBalance	tol_getLatestBalance, tol_getBalance
Nonce	eth_getTransactionCount	tol_getNonce
Block numbering	Native V2 sequence starting at 0	Continuous legacy-facing projection when an archive is committed
Events	eth_getLogs	tol_getPastEvents and related methods

Use documented conversion routines for legacy addresses; do not truncate strings or remove checksum bytes by guesswork.

Common read-only methods

web3_clientVersion, net_version, net_listening, eth_chainId, eth_blockNumber, eth_getBalance, eth_getCode, eth_getTransactionReceipt and eth_getLogs are useful starting points.

Network reporting also includes methods such as net_peerCount, net_masterNodeCount and net_isMasterNode. Their responses describe the queried node’s view.

Simulations deserve special care

The V2 compatibility implementation preserves V1 simulation behavior for tol_tryCallTransaction, tol_getGasEstimate and eth_call. These calls must not be treated as ordinary funded transaction admission.

In particular, the legacy-compatible eth_call failure convention differs from a standard Ethereum revert error. eth_estimateGas and the Tolar estimate method have distinct bounds and error behavior. Test success, revert and out-of-gas cases against your deployed endpoint.

Optional data and limits

Tracing, historical state and old receipts depend on node mode, retained data and configuration. An unavailable result is not permission to substitute the latest state.

Request examples

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_getBalance",
  "params": ["0x0000000000000000000000000000000000000000", "latest"]
}

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "eth_getTransactionCount",
  "params": ["0x0000000000000000000000000000000000000000", "pending"]
}

The zero address here is a valid read-only example, not an account to fund. Replace it with the account you need to inspect. Do not convert a legacy Tolar address by string slicing.

The public legacy JSON-RPC specification documents V1 formats. Use this guide for V2 differences and contact Tolar for release-specific operator/source access.