WIO

bip

BLOCKCHAIN_PROTOCOL

Evidence in r/Bitcoin — Bitcoin

Trend support

Rising+0.2 pp
Current seven-day window
Current 2026-07-12 → 2026-07-18
Comparison seven-day window
Comparison 2026-07-05 → 2026-07-11
Distinct-document support
Seen in 12 current vs 1 comparison posts/comments
Mentions
29 current vs 1 mentions

Windows are complete UTC days compared with the preceding seven. How trends are measured.

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-07-18

Final complete day: 2026-07-18. Attention was 0.2% — this entity appeared in 12 of 6,464 analyzed posts/comments in the seven days ending that day (29 mentions).

0%1.0%Apr 20Jun 3Jul 18

Hover, touch, or focus the chart (Tab) and use the arrow keys — each point is one seven-day window.

View all 90 data points (semantic table)
Week endingSeven-day rangeStatusPrevalenceSeen inMentionsAnalyzed
2026-04-202026-04-142026-04-20Comparable0.1%5 of 7,68657,686
2026-04-212026-04-152026-04-21Comparable0.1%4 of 7,96947,969
2026-04-222026-04-162026-04-22Comparable0.1%4 of 8,57948,579
2026-04-232026-04-172026-04-23Comparable0.0%1 of 8,12318,123
2026-04-242026-04-182026-04-24Comparable0.0%1 of 7,56017,560
2026-04-252026-04-192026-04-25Comparable0.0%2 of 6,93626,936
2026-04-262026-04-202026-04-26Comparable0.0%2 of 6,58326,583
2026-04-272026-04-212026-04-27Comparable0.0%2 of 6,33826,338
2026-04-282026-04-222026-04-28Comparable0.0%2 of 5,80825,808
2026-04-292026-04-232026-04-29Comparable0.0%2 of 5,45125,451
2026-04-302026-04-242026-04-30Comparable0.0%1 of 5,11515,115
2026-05-012026-04-252026-05-01Comparable0.0%1 of 5,02115,021
2026-05-022026-04-262026-05-02Comparable0.0%1 of 5,27915,279
2026-05-032026-04-272026-05-03Comparable0.0%2 of 5,62245,622
2026-05-042026-04-282026-05-04Comparable0.0%2 of 5,55045,550
2026-05-052026-04-292026-05-05Comparable0.0%2 of 5,71145,711
2026-05-062026-04-302026-05-06Comparable0.0%2 of 5,79845,798
2026-05-072026-05-012026-05-07Comparable0.0%2 of 5,97345,973
2026-05-082026-05-022026-05-08Comparable0.0%2 of 5,94645,946
2026-05-092026-05-032026-05-09Comparable0.0%1 of 5,70535,705
2026-05-102026-05-042026-05-10Comparable0.0%0 of 5,64105,641
2026-05-112026-05-052026-05-11Comparable0.0%0 of 5,78105,781
2026-05-122026-05-062026-05-12Comparable0.0%0 of 5,54105,541
2026-05-132026-05-072026-05-13Comparable0.0%0 of 5,33305,333
2026-05-142026-05-082026-05-14Comparable0.0%0 of 5,42805,428
2026-05-152026-05-092026-05-15Comparable0.0%0 of 5,49505,495
2026-05-162026-05-102026-05-16Comparable0.0%0 of 5,53605,536
2026-05-172026-05-112026-05-17Comparable0.0%0 of 5,39705,397
2026-05-182026-05-122026-05-18Comparable0.0%0 of 5,20805,208
2026-05-192026-05-132026-05-19Comparable0.0%0 of 5,48605,486
2026-05-202026-05-142026-05-20Comparable0.0%0 of 5,66605,666
2026-05-212026-05-152026-05-21Comparable0.0%1 of 5,57515,575
2026-05-222026-05-162026-05-22Comparable0.0%1 of 5,61515,615
2026-05-232026-05-172026-05-23Comparable0.0%1 of 5,61815,618
2026-05-242026-05-182026-05-24Comparable0.0%1 of 5,60015,600
2026-05-252026-05-192026-05-25Comparable0.0%1 of 5,34515,345
2026-05-262026-05-202026-05-26Comparable0.0%1 of 4,81414,814
2026-05-272026-05-212026-05-27Comparable0.0%1 of 4,25814,258
2026-05-282026-05-222026-05-28Comparable0.0%1 of 4,34214,342
2026-05-292026-05-232026-05-29Comparable0.1%2 of 4,19024,190
2026-05-302026-05-242026-05-30Comparable0.1%2 of 3,95723,957
2026-05-312026-05-252026-05-31Comparable0.1%2 of 3,77323,773
2026-06-012026-05-262026-06-01Comparable0.0%2 of 4,67824,678
2026-06-022026-05-272026-06-02Comparable0.0%2 of 5,99725,997
2026-06-032026-05-282026-06-03Comparable0.0%2 of 7,46927,469
2026-06-042026-05-292026-06-04Comparable0.0%1 of 9,14919,149
2026-06-052026-05-302026-06-05Comparable0.0%0 of 11,221011,221
2026-06-062026-05-312026-06-06Comparable0.0%0 of 13,257013,257
2026-06-072026-06-012026-06-07Comparable0.0%1 of 15,112115,112
2026-06-082026-06-022026-06-08Comparable0.0%3 of 15,448315,448
2026-06-092026-06-032026-06-09Comparable0.0%3 of 15,396315,396
2026-06-102026-06-042026-06-10Comparable0.0%3 of 15,368315,368
2026-06-112026-06-052026-06-11Comparable0.0%3 of 14,251314,251
2026-06-122026-06-062026-06-12Comparable0.0%4 of 12,863512,863
2026-06-132026-06-072026-06-13Comparable0.0%4 of 11,471511,471
2026-06-142026-06-082026-06-14Comparable0.0%3 of 10,175410,175
2026-06-152026-06-092026-06-15Comparable0.0%1 of 9,14429,144
2026-06-162026-06-102026-06-16Comparable0.0%1 of 8,04128,041
2026-06-172026-06-112026-06-17Comparable0.0%2 of 6,99036,990
2026-06-182026-06-122026-06-18Comparable0.0%2 of 6,53836,538
2026-06-192026-06-132026-06-19Comparable0.0%1 of 5,82715,827
2026-06-202026-06-142026-06-20Comparable0.0%1 of 5,76915,769
2026-06-212026-06-152026-06-21Comparable0.0%1 of 5,27215,272
2026-06-222026-06-162026-06-22Comparable0.0%1 of 5,11515,115
2026-06-232026-06-172026-06-23Comparable0.0%1 of 5,21215,212
2026-06-242026-06-182026-06-24Comparable0.0%0 of 6,23706,237
2026-06-252026-06-192026-06-25Comparable0.0%0 of 7,03707,037
2026-06-262026-06-202026-06-26Comparable0.0%1 of 7,62517,625
2026-06-272026-06-212026-06-27Comparable0.0%1 of 7,97917,979
2026-06-282026-06-222026-06-28Comparable0.0%2 of 8,38638,386
2026-06-292026-06-232026-06-29Comparable0.0%2 of 9,90739,907
2026-06-302026-06-242026-06-30Comparable0.1%5 of 10,622710,622
2026-07-012026-06-252026-07-01Comparable0.1%6 of 10,536810,536
2026-07-022026-06-262026-07-02Comparable0.1%6 of 10,059810,059
2026-07-032026-06-272026-07-03Comparable0.1%5 of 9,74379,743
2026-07-042026-06-282026-07-04Comparable0.1%5 of 9,04879,048
2026-07-052026-06-292026-07-05Comparable0.1%4 of 8,81558,815
2026-07-062026-06-302026-07-06Comparable0.1%4 of 7,49657,496
2026-07-072026-07-012026-07-07Comparable0.0%2 of 6,89326,893
2026-07-082026-07-022026-07-08Comparable0.0%1 of 5,78615,786
2026-07-092026-07-032026-07-09Comparable0.0%1 of 5,43515,435
2026-07-102026-07-042026-07-10Comparable0.0%1 of 5,36815,368
2026-07-112026-07-052026-07-11Comparable0.0%1 of 5,29415,294
2026-07-122026-07-062026-07-12Comparable0.0%1 of 5,20615,206
2026-07-132026-07-072026-07-13Comparable0.0%1 of 5,28215,282
2026-07-142026-07-082026-07-14Comparable0.1%5 of 5,40295,402
2026-07-152026-07-092026-07-15Comparable0.1%7 of 5,767115,767
2026-07-162026-07-102026-07-16Comparable0.1%8 of 5,763125,763
2026-07-172026-07-112026-07-17Comparable0.2%12 of 5,842295,842
2026-07-182026-07-122026-07-18Comparable0.2%12 of 6,464296,464

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

  1. Comment

    Right, which is a logical conclusion given that never before in the history of bitcoin have a significant portion of miners waited until the last possible moment to signal for a BIP activation. Signaling is meant to display readiness and allow for smooth distributed coordination across a global group, it's not a game you play to "rug" other miners and cause disruptions.

  2. Comment

    Reader: This would only be the case if no more hash joins the bip.

  3. Comment

    Sure, but how much are the miningpools willing to risk a reorg? That’s a lot of money they risk wasting in case of a reorg of the legacy chain. Especially if they they aren’t fighting and actively opposing the bip. If they are indifferent, the most safe thing would be to just join the bip. Also if a mining pool want to hurt the other miningpools and force them to loose blocks and revenue, it would switch to the bip and trigger a join cascade and a reorg. And the sooner they do it, the less money they loose themselves in a reorg. The threat of this won’t go away. The only way to get around this would be if the miners collude together and sign an agreement to not join the bip chain. This in itself would imply that the pools would trust each other, which would likely be shaky. And if the miner colludes, bitcoin is lost. They can then force though any change they want…

  4. Comment

    The bip will 100% activate in the nodes that run it. At activation, all the thousands of nodes, running the bip, will reject blocks that contain op_ret larger then 83B or if they contain usage the most common inscriptions exploit prohibited by the bip. The question is rather if the miners will start to filter out non-bip110 compliant transactions, or risk having their block rejected by every node enforcing the bip. All current nodes will accept blocks that are bip110 compliant. That’s the beauty of a soft fork that tightens the rules. Bip110 will reject some blocks that current nodes accept, but all current nodes will accept the stricter bip blocks and chain. Before the nodes activate, the miners have an opportunity to signal if they want to activate the bip early. If 55% of blocks in a difficulty adjustment (2016 blocks) signals for the bip, then it locks in and activate in the next adjustment. As a miner, when bip110 activates, the block template you mine must exclude transactions that violate the bip. Using your bip110 node to build templates will do this for you. I’m not a miner, so dyor. If the majority of miners refuse, or ignore, building blocks that are bip110 compliant, then we have a chain split. The risk to the non-signaling miners is that if other miners would start to mine on the bip chain instead, and the bip chain would become the longest, then all the blocks in the non-signaling chain will be lost, along with all their block rewards. So the faster you switch to the bip chain, the fewer blocks you will loose in the legacy chain. The bitcoin in your trezor will not disappear or become a different form of bitcoin. If there is no persistent chain split, then nothing will happen to the coins. If there is a persistent split, then pre split coins will exist in both chains. I’d refrain from making transactions during those weeks, until the dust settles. Personally, I think a persistent chain split is unlikely. I don’t think that miners will risk mining on the legacy chain with the risk of having all their blocks there thrown out if the bip chain becomes the longest. They won’t risk it since there is no real miner movement against the bip. I think that it’s only f2pool’s founder that has said they wont run bip110.

  5. Comment

    That's what BIPs are for

Excerpts above are public Reddit posts and comments. WIO never synthesizes Reddit URLs from stored ids, and entities are extracted automatically and may be wrong. See the extraction notes and the limitations and privacy section of the methodology.