> For the complete documentation index, see [llms.txt](https://docs.tajirchain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tajirchain.com/developers/network-connection-guide/exchange-and-payment-integration.md).

# Exchange & Payment Integration

This page provides the technical information required by exchanges, payment gateways, wallets, custodians, and infrastructure providers integrating Tajir Chain and its native TJR asset.

### Network Configuration

<table data-search="false"><thead><tr><th>Parameter</th><th>Value</th></tr></thead><tbody><tr><td>Network Name</td><td>Tajir Chain</td></tr><tr><td>Network Type</td><td>EVM-compatible Layer 2</td></tr><tr><td>Chain ID</td><td>3377</td></tr><tr><td>Chain ID in Hex</td><td>0xd31</td></tr><tr><td>Native Asset</td><td>TJR</td></tr><tr><td>Decimals</td><td>18</td></tr><tr><td>Address Format</td><td>Standard 20-byte EVM address</td></tr><tr><td>Address Prefix</td><td>0x</td></tr><tr><td>Memo or Destination Tag</td><td>Not required</td></tr><tr><td>Average Block Time</td><td>Approximately 2 seconds</td></tr><tr><td>Mainnet RPC</td><td><a href="https://rpc.tajirchain.com/">https://rpc.tajirchain.com</a></td></tr><tr><td>Explorer</td><td><a href="https://explorer.tajirchain.com/">https://explorer.tajirchain.com</a></td></tr><tr><td>Explorer API</td><td><a href="https://explorer.tajirchain.com/api-docs">https://explorer.tajirchain.com/api-docs</a></td></tr><tr><td>Mainnet Bridge</td><td><a href="https://bridge.tajirchain.com/">https://bridge.tajirchain.com</a></td></tr></tbody></table>

### Asset Model

TJR is the native currency of Tajir Chain. It is not an ERC-20 contract on Tajir Chain.

Integrators should:

* Treat TJR as the native coin of Chain ID 3377.
* Monitor native transfers through transaction `value`.
* Use standard Ethereum-compatible address validation.
* Use 18 decimal places.
* Maintain sufficient TJR in operational wallets to pay network fees.
* Avoid requesting an L2 TJR contract address because no separate ERC-20 contract exists on Tajir Chain.

The canonical Ethereum Mainnet ERC-20 proxy address is:

`0x9D98C61d1136cfA2ac263Be355350C97Ca41c110`

### Deposit Monitoring

Integration systems can use standard Ethereum JSON-RPC methods:

* `eth_blockNumber`
* `eth_getBlockByNumber`
* `eth_getTransactionByHash`
* `eth_getTransactionReceipt`
* `eth_getBalance`
* `eth_getTransactionCount`
* `eth_getLogs`

A successful transaction receipt returns:

```json
{
  "status": "0x1"
}
```

Integrators should verify:

1. The destination address
2. The transferred native `value`
3. The transaction receipt status
4. The block number
5. The configured number of confirmations
6. That the transaction remains in the canonical chain

The final production confirmation threshold should be agreed during technical onboarding and integration testing. Sequencer inclusion should not automatically be treated as complete L1 settlement.

### Withdrawals

TJR withdrawals are standard EVM native-asset transactions.

Integrators should:

1. Validate the destination address.
2. Estimate gas using `eth_estimateGas`.
3. Obtain current fee data using `eth_gasPrice` or supported EIP-1559 methods.
4. Keep enough TJR available for network fees.
5. Sign the transaction securely.
6. Broadcast using `eth_sendRawTransaction`.
7. Confirm success using `eth_getTransactionReceipt`.

### RPC Access

The public RPC is suitable for standard integration and testing:

`https://rpc.tajirchain.com`

High-volume exchanges and payment providers should request dedicated or authenticated RPC access to obtain stable throughput, controlled rate limits, and operational support.

### Node and Chain Configuration

Canonical mainnet files are available from:

<https://github.com/Tajir-Chain/tajir-chain-registry>

The registry contains:

* Mainnet genesis configuration
* Rollup configuration
* Deployed L1 and L2 contract addresses
* SHA-256 checksums
* Network metadata
* Node initialization instructions
* Token ABI
* Deployment provenance

### Integration Testing

Before enabling customer deposits and withdrawals, integration partners should complete:

* RPC connectivity testing
* Chain ID validation
* Native TJR deposit testing
* Native TJR withdrawal testing
* Gas estimation testing
* Transaction-status testing
* Confirmation and finality testing
* Service interruption and retry testing
* Bridge testing, where required