# Broadcasting a signed Bitcoin transaction: what acceptance proves

Broadcasting submits a signed Bitcoin transaction to a network-connected node for validation and relay. A local acceptance result does not guarantee every peer accepts it or that a miner includes it. Core separates testmempoolaccept, which tests local rules, from sendrawtransaction, which submits the transaction. Repeated manual rebroadcast can also reveal information about the transaction’s origin.

Evidence: [testmempoolaccept RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/rawtransactions/testmempoolaccept/); [sendrawtransaction RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/rawtransactions/sendrawtransaction/); [P2P Network](https://developer.bitcoin.org/devguide/p2p_network.html)

Canonical: https://degreesofsatoshi.com/encyclopedia/bitcoin-transaction-broadcasting/
Published: 2026-10-02
Substantively modified: 2026-10-02
Independently verified by an automated reviewer: 2026-10-02T19:29:20.637Z
Data current through: 2026-10-02

AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied.

## Key facts

- **Test:** Local acceptance check without submission ([testmempoolaccept RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/rawtransactions/testmempoolaccept/))
- **Broadcast:** Submit the serialized transaction to a node ([sendrawtransaction RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/rawtransactions/sendrawtransaction/))
- **Settlement:** Inclusion requires a later chain event ([Block Chain](https://developer.bitcoin.org/devguide/block_chain.html))

## A transaction ID is not the transaction itself

A node needs the serialized transaction, including the required authorization data, to evaluate a new submission. An identifier is useful for lookup, but it is not a file from which an unknown transaction can always be reconstructed.

Signing can happen on a different device from broadcasting. The relay device does not need to learn the private key merely to submit an already signed transaction.

Evidence: [sendrawtransaction RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/rawtransactions/sendrawtransaction/); [Transactions](https://developer.bitcoin.org/devguide/transactions.html)

## Read a test result at its actual scope

The cited Core RPC checks both consensus and local policy rules, and can report a rejection reason. For a package, parent ordering and package conditions also matter. A successful result describes what that node would accept under the observed conditions.

For example, a test at one moment can pass before another transaction spends the same input. The earlier result does not reserve the output or a place in a future block.

Evidence: [testmempoolaccept RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/rawtransactions/testmempoolaccept/)

## Preserve the transaction before retrying

After submission, record the transaction ID and inspect the relevant outputs and later confirmation state. If a network call times out, the node may have received the transaction even though your application missed the response. Check before creating a separate payment.

Core warns that manual rebroadcast can leak origin information because its behavior differs from normal relay of transactions already known to the node. More submission services are not automatically better privacy or guaranteed faster confirmation.

Evidence: [sendrawtransaction RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/rawtransactions/sendrawtransaction/); [Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html)

## Questions

### Does testmempoolaccept send my transaction?

No. It evaluates local acceptance rules and returns a result. Core provides sendrawtransaction for submission. A successful test is not a broadcast receipt, miner commitment or confirmation.

Evidence: [testmempoolaccept RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/rawtransactions/testmempoolaccept/); [sendrawtransaction RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/rawtransactions/sendrawtransaction/)

### Can someone else broadcast a transaction I signed offline?

Yes, if they possess the complete valid signed transaction. Broadcasting does not require your private key; that is why you should review and control the signed payment before handing it to a relay.

Evidence: [Cold Storage](https://electrum.readthedocs.io/en/latest/coldstorage.html); [sendrawtransaction RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/rawtransactions/sendrawtransaction/)

## Claims and scope

### bitcoin-transaction-broadcasting-quick-answer

Broadcasting submits a signed Bitcoin transaction to a network-connected node for validation and relay. A local acceptance result does not guarantee every peer accepts it or that a miner includes it. Core separates testmempoolaccept, which tests local rules, from sendrawtransaction, which submits the transaction. Repeated manual rebroadcast can also reveal information about the transaction’s origin.

Educational explanation. Product-specific behavior is scoped to the cited documentation, checked 2026-10-02.

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

### bitcoin-transaction-broadcasting-fact-test

Test: Local acceptance check without submission

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

### bitcoin-transaction-broadcasting-fact-broadcast

Broadcast: Submit the serialized transaction to a node

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

### bitcoin-transaction-broadcasting-fact-settlement

Settlement: Inclusion requires a later chain event

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

## Sources

- [testmempoolaccept RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/rawtransactions/testmempoolaccept/) — Bitcoin Core. Local admission checks do not broadcast or promise miner inclusion. Locator: Description; Result: allowed, reject-reason. Retrieved: 2026-10-02T18:53:56.573Z.
- [sendrawtransaction RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/rawtransactions/sendrawtransaction/) — Bitcoin Core. Submitting serialized signed transactions, fee guardrails and rebroadcast privacy warning. Locator: Description; Arguments; Result. Retrieved: 2026-10-02T18:53:56.420Z.
- [P2P Network](https://developer.bitcoin.org/devguide/p2p_network.html) — Bitcoin developer documentation. Peer connections, initial download and block/transaction relay. Locator: Peer Discovery; Connecting To Peers; Initial Block Download; Block Broadcasting; Transaction Broadcasting. Retrieved: 2026-10-02T18:53:53.860Z.
- [Block Chain](https://developer.bitcoin.org/devguide/block_chain.html) — Bitcoin developer documentation. Chain validation, block timing, proof of work and accepted-chain context. Locator: Block Height And Forking; Transaction Data; Proof Of Work; Consensus Rule Changes. Retrieved: 2026-10-02T18:53:53.957Z.
- [Transactions](https://developer.bitcoin.org/devguide/transactions.html) — Bitcoin developer documentation. Inputs, outputs, authorization, change, coinbase exceptions and fee accounting. Locator: Introduction; Spending An Output; P2PKH Script Validation; Multisig; Transaction Fees And Change; Avoiding Key Reuse. Retrieved: 2026-10-02T18:53:53.759Z.
- [Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html) — Bitcoin developer documentation. Payment request interpretation, confirmation checks and refund destination risks; historical protocol sections are dated. Locator: Requesting Payments; Verifying Payment; Issuing Refunds. Retrieved: 2026-10-02T18:53:53.958Z.
- [Cold Storage](https://electrum.readthedocs.io/en/latest/coldstorage.html) — Electrum. Electrum offline signing workflow and separation of watch-only and signing devices. Locator: Create an offline wallet; Create a watching-only version of your wallet; Create an unsigned transaction; Get your transaction signed; Broadcast your transaction. Retrieved: 2026-10-02T18:53:56.455Z.

## Revision history

- 2026-10-02: First publication after primary-source research and separate automated verification.

## Cite this entry

Degrees of Satoshi editorial project. “Broadcasting a signed Bitcoin transaction: what acceptance proves.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/bitcoin-transaction-broadcasting/