Skip to main content
This section is for exchanges, custodians and payment processors adding LAX, the native coin of Parallax. It covers running your own nodes, crediting deposits, sending withdrawals, and deciding how many confirmations a deposit needs. Parallax is a proof-of-work chain that runs the Ethereum Virtual Machine. If you already support Ethereum or an Ethereum Classic-style chain, most of your tooling works unchanged: the same addresses, the same JSON-RPC, the same transaction format and signing libraries. What changes is the part that matters most to an exchange, settlement: blocks come every 10 minutes, no block is ever final the way a proof-of-stake checkpoint is, and the safe number of confirmations depends on how mining power is spread across the network at the time.

​
What’s in this section

Network reference

Chain ID, consensus and supply parameters, public services, and the JSON-RPC methods specific to Parallax.

Differences from Ethereum

Finality, transaction types, block headers and the other places an Ethereum integration needs changes.

Running your nodes

Topology, sync and history settings, locking down JSON-RPC, health checks and upgrades.

Deposits

Deposit addresses, scanning blocks and traces, reorganizations, crediting and sweeping.

Withdrawals

Signing legacy transactions, fees, nonces, and replacing stuck withdrawals.

Confirmations

How many confirmations to wait for, from live mining data, and when to hold or pause deposits.

Network status API

The status page’s JSON API: fields, alerts, trust model, and a policy sketch in Python.

​
Integration checklist

1

Read the differences from Ethereum

Most integration problems come from finality, type 2 transactions and block headers. Differences from Ethereum.
2

Run at least two nodes you control

One for deposits and one for withdrawals at minimum, on separate hosts, with RPC reachable only from your own services. Running your nodes.
3

Test on a local chain

There is no public testnet. See Testing your integration.
4

Detect deposits from blocks, not from the mempool

Credit only transactions in blocks with a successful receipt, track them by block hash, and handle reorganizations. Deposits.
5

Send withdrawals as signed legacy transactions

Manage nonces yourself, price fees with eth_estimateSmartFee, and replace stuck transactions by fee. Withdrawals.
6

Set a confirmation policy tied to live mining data

A fixed number is not enough on a young proof-of-work chain. Poll the status page and your own nodes, scale confirmations with deposit size, and define when deposits pause. Confirmations and Network status API.
7

Watch for releases

Subscribe to GitHub releases and run parallaxd version-check from monitoring. Release notes say when an upgrade is mandatory. Upgrades.

​
Testing your integration

There is no public testnet at the moment, so test against a chain of your own:
  • Functional tests. parallaxd --dev starts a single-node chain (chain ID 1337) that seals a block as soon as a transaction arrives. It is quick for exercising address generation, deposit detection, sweeping and withdrawals. See Developer mode.
  • Reorganization drill. Run two or more nodes on a private network, let them mine apart, then reconnect them, and check that your scanner orphans and rescans the replaced blocks.
  • Mainnet. Finish with small real deposits and withdrawals.
Questions about integrating can go to the issue tracker. Report security problems privately, as described in Disclosures.