This is the way
Putting a call out to anyone with a #Blake2b lighting node running- looking to get test channels spun up.
github.com/privkeyio/lightni…
Genius
Why Hashing Alone Should Not Be Confused With Mining
We should hold ourselves to a higher standard as a network.
The reason we changed proof-of-work was not because the previous algorithm stopped producing valid hashes. We changed because concentration surrounding mining had become incompatible with the decentralization we expect from Bitcoin.
We cannot make that transition and then immediately recreate the same structural failure.
Mining is more than producing hashes. It consists of two essential functions:
Block construction — independently determining the candidate block, choosing transactions, and having the opportunity to introduce transactions into the ledger.
Proof-of-work — expending computational energy to secure that candidate block and compete for the right to extend the chain.
Traditional pool-controlled Stratum V1 separates those responsibilities poorly. The pool constructs the work and exercises template authority while the ASIC operator largely supplies hashes.
Those hashes are real. The resulting block may be completely consensus valid. But valid does not automatically mean deserving of equal reward.
DATUM gives us the opportunity to do better:
Node → local DATUM → independently constructed block → ASIC → proof-of-work
A pool can still aggregate shares, reduce variance, and distribute payouts without becoming the authority that decides what its miners are permitted to put into blocks.
This is fundamental because decentralization is not merely about having many machines performing hashes. It is about maintaining equality of opportunity to participate in constructing the ledger.
Every miner should have a meaningful opportunity to construct its own template, select from valid transactions according to its own policy, and introduce its own valid transactions for inclusion when it wins the right to extend the chain.
That right disappears as template construction becomes centralized.
A network could have thousands of independently owned ASICs and still have only a handful—or even one—actual block constructor. Such a system may look decentralized when measured by machines while being profoundly centralized where it matters: control over what enters the ledger.
We therefore should not encourage that architecture by compensating centralized template delegation exactly as we compensate independent block construction.
Equal rewards for unequal contributions create the wrong incentive.
If surrendering template authority is cheaper, easier, and equally profitable, rational participants will surrender it. The protocol would effectively subsidize its own centralization.
It also encourages transient, drive-by hashrate: guns for hire that point at centrally supplied work, collect rewards, and leave when another opportunity becomes more profitable. Such participants provide proof-of-work, but capture compensation intended to incentivize decentralized network security without assuming the full responsibilities of mining.
SV1 hashing can remain consensus valid. It can remain available as a fallback because chain liveness matters.
But tolerance is not entitlement to equal compensation.
Our goal should be a system that continuously strives toward equality of opportunity: the opportunity for every participant, large or small, to construct a block template, exercise independent transaction-selection policy, and introduce valid transactions into the ledger without requiring permission from a centralized intermediary.
Centralization, if taken far enough, abolishes that opportunity.
We changed proof-of-work because we had already learned the consequences of allowing mining power to concentrate. We should not repeat that mistake by economically rewarding the architecture that recreates it.
Valid work may extend the chain. Full mining rewards should favor work that preserves the individual miner’s opportunity to participate directly in constructing the decentralized ledger that proof-of-work exists to secure.
Ex-miners abandoned #bitcoin on August 8th, 2026, by refusing to mine valid blocks following a critical soft fork, with the exception of @Roughnecks110
We plebs have taken up the slack since then with the #blake2b proof of work UPGRADE
Replying to @Scotthew82
The ex-miners QUIT on Aug 8th. We didn't need to fire them, they freely abandoned Bitcoin.
The PoW change was needed to make Bitcoin fully functional again. It did not fork the chain.
XBT Legata retweeted
Replying to @curly60e
No, if miners are not running their own node, it's not DATUM.
XBT Legata retweeted
Block 970,000, The Revolution. …S👀N…
Be PyBLØCK.
Node-Runners rule, Miners obey.
More info at: b.pyblock.xyz:8443
@Curly60e - PyBLØCK Crew.
XBT Legata retweeted
Here’s my breakdown of how to prepare for the #Blake2b PoW change if you’re interested in mining:
youtu.be/34ucRr_5is8
XBT Legata retweeted
Replying to @awbitcoin @mattkratter
No, that's the point.
20% (at most) support Core30's changes.
BIP110 merely defended the status quo from their onslaught.
XBT Legata retweeted
You can now book two humanoids for our cleaning service in SF. One humanoid for 60 minutes is $30, two are $60.
You can book a cleaning at tau-robotics.com. If you don’t have an invite code yet, join the waitlist. Timelapse at 5× speed (~40 minutes in real time).
Bpedo 🤣🤣
Facts bro
Facts:
1) Saturday, bad actors attempted a contentious hardfork with the purpose of forcing users to distribute CSAM. This spawned a new scamcoin with an airdrop (I call Bpedo).
2) Most formerly Bitcoin pools (a small handful of people) then began to attack the Bitcoin network to try to deceive the world into thinking Bpedo is "the real Bitcoin".
3) People who aren't using full nodes are easily fooled because they don't validate the blockchain. Upgrading to a full node (such as the latest release of Bitcoin Knots) will put you back on the Bitcoin network.
4) Community-led mitigations are in progress to overcome the ongoing attack on the Bitcoin network and restore it to full functionality. And update with these mitigations is expected by September 1st.




















