If you've been on the fence, recent BIP-110 blocks being mined are a signal that momentum is starting to build. For Bitcoiners who want to keep spam off the network and push back against Bitcoin Core's current direction, this is your time to act. Here are the basics: 1. Run your own node (Start9, Umbrel, Windows, or Mac). 2. Run Bitcoin Knots and signal for BIP-110. 3. Point your home miners and/or rent hash rate through Ocean and Datum. You can also direct your hash rate to @_PyBlock_, which offers a Datum gateway that runs Bitcoin Knots and BIP-110. Help secure the Bitcoin network and get started with BIP-110.

"What is it about Core as a process that is causing all these bugs? These bugs are a result of a culture that makes everyone feel afraid to question anyone that is part of the untouchable clique at the center of it... So you have a few wizards at the top who's egos can never be touched or questioned, and you have all of their lackeys below them who will remain in the places they are in and be very careful not to offend the people, that way they can maintain their position and continue up the hierarchy, and theyll continue getting grants and funding.. those people will continue to exist, and they will continue screwing up as people get their energy drained out from the war that's going on... Everything gets discussed behind closed doors now, and if you dare question anything that happens in public, you're out. You're never going to have anything you ever write or propose in Bitcoin again be considered seriously, its just going to die."

BIP110, back at it with another block.

Bitcoin belongs to the plebs.

A recap of the last eight months of Bitcoin Core: ⚠️ 30 blew OP_RETURN open, 80b to 100KB. "Ethereum on Bitcoin." ❌ 30 and 30.1 could delete every wallet on the node during migration. 😱 31 reveals your IP to peers. Core is reduced to spam relay, deletion and doxxing. #BIP110

Bitcoin has survived 17 years _with_ the RDTS rules. It has only been "without them" since last October, a mere 8 months, and has been in mortal peril that entire time. It's only a matter of time until Bitcoin dies with this new status quo. RDTS is the only way to prevent that.

If a developer reaches the point where the egos of the Core devs feel threatened he'll be chased out quick. The resulting sycophantic monoculture is going to result in issues until more people realize that its no longer a competent team capable of maintaining Bitcoin's reference client

The deep state wants you to stack stonks, not sats. Wake up

Twice as many BIP-110 signaling blocks this period, compared to previous. And still 200 blocks to go. It’s pretty clear that BIP-110 support is growing. thebitcoinportal.com/live/no…

BIP-110 is inevitable. And BIP110 will not stop, how many blocks have they mined now?

Michael Saylor Never Seller?

Here We Go

At least the Bcashers had the guts to fork off. These corewhores are all talk

RDTS is currently the _only_ way. There are no alternatives or counter-fork proposed at this point. If RDTS isn't locked-in by August, signalling becomes mandatory, and blocks that don't signal are invalid. Miners do not get the option to impede the softfork.

(Note that I'm not endorsing this, just notifying you about it. Promise.)

Setting Up Lightning Payouts With Ocean (Home Bitcoin Mining)

Miners signal that they are ready. It's not a decision. Their deadline is August. If they don't get their act together by then, they are fired and their blocks will be rejected by the network.

I also find Saylor's claim that retweeting ERC20 grift is not endorsement, just "notifications", very ridiculous.

Growing...