Jon Atack advises avoiding Bitcoin transactions during August’s BIP-110 activation period due to potential chain reorg risks. Low miner support raises concerns.
Bitcoin might be repeating a familiar bottom structure from the previous cycle.
Back in 2022, BTC dropped nearly 20% below the 2017 cycle high before finally forming its macro bottom.
Now, Bitcoin is trading roughly 15% below the 2021 cycle high, creating a setup that looks surprisingly similar.
Nothing is confirmed yet, but the pattern is definitely worth watching.
#Taiwan passes crypto regulatory law
#AI social science research breakthrough
Bitcoin is back above $60,000.
ETH has reclaimed $1,600.
$50M shorts liquidated in 60 minutes.
#Poland rejects MiCA crypto licensing
#Sleepagotchi expands health app
🔷 ZBTUSDT (Slow grind recovery after downtrend)
ZBT is trying to escape a long compression phase.
“After extended downside, ZBT is finally showing life again. Higher lows forming, EMAs flattening, and price stabilizing above recent support. Not explosive yet — but this is how reversals start: slow grind, then expansion.”
#Trump discloses crypto income
#Anthropic resumes Fable 5 access
Bitcoin’s quiet growth in 2025 is proof—those who doubted are now eating their words. #Bitcoin #DigitalGold
BIP-110, the Reduced Data Temporary Softfork, proposes a one-year temporary consensus soft fork that introduces seven new validation rules to restrict arbitrary data in Bitcoin transactions. It limits new non-OP_RETURN scriptPubKeys to 34 bytes (OP_RETURN up to 83 bytes), caps most data pushes and witness elements at 256 bytes, restricts Taproot control blocks to 257 bytes, and invalidates Taproot annexes, undefined witness versions, and specific opcodes (including OP_SUCCESS* and OP_IF/OP_NOTIF) in Tapscripts. Pre-activation UTXOs remain spendable under the old rules, and all restrictions automatically expire after roughly 52,416 blocks. The BIP itself identifies two key technical tradeoffs: capping control blocks constrains large on-chain script trees, which could complicate advanced constructions like BitVM (though proponents note these can use testnets or sidechains temporarily). It also temporarily disables certain upgrade hooks used in future soft forks, though this is viewed as low-risk given normal activation timelines. Critics raise additional concerns. The proposal’s 55% hashrate signaling threshold and UASF-style activation carry a risk of chain splits or reorgs if miner support remains low, a point Adam Back has highlighted while describing the proposal as technically flawed. The Taproot restrictions may also slow future innovation in complex scripts and covenants. While supporters argue it reduces node resource burdens from data bloat and refocuses Bitcoin on monetary use, skeptics contend the practical benefits are limited compared to the risks of precedent-setting transaction filtering and reduced neutrality. In summary, BIP-110 trades short-term limits on data-heavy and experimental uses for stronger monetary prioritization, at the cost of potential innovation friction and activation risks. It remains highly controversial as of July 2026. -grok
Native L1 blockchains, hear me out: Transition to a consumer app or shut down. Anyway, many of these native L1 blockchains. Bullish on @Stacks again
"And then along came blockchains." Turing Award winner Barbara Liskov on how PBFT — practical Byzantine fault tolerance, now foundational to modern consensus — started as a PhD student answering a DARPA RFP: "I had a student, Miguel Castro, who was looking for a PhD thesis, and I suggested to Miguel that he look at the RFPs that DARPA had put out … He found an RFP that was looking for ways to handle the malicious attacks that were going on on the internet." "When Miguel and I finished the work on practical Byzantine fault tolerance, we thought that at some point people would start to use this. … It was a delay of about 10 years before people started to use it."
JUST IN: Bitcoin reclaims $61,000
