Skip to main content
Version: 1.x

Supported Chains & Assets

Yellow Network nodes advertise their supported blockchains, ChannelHub addresses, and assets through v1 RPC. Treat runtime discovery as the source of truth.

Runtime Discovery​

Do not hardcode v1 contract addresses in application docs or app configuration. The active Nitronode returns current network and asset configuration:

  • client.getConfig() wraps node.v1.get_config and returns the node address, node version, supported signature validators, supported blockchains, and each blockchain's ChannelHub address.
  • client.getAssets() wraps node.v1.get_assets and returns asset symbols, decimals, suggested blockchain IDs, token addresses, and token chain IDs.
import { Client, createSigners, withBlockchainRPC } from '@yellow-org/sdk';

const wsUrl = process.env.NITRONODE_WS_URL!;
const rpcUrl = process.env.RPC_URL!;
const chainId = BigInt(process.env.CHAIN_ID!);
const privateKey = process.env.PRIVATE_KEY as `0x${string}`;

const { stateSigner, txSigner } = createSigners(privateKey);
const client = await Client.create(
  wsUrl,
  stateSigner,
  txSigner,
  withBlockchainRPC(chainId, rpcUrl),
);

const config = await client.getConfig();
const assets = await client.getAssets();

for (const chain of config.blockchains) {
  console.log(`${chain.name} (${chain.id}) ChannelHub=${chain.channelHubAddress}`);
}

for (const asset of assets) {
  console.log(`${asset.symbol} decimals=${asset.decimals}`);
  for (const token of asset.tokens) {
    console.log(`  chain=${token.blockchainId} token=${token.address}`);
  }
}

Raw RPC clients can call node.v1.get_config for blockchain and ChannelHub data and node.v1.get_assets for asset and token data.

:::tip Builder Toolkit Need a consolidated list of live examples, source repositories, Playground, faucet, MCP, and SDK entry points? Open the Builder Toolkit. :::

Current Public Endpoints​

The table below was queried from the public v1 Nitronode endpoints on June 2, 2026. Treat it as a convenience snapshot. The active endpoint response from node.v1.get_assets remains the source of truth for production code.

EnvironmentWebSocket endpointNode addressNode version
Production (mainnet)wss://nitronode.yellow.org/v1/ws0xbffaa37e34fb9aa11b23eb6cc939abbb45d6ccb655fd346
Sandboxwss://nitronode-sandbox.yellow.org/v1/ws0x6f375dad1ff0ad968bdde939f76a2b3d6b9d3ec555fd346

Current Asset Matrix​

Use this matrix for asset availability. Exact token decimals can vary by chain, so use the token address tables below when configuring amounts.

Asset symbolSandbox NitronodeProduction Nitronode
ethEther, 18 decimals. Available on Linea Sepolia 59141, Base Sepolia 84532, and Ethereum Sepolia 11155111.Ether, 18 decimals. Available on Linea 59144.
polPOL, 18 decimals. Available on Polygon Amoy 80002.Not listed.
usdtNot listed.Tether USD. Available on Ethereum 1, Flare 14, BSC 56, Polygon 137, Base 8453, Linea 59144, and XRPL EVM 1440000; token decimals are chain-specific.
xrpXRP. Available on XRPL EVM Testnet 1449000; token decimals are chain-specific.XRP. Available on Flare 14 and XRPL EVM 1440000; token decimals are chain-specific.
yellowYellow, 18 decimals. Available on Ethereum Sepolia 11155111.Yellow, 18 decimals. Available on Ethereum 1.
yusdYellow USD. Available on Linea Sepolia 59141, Polygon Amoy 80002, Base Sepolia 84532, XRPL EVM Testnet 1449000, and Ethereum Sepolia 11155111; token decimals are chain-specific.Not listed.

Production Token Addresses​

AssetChainToken addressToken decimals
ethLinea 591440x000000000000000000000000000000000000000018
usdtEthereum 10xdac17f958d2ee523a2206206994597c13d831ec76
usdtFlare 140xe7cd86e13ac4309349f30b3435a9d337750fc82d6
usdtBSC 560x55d398326f99059ff775485246999027b319795518
usdtPolygon 1370xc2132d05d31c914a87c6611c10748aeb04b58e8f6
usdtBase 84530xfde4c96c8593536e31f229ea8f37b2ada2699bb26
usdtLinea 591440xa219439258ca9da29e9cc4ce5596924745e12b936
usdtXRPL EVM 14400000x9f8cf9c00fac501b3965872f4ed3271f6f4d06ff6
xrpFlare 140xad552a648c74d49e10027ab8a618a3ad4901c5be6
xrpXRPL EVM 14400000xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee18
yellowEthereum 10x236eb848c95b231299b4aa9f56c73d689346272018

Sandbox Token Addresses​

AssetChainToken addressToken decimals
ethLinea Sepolia 591410x000000000000000000000000000000000000000018
ethBase Sepolia 845320x000000000000000000000000000000000000000018
ethEthereum Sepolia 111551110x000000000000000000000000000000000000000018
polPolygon Amoy 800020x000000000000000000000000000000000000000018
xrpXRPL EVM Testnet 14490000xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee18
yellowEthereum Sepolia 111551110x236eb848c95b231299b4aa9f56c73d689346272018
yusdLinea Sepolia 591410x67a5f0b0553e22689a539b80cbe4a1cd126e2bde18
yusdPolygon Amoy 800020x1b66e510b845a746334b866b62c64746bebff8578
yusdBase Sepolia 845320x67a5f0b0553e22689a539b80cbe4a1cd126e2bde6
yusdXRPL EVM Testnet 14490000x67a5f0b0553e22689a539b80cbe4a1cd126e2bde18
yusdEthereum Sepolia 111551110x67a5f0b0553e22689a539b80cbe4a1cd126e2bde6

Native assets use the sentinel token address returned by Nitronode: 0x0000000000000000000000000000000000000000 for native EVM gas tokens and 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee where the node config uses that native-token marker.

Deployed v1 Contract Folders​

The Nitrolite repository currently contains v1 deployment artifacts under contracts/deployments.

Chain IDDeployment folder
11155111contracts/deployments/11155111/
80002contracts/deployments/80002/
84532contracts/deployments/84532/

Each folder contains ChannelHub, ChannelEngine, escrow engines, signature validators, and test token deployment records for that chain. Use the runtime RPC response for the active endpoint you are connected to, because a node may support only a subset of deployed chains.

Asset Symbols​

Asset symbols are node configuration, not protocol constants. The current v1 sandbox examples use symbols such as yusd and yellow, all represented in lower case, but applications should discover the available list through client.getAssets() or node.v1.get_assets.

See Also​