Skip to main content
£0.00 0

Basket

No products in the basket.

ASIC mining knowledge centre

BIP 338 Disable Transaction Relay Message: Historical Guide

BIP 338 guide covering its Closed status, disabletx proposal, block-relay-only connections, version-message limits, negotiation, compatibility and successor context.

BIP 338 Disable transaction relay message guide cover

This guide explains BIP 338 Disable transaction relay message in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.

TL;DR

  • What it is: BIP 338 proposed a disabletx peer-to-peer message so a node could state that a connection would never be used for transaction relay. The design targeted block-relay-only links, reducing bandwidth and making parts of the network graph harder to infer.
  • Why it matters: BIP 338 captured a useful explicit-signalling idea for block-relay-only links, but its Closed status is decisive. Use it to understand the design problem, not as a current interoperability contract.
  • Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.

What this means in simple English

A BIP is a document that proposes or explains a Bitcoin idea, standard or rule. A BIP number does not mean the idea is active. Some BIPs are widely used, while others are drafts or historical proposals.

You do not need to read code to understand the main point. Start with the status, the problem being addressed and the practical effect on ordinary users, wallets, miners or node operators.

Simple example

Think of the transaction as a form passed between several authorised signers. Each person or device checks the same payment details before adding approval. Passing the form around does not make the payment safe unless every signer checks what it contains.

Key terms in plain English

BIP:
Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
Node:
A computer running Bitcoin software that checks data and communicates with other peers.

Closed status

The primary record labels BIP 338 Peer Services, Specification and Closed. Do not advertise disabletx as generally negotiated current behaviour solely because block-relay-only connections exist.

Motivation

Low-bandwidth block-only connections can improve resistance to network partitions and reduce topology disclosure by avoiding transactions and address gossip.

Version-message limitation

The relay field in the version message indicated initial transaction relay preference but was not a permanent lifetime commitment, leaving an inbound peer unable to distinguish a permanent block-only link.

BIP 338 Disable transaction relay message technical diagram
Version-message limitation: the fields, validation boundary and operational evidence that implementations need to agree.

Proposed signal

The proposal added an explicit message after connection negotiation to declare that transaction relay would remain disabled. Implementations needed ordering and one-time-state rules to avoid ambiguity.

Connection behaviour

A block-relay-only connection still exchanges the messages needed for blocks and chain maintenance. It must not be mistaken for a full transaction relay or address source.

Compatibility

Peers unaware of the new message would treat it according to existing unknown-message behaviour, but operators still needed feature negotiation and fallback logic.

How specialists test it

Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.

Frequently asked questions

What is BIP 338 Disable Transaction Relay Message?

BIP 338 proposed a disabletx peer-to-peer message so a node could state that a connection would never be used for transaction relay. The design targeted block-relay-only links, reducing bandwidth and making parts of the network graph harder to infer.

Is BIP 338 Disable Transaction Relay Message active or supported today?

Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.

Why does BIP 338 Disable Transaction Relay Message matter?

BIP 338 captured a useful explicit-signalling idea for block-relay-only links, but its Closed status is decisive. Use it to understand the design problem, not as a current interoperability contract.

Do beginners need to use the technical details?

No. Most readers only need to understand the idea and its current status. Developers and node operators can use the primary sources when they need the exact technical rules.

Conclusion

BIP 338 captured a useful explicit-signalling idea for block-relay-only links, but its Closed status is decisive. Use it to understand the design problem, not as a current interoperability contract.

Primary sources

Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.

On this page

Search More Guides

Continue Reading

Explore more practical guidance on ASIC hardware, profitability, setup, hosting and maintenance.

Need Advice for Your Mining Setup?

Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.
Contact our team
Browse ASIC miners