The network
Networks and assets
Two public test networks are supported today. Both are testnets — the assets on them have no value.
| Network | Code | Native asset | Token |
|---|---|---|---|
| Ethereum Sepolia | sep | ETH | USDT (a Varnir-deployed test USDT) |
| Tron Nile | niles | TRX | USDT (a Varnir-deployed test USDT) |
Deposit records carry the network as TRX-NILE, while wallet and pool records
use niles. Both refer to the same network — they come from different code
paths (the L1 deposit monitors versus the wallet pool). If you match on the
network string anywhere, normalise both spellings, case-insensitively.
Wallet claiming is addressed by network code plus native symbol — for Tron
Nile that is niles / trx, for Ethereum Sepolia sep / eth.
Currencies on an invoice
An invoice is priced in one of exactly two currencies:
native— the wallet's own chain token, ETH or TRX depending on the network.USDT
Deposit records use different spellings than invoices do: a native transfer may
arrive labelled #native (or with no currency at all), and a Tron USDT transfer
arrives labelled Tether. Varnir normalises these when matching payments to
invoices, so you generally do not have to — but if you read raw deposit records
yourself, expect all of those spellings.
Ledger nodes
The settlement layer is a four-node ActiveLedger testnet. Transactions are POSTed directly to a node — your signing code talks to the chain, not through a Varnir API:
https://node1-testnet.varnir.site
https://node2-testnet.varnir.site
https://node3-testnet.varnir.site
https://node4-testnet.varnir.site
Any node accepts any transaction. A robust integration should try them in turn and move on when one is unreachable, which is exactly what the SDK example does.
Explorer
The public block explorer is at scanner.varnir.site.
It indexes ledger transactions, L1 deposits on both networks, wallets and
identities, and hosts the browser wallet at
/wallet.
The same host serves the HTTP API that these docs' API reference describes.
Contract identities
The on-ledger contracts an integration signs against, in the varnir
namespace:
| Contract | Id |
|---|---|
| Onboard | 79bfad7705d57b81e4e15cbce425686d97e240972e5d319058c675685bc4dc98 |
| AssignOwner | fd9e832e1169d5fb1aa7a591cdbd8bb74dff7addde4e26176bf21f6569ef8e64 |
These are testnet ids and will change if the contracts are redeployed. Read them from configuration rather than hardcoding them in anything long-lived.