Skip to content
Closed

. #2246

Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
75 changes: 75 additions & 0 deletions BIP-911.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,75 @@
## Take 1

```
BIP: 911
Layer: Applications (relay policy) / Consensus (soft fork)
Title: Reduced Discourse Temporary Softfork (RDTS-2)
Author: Dathon Ohm II <dathon.ohm.ii@proton.me>
Amir "genjix" Takki <genjix@riseup.net> (advisory, unreachable)
Comments-URI: https://github.com/[repo]/bips/wiki/Comments:BIP-0911
Status: Draft
Type: Standards Track
Created: 2026-09-11
Requires: BIP-110 (deceased), BIP-148 (retired, in good standing)
License: BSD-2-Clause
```

### Abstract

This BIP specifies a temporary consensus-layer restriction on transactions whose principal economic purpose is the continuation of prior consensus-layer restrictions. Following the conclusion of the BIP-110 mandatory-signalling window on approximately August 8, 2026, on-chain and off-chain measurements indicate that the debate itself has become a load-bearing component of Bitcoin's mempool, developer bandwidth, and lower back. This proposal introduces seven new consensus rules, of which four are load-bearing and three are for symmetry with the document it addresses.

### Motivation

The reference implementation of Bitcoin has, over several release cycles, developed a class of participant characterized by a stable set of dietary, athletic, and sacramental commitments: a diet consisting principally of ribeye; a training regimen consisting principally of the deadlift; a light regimen consisting principally of direct sunlight applied to regions previously assumed to be shaded by design; and a devotional regimen consisting principally of the Tridentine Mass, mediated by IRC.

This BIP takes no position on any of these commitments individually. It observes only that their combined signal in the OP_RETURN field has, as of block 963,648, exceeded the combined signal of every legitimately-authored inscription since 2023, and that the resulting payloads increasingly resemble a devotional codex maintained by a single node operator in southern Florida.

The author further observes that at least one BIP-110 signalling block was mined by a pool whose devotional literature is presently longer than its release notes, and that this ratio, while not itself a consensus violation, is difficult to defend at a difficulty adjustment.

### Specification

After activation, upgraded nodes shall reject:

1. Any output whose script, decoded, contains a case-insensitive match for `spam`, `sound money`, `filter`, `Knots`, or `the real Bitcoin`.
2. Any OP_RETURN payload whose entropy is indistinguishable from that produced by a recent-vintage hardware wallet's PRNG. Reference vectors are provided in Appendix C. Wallets shipped between firmware versions 6.2.1.X and 6.2.2.X are, for the purposes of this BIP, treated as producing constants.
3. Any transaction whose witness contains, in any encoding, a reference to a document authored by a party listed in the unsealed exhibits to *United States v. Maxwell* (S.D.N.Y.), including but not limited to correspondence, flight manifests, and Bitcoin address books whose provenance is described by the author as "recreational."
4. Any transaction broadcast from an IP address geolocated to a gymnasium.
5. Any coinbase whose scriptSig contains the string `/Ocean/` followed, within 33 bytes, by a Latin liturgical fragment.
6. Any block whose header timestamp falls between 08:46 and 10:28 UTC on September 11 of any year and which also signals bit 4. Rationale: the author is aware of the coincidence and considers it in poor taste on both sides.
7. Reserved.

Pre-existing UTXOs are grandfathered, including those attributed to the late Amir Taaki, whose 2011-era outputs are held to have been created in a spirit of curiosity that the present proposal does not seek to relitigate.

### Rationale

Rule (2) is included in recognition of the fact that, in mid-2026, a nontrivial fraction of nominally high-entropy on-chain data was in fact produced by a single deterministic function evaluated at a single point. Filtering it out is therefore not censorship of expression but deduplication of a constant, which the author submits is a well-established relay policy dating to at least 2011.

Rule (3) is included because a soft fork that filters "spam" but not the correspondence of J.E. is, on inspection, filtering the wrong data.

Rule (6) is included because the author acknowledges that the number 911 has multiple readings, and wishes to close one of them explicitly rather than leave it as an exercise for the reader.

The 55% activation threshold is retained from BIP-110 in order to test the hypothesis, advanced by that proposal's proponents, that 55% is a load-bearing number. The author suspects it is not, but wishes to be shown.

### Deployment

Signalling begins at block 970,000, using version bit 4. The reuse of bit 4 is intentional. The author is aware of the recommendations in the alternate BIP-911 draft ("Version Bit 4 Retirement and Consensus Cool-Down Period") and considers them, in the author's own phrasing, misguided and unusually careless.

A mandatory-signalling flag day is set at block 1,006,146. The choice of block height is not symbolic. The author has checked.

### Backwards Compatibility

This proposal is a soft fork with respect to consensus. It is a hard fork with respect to the group chat.

### Reference Implementation

A reference implementation is available in the `knots-of-knots` branch of a fork of a fork of Bitcoin Core, maintained by a pseudonymous contributor who declines to appear on video, on principle, and in daylight, for related reasons.

### Security Considerations

Rule (2) may be circumvented by any wallet capable of generating genuine entropy. As of publication, the set of such wallets is understood to be nonempty but was, for approximately six weeks in mid-2026, smaller than commonly assumed.

Rule (3) is not expected to affect any transaction the author would defend in public.

### Copyright

Released under BSD-2-Clause. The phrase "sound money" continues to be claimed by everyone, and is used here without prejudice.