For the complete documentation index, see llms.txt. This page is also available as Markdown.

Quickstart

Take a signed transaction from hex to mined in a few minutes using a public BSV Broadcaster endpoint, from the command line or any of the SDKs.

This page gets one transaction onto the BSV blockchain and shows you how to watch it get mined. It uses a public BSV Broadcaster endpoint, so there is nothing to install or sign up for. Where it says <hex>, substitute your own signed transaction.

1. Get a signed transaction

You need a fully signed transaction serialised as hex. If you do not have one yet:

  • Follow the Quick Start in the Intro section, which funds a key and builds a transaction with the TypeScript SDK. Stop before the tx.broadcast() line and use tx.toHex() instead.

  • Or use one of the SDK examples: TypeScript, Go, or Python.

  • Or export a raw transaction from any wallet that offers it.

The transaction must spend outputs that exist and are unspent, and must pay at least the fee rate the endpoint requires, which you check next.

2. Pick an endpoint and read its policy

Choose the public instance nearest to you. This page uses the BSV Association's US endpoint throughout; the full list is on the BSV Broadcaster page.

export BROADCASTER=https://arcade-us-1.bsvblockchain.tech
curl -s $BROADCASTER/policy
{
  "policy": {
    "miningFee": { "satoshis": 1, "bytes": 1000 },
    "maxtxsizepolicy": 100000000,
    "maxscriptsizepolicy": 100000000,
    "maxtxsigopscountspolicy": 4294967295,
    "standardFormatSupported": true
  },
  "timestamp": "2026-10-16T12:00:00Z"
}

miningFee is the minimum rate the instance will accept, here one satoshi per kilobyte. If your transaction pays less, build it again with a higher fee before continuing.

3. Submit it

A 202 means BSV Broadcaster validated the transaction and is delivering it to the network. If you get a 400 instead, the body tells you what is wrong with the transaction itself; fix it and resubmit. Nothing else is at fault, so do not try another service with the same bytes.

Sending the same transaction twice is harmless. You get another 202 with whatever status it has reached.

4. Watch it progress

Run that a few times. Within seconds txStatus should move from RECEIVED through SENT_TO_NETWORK to SEEN_ON_NETWORK, at which point miners have it and it is safe to treat as a zero-confirmation payment. Within roughly ten minutes it should reach MINED:

The merklePath is a BUMP you can verify against block headers yourself. That is the proof of inclusion an SPV client needs, and you got it without running a node.

If you would rather not poll, open a stream instead. Submit with an X-CallbackToken: mytoken header, then:

Every status change for transactions submitted with that token arrives as a server-sent event.

5. The same from the SDKs

Each snippet loads a transaction from hex and broadcasts it to the same endpoint.

BSV Broadcaster's /tx endpoint takes a hex body, so a broadcaster is a few lines. The SDK's built-in Teranode class also works, but only when every input carries its sourceTransaction, which a transaction loaded from bare hex does not.

The Go SDK's Arc broadcaster posts to {ApiUrl}/tx, which is BSV Broadcaster's path, and accepts the 202 response.

The Python SDK has a native Arcade class.

Where to go next

  • Get notified instead of polling. Submit with X-CallbackUrl and BSV Broadcaster will POST each status change to your server. See Webhooks.

  • Run your own BSV Broadcaster. The public endpoints are shared. For private callbacks, your own policy, and no third-party dependency, run an instance; it takes about ten minutes.

  • Use a different route. Every other way to broadcast, and when each one makes sense, is on the overview.

Last updated