> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tavchain.safeney.com/llms.txt
> Use this file to discover all available pages before exploring further.

# JSON-RPC response formats

> Interpret Tavchain JSON-RPC results, errors, hexadecimal quantities, addresses, byte data and receipt execution status.

Tavchain's Ethereum JSON-RPC endpoint uses JSON-RPC 2.0. Each response identifies the request by `id` and contains either `result` or `error`.

## Successful response

```json theme={null}
{"jsonrpc":"2.0","id":1,"result":"0xbc3ba"}
```

## Field formats

| Value | Representation |
| - | - |
| Balance, nonce, gas or block number | A `0x`-prefixed hexadecimal quantity; zero is `0x0`. |
| EVM address | `0x` followed by 40 hexadecimal characters. |
| Transaction or block hash | `0x` followed by 64 hexadecimal characters. |
| Bytes or calldata | `0x`-prefixed hexadecimal data. |
| Receipt not available | JSON `null`. |

Use integer-safe parsing for quantities. Native balances use `atav`, with **10^18 atav per TAV**. Contract return data is ABI-encoded and must be decoded according to the contract's ABI.

## Errors and execution status

Inspect the JSON-RPC `error` object separately from the HTTP status. HTTP 429, HTTP 503 and connection failures can occur before a JSON-RPC response is returned.

Receipt status `0x1` means execution succeeded; `0x0` means execution failed. A successful HTTP request does not imply a successful contract transaction.

[RPC limits](https://docs.tavchain.safeney.com/tavchain/http-api.md) · [Receipts](https://docs.tavchain.safeney.com/tavchain/api/transaction.md) · [Troubleshooting](https://docs.tavchain.safeney.com/tavchain/troubleshooting.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.