> For the complete documentation index, see [llms.txt](https://timechain.gitbook.io/neucron/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://timechain.gitbook.io/neucron/networks-and-assets/supported-networks.md). # Supported Networks Neucron treats **each blockchain as a rail** for moving value, the same way card networks, ACH, and SEPA are rails. Your product integrates one wallet API; Neucron handles address derivation, transaction submission, confirmation tracking, and asset standards per rail underneath. This page lists which rails are live, which are on the roadmap, and how to choose between them. ## Live rails | Rail | Type | Send | Receive (webhooks) | Token issuance | Testnet | Notes | | --------- | -------- | ---- | ------------------ | -------------------------------- | -------------- | --------------------------------------------------------------------------------------------------- | | BSV | L1 | Yes | Yes | STAS utility tokens and ordinals | Yes | Neucron's first integrated rail; useful for low-fee utility-token and ordinal workflows. | | Ethereum | L1 | Yes | Yes | ERC-20 utility tokens | Yes | Deepest institutional liquidity and stablecoin/RWA ecosystem; highest fees among live public rails. | | Polygon | L1/L2 | Yes | Yes | ERC-20 utility tokens | Yes | Consumer brands, payments, and gaming; low fees. | | BNB Chain | L1 | Yes | Yes | ERC-20 utility tokens | Yes | Retail and low-cost DeFi reach. | | Base | L2 | Yes | Yes | ERC-20 utility tokens | Yes | OP Stack L2 with strong consumer and fintech distribution. | | Avalanche | L1 | Yes | Yes | ERC-20 utility tokens | Yes | RWA tokenization and subnet ecosystem. | | Optimism | L2 | Yes | Yes | ERC-20 utility tokens | Yes | Governance and Superchain ecosystem. | | Arbitrum | L2 | Yes | Yes | ERC-20 utility tokens | Yes | DeFi and institutional L2 activity. | | HyperEVM | L1 (EVM) | Yes | Yes | ERC-20 utility tokens | **No testnet** | Production rail; plan integration testing accordingly because testnet support is not available. | | Tron | L1 | Yes | **No** | TRC-20 tokens | Yes | Balance sync is available; inbound transfers are not webhook-delivered. | | Cardano | L1 | Yes | Yes | Native assets | Yes | ADA support for wallet and transfer workflows. | {% hint style="info" %} **Tron receive flows:** Tron has balance sync but no receive webhooks. If your product depends on push notifications for inbound payments, prefer a rail with receive webhooks, or design for polled balance updates on Tron. {% endhint %} Balance sync, sending, receiving, and utility-token issuance on the live rails are production capabilities. Anything not listed above is on the roadmap, not live. ## Roadmap rails The following networks are evaluated and prioritized, but **not yet live**. Status for every row below is **planned**. | Rail | Type | Consensus | Typical fees | Primary adoption profile | Status | | -------------- | ------------ | ----------------- | ------------ | ----------------------------------------------------- | ------- | | Solana | L1 | PoH + PoS | < $0.01 | Retail / high-frequency trading (3,000 to 50,000 TPS) | Planned | | Stellar | L1 | SCP (federated) | < $0.0001 | Remittances / CBDCs | Planned | | Hedera | L1 | aBFT (hashgraph) | \~$0.0001 | Enterprise ESG / notarization | Planned | | XRPL (Ripple) | L1 | RPCA | < $0.001 | Cross-border liquidity | Planned | | Algorand | L1 | PPoS | \~$0.001 | High-throughput L1 (10,000+ TPS) | Planned | | Aptos / Sui | L1 | Move-based BFT | Low | Move-based object assets | Planned | | Canton Network | L1 / private | BFT (Daml) | $0.1+ | Inter-bank settlement / privacy | Planned | | Corda | Private | Notary | N/A | Regulated finance / insurance | Planned | | Hyperledger | Private | Modular / plug-in | N/A | Enterprise supply chain | Planned | ```mermaid flowchart LR P[Your product] --> N[Neucron Wallet API] subgraph Live["Live rails"] L0[BSV] L1[Ethereum] L2[Polygon / BNB / Base / Avalanche] L3[Optimism / Arbitrum / HyperEVM] L4[Tron / Cardano] end subgraph Roadmap["Roadmap rails"] R1[Solana / Stellar / Hedera / XRPL / Algorand] R2[Aptos / Sui] R3[Canton / Corda / Hyperledger] end N --> Live N -.-> Roadmap ``` ## How fintechs choose rails The selection criteria are the same ones you already use for payment rails: cost, speed, finality, adoption, and compliance. **Fees.** Ethereum L1 is best for high-value settlement and institutional liquidity. EVM L2s such as Base, Optimism, and Arbitrum are better for lower-cost consumer and fintech workflows. BSV is useful for very low-fee utility-token and ordinal workflows. Sub-cent rails such as Stellar, Solana, and XRPL are on the roadmap. **Throughput.** Ethereum L1 handles lower throughput than L2s. BSV and several roadmap rails are relevant when the product needs low-cost, high-volume transfers or tokenized utility activity. **Finality and settlement.** Public account-model rails finalize within seconds to minutes. Private settlement rails on the roadmap (Canton, Corda, Hyperledger) offer atomic settlement, which matters for delivery-versus-payment in regulated finance. **Adoption type.** Match the rail to your customer base: Ethereum for institutional liquidity and DeFi, BSV for Neucron's earliest low-fee token workflows, BNB and Solana for retail reach, Stellar for remittances and CBDCs, Avalanche for RWA tokenization, and private rails (Canton, Corda) for inter-bank or insurance workflows. **Compliance posture.** Permissioned rails and permissioned token standards go together. If you issue regulated instruments, you will pair the rail choice with a security-token protocol such as ERC-3643 or CMTAT. See [Asset Protocols & Types](/neucron/networks-and-assets/asset-protocols-and-types.md). **Talent and ecosystem.** Developer availability is a real cost. Ethereum has extreme talent demand and the deepest pool; Solana is very high; newer or private rails are thinner. | If your product needs... | Consider | | ------------------------------------------- | ----------------------------------------------------------------- | | Lowest-cost consumer payments at scale | BSV, Polygon, BNB Chain, Base (live); Solana or Stellar (roadmap) | | Institutional DeFi liquidity | Ethereum, Arbitrum (live) | | Utility tokens and ordinal-backed workflows | BSV with STAS tokens and ordinals | | RWA / tokenized securities distribution | Avalanche and Ethereum (live); Canton (roadmap) | | Cross-border remittances | Tron (live, polled receives); Stellar or XRPL (roadmap) | | Regulated inter-bank settlement | Canton or Corda (roadmap) | {% hint style="info" %} **Design principle:** you never bet on one rail. The same wallet, balance, and transfer APIs work across every live network, and roadmap rails are added without breaking changes to your integration. {% endhint %} ## Related pages * [Asset Protocols & Types](/neucron/networks-and-assets/asset-protocols-and-types.md): which token standard to use on each rail * Assets: Live & Upcoming: per-rail capability matrix and asset roadmap * Blockchains as Rails: the rail model in depth