# Network endpoints

> For the complete documentation index, see [llms.txt](https://bsvblockchain.com/docs/llms.txt).

The explorer, faucet, broadcast endpoints, wallet storage and address format of every BSV blockchain network that @bsv/sdk and @bsv/wallet-toolbox support.

import BlueTable from '/snippets/BlueTable.jsx';

Look up the explorer, faucet (A site that sends free test coins to an address), broadcast endpoint, wallet storage and address format of each BSV blockchain network. Use it when you point code, a wallet or a test script at a network, and take every value from the same row. What each network is for, and the name each package gives it, is in [How BSV blockchain networks differ](https://bsvblockchain.com/docs/concepts/networks/).

This page was written against `@bsv/sdk` 4.0.1 and `@bsv/wallet-toolbox` 2.15.1. Every endpoint on it was checked on 3 November 2026.

## Endpoints by network

Each row is one public network. The BSV Broadcaster and wallet storage of each network are in the sections below:

<BlueTable>

| Network | Explorer | Faucet | Address starts with |
| --- | --- | --- | --- |
| Mainnet, `main` | [whatsonchain.com](https://whatsonchain.com/) | None | `1` |
| testnet, `test` | [test.whatsonchain.com](https://test.whatsonchain.com/) | [bsvfaucet.com](https://bsvfaucet.com/) | `m` or `n` |
| teratestnet, `ttn` | [woc-ttn.bsvblockchain.tech](https://woc-ttn.bsvblockchain.tech/) | [faucet-ttn.bsvblockchain.tech](https://faucet-ttn.bsvblockchain.tech/) | `m` or `n` |

</BlueTable>

`@bsv/wallet-toolbox` also accepts `stn`, `tstn`, `regtest` and `mock` as `chain`. They have no public explorer, faucet or storage. For `stn`, `tstn` and `regtest`, the toolbox reads the broadcaster address from `STN_ARCADE_URL`, `TSTN_ARCADE_URL` or `REGTEST_ARCADE_URL`, and the block header service from `STN_CHAINTRACKS_URL`, `TSTN_CHAINTRACKS_URL` or `REGTEST_CHAINTRACKS_URL`, which falls back to `/chaintracks/v1` on the broadcaster host when unset. `mock` uses no network and needs `MockServices`.

## Broadcast endpoints

The public BSV Broadcaster (Transaction broadcaster software that takes a signed transaction over HTTP and follows it until it is mined) endpoints need no API key, and [Broadcast transactions with BSV Broadcaster](https://bsvblockchain.com/docs/guides/services/broadcasting/) shows how to submit to them. Each one answered `GET /health` with `"healthy":true`. The ones marked in the last column are the hosts `@bsv/wallet-toolbox` uses:

<BlueTable>

| Network | Endpoint | Used by `@bsv/wallet-toolbox` |
| --- | --- | --- |
| Mainnet | `https://arcade-v2-us-1.bsvblockchain.tech` | Yes |
| Mainnet | `https://arcade-us-1.bsvblockchain.tech` | No |
| Mainnet | `https://arcade-eu-1.bsvblockchain.tech` | No |
| Mainnet | `https://arcade.gorillapool.io` | No |
| testnet | `https://arcade-v2-testnet-us-1.bsvblockchain.tech` | Yes |
| teratestnet | `https://arcade-v2-ttn-us-1.bsvblockchain.tech` | Yes |

</BlueTable>

> Any endpoint in a Mainnet row moves real BitcoinSV (BSV), and a broadcast transaction cannot be undone. Match the endpoint to the network your keys and wallet use before you send.

### Defaults in the packages

When your code does not name a broadcaster, the packages pick one by network:

<BlueTable>

| Network | `@bsv/sdk` | `Services` in `@bsv/wallet-toolbox`, in the order it tries them |
| --- | --- | --- |
| Mainnet | `https://arc.gorillapool.io` | `https://arc.gorillapool.io`, then `https://arc.taal.com`, then Bitails at `https://api.bitails.io/`, then WhatsOnChain |
| testnet | `https://testnet.arc.gorillapool.io` | `https://arc-test.taal.com`, then Bitails at `https://test-api.bitails.io/`, then WhatsOnChain |
| teratestnet | None | `https://arcade-v2-ttn-us-1.bsvblockchain.tech` only |

</BlueTable>

- In `@bsv/sdk`, `tx.broadcast()` with no argument always sends to the Mainnet address. The testnet address comes from `defaultBroadcaster(true)`. Both are ARC (The broadcast API that came before BSV Broadcaster) endpoints.
- In `@bsv/wallet-toolbox`, `createDefaultWalletServicesOptions` takes a BSV Broadcaster endpoint as its ninth argument, `arcadeUrl`, and puts it first on Mainnet or testnet.

## Explorer API

Each public network has a WhatsOnChain API for transactions, addresses and block data. Each base answered `GET /chain/info`:

<BlueTable>

| Network | API base | `chain` in the answer |
| --- | --- | --- |
| Mainnet | `https://api.whatsonchain.com/v1/bsv/main` | `main` |
| testnet | `https://api.whatsonchain.com/v1/bsv/test` | `test` |
| teratestnet | `https://api.woc-ttn.bsvblockchain.tech/v1/bsv/test` | `teratestnet` |

</BlueTable>

The teratestnet API keeps `test` in its path. The `WhatsOnChain` class of `@bsv/sdk` does not accept a teratestnet value, and the `Services` class of `@bsv/wallet-toolbox` calls WhatsOnChain only on Mainnet and testnet.

## Wallet storage

`Setup.createWalletClientNoEnv` in `@bsv/wallet-toolbox` uses `https://storage.babbage.systems` when `chain` is `main`, and `https://staging-storage.babbage.systems` for every other chain. Each server names its network on its home page:

<BlueTable>

| URL | Home page text |
| --- | --- |
| `https://storage.babbage.systems` | `BRC-100 mainNet Storage Provider.` |
| `https://staging-storage.babbage.systems` | `BRC-100 ttnNet Storage Provider.` |

</BlueTable>

The default for `test` is therefore a server that names teratestnet, and testnet has no package default. For a testnet wallet, pass `storageUrl` with a testnet storage server, or keep the storage local with `Setup.createWalletSQLite`.

## Address format

The first character tells a Mainnet address from a testnet address made from the same key:

<BlueTable>

| Network | `toAddress` argument | Starts with |
| --- | --- | --- |
| Mainnet | `'mainnet'` or `'main'`, or no argument | `1` |
| testnet | `'testnet'` or `'test'` | `m` or `n` |
| teratestnet | `'testnet'` | `m` or `n` |

</BlueTable>

`toAddress` in `@bsv/sdk` throws `Invalid prefix` for `'ttn'`, `'teratestnet'`, `'stn'` and `'regtest'`. Teratestnet uses the testnet format, and its explorer API accepts an address that starts with `m` and rejects one that starts with `1`. An address shows only how it was encoded, not the network your code is on, as [How BSV blockchain networks differ](https://bsvblockchain.com/docs/concepts/networks/#how-to-tell-which-network-you-are-on) explains.

## Related articles

To learn more about BSV blockchain networks and their services, review these articles:

- [How BSV blockchain networks differ](https://bsvblockchain.com/docs/concepts/networks/)
- [Broadcast transactions with BSV Broadcaster](https://bsvblockchain.com/docs/guides/services/broadcasting/)
- [Verify your payment on the explorer](https://bsvblockchain.com/docs/get-started/verify/)