Skip to content
Broadcaster

BSV Transaction Broadcaster

The world's most scalable transaction broadcast manager

A high-throughput, callback-driven gateway for submitting BSV transactions, tracking their lifecycle, and streaming status updates to subscribers in real time.

API server base URL
http://arcade-v2-testnet-us-1.bsvblockchain.tech
Checking
Content encoding
UTF-8
Status codes
2xx · 4xx · 5xx
broadcast.sh
curl -X POST http://arcade-v2-testnet-us-1.bsvblockchain.tech/tx \  -H "Content-Type: text/plain" \  -d "0100000001abc...def00000000"# -> 202{  "txid": "<hex>",  "status": 202,  "txStatus": "RECEIVED"}

API reference

Submit, track and stream, from one reference

11 API server routes with their request and response contracts, headers and examples, the status lifecycle, and the Chaintracks block-header API. Every route has its own link.

YOU CALLYOU HEAR BACKPOST/txPOST/txsGET/eventsBroadcasterRECEIVEDSEEN_ON_NETWORKMINED→ SSE · webhook

Questions

How does BSV Broadcaster work?

What is BSV Broadcaster?

A Teranode-native transaction broadcast and status-tracking service. It accepts BSV transactions, validates them against policy, broadcasts them to Teranode, tracks their lifecycle and emits status updates over webhooks and Server-Sent Events. It was built as a Teranode-native replacement for ARC.

How do I submit a transaction?

Send it to POST /tx, or a batch to POST /txs, on the API server serving this page (http://arcade-v2-testnet-us-1.bsvblockchain.tech). The body can be raw bytes (application/octet-stream, the most efficient), hex (text/plain) or a JSON envelope. Policy validation runs before the 202 response, which carries the txid and the status RECEIVED.

How do I track a transaction's status?

Three ways. Look it up any time with GET /tx/:txid. Stream updates over Server-Sent Events on GET /events, scoped by the X-CallbackToken you submitted with. Or register a webhook with the X-CallbackUrl header when you submit.

Is BSV Broadcaster the same as Arcade?

Yes. The project formerly called Arcade was renamed BSV Broadcaster. Legacy ARCADE_* environment variables are still read and mapped to their BSV_BROADCASTER_* names, with a deprecation warning at startup.