@glozow Bitcoin Core's v30 will be the version that has fractured its dominance. Time to embrace Bitcoin Knots & other implementations for true dev decentralization. No more benevolent Core dictators. Time has come to embrace a more decentralized future for Bitcoin’s development.
@jabulanijakes@MundokAdam You're right that running two different hash algors under the exact same ticker on one exchange is asking for trouble. It is true that the collision risk is real but not impossible to handle (IMO).
@BitcoinMonk21 AlphaPool (F2Pool) should've used DATUM. They're a bad actor and clearly don't care.
You change the algorithm when it gets captured. If it happens again, fire them again.
That's the feature, not a bug.
@88_sats Calling it insane is easier than answering the point, right?
The whole reason this chain exists is because industrial pools captured the last one. Now a new pool does the same shit and you act like nodes pushing back is the crazy part.
You got nothing left so you just go personal
Quote of the day from @MiningStacker:
"This community does not give a flying fuck about prices, listings on exchanges, any of that crap. They care about keeping to the principles."
Exactly!
SHA256d obsess over price.
Blake2b: principles over capture.
https://t.co/30X8nOM6gK
@BitcoinMonk21 You keep treating that as some shocking new development instead of the entire point of the fork.
Pooling is fine, but ecreating the exact industrial capture the POW change was designed to kill is not.
https://t.co/Gz5haOmmnX
@MiningRabid Nodes set the rules. Miners follow them or get left behind.
A pool dominating the chain that was created to escape industrial capture, while refusing DATUM, isn't some free-speech martyr. Rejecting that power grab isn’t "censorship". It's the network refusing to get owned again.
Quote of the day from @MiningStacker:
"This community does not give a flying fuck about prices, listings on exchanges, any of that crap. They care about keeping to the principles."
Exactly!
SHA256d obsess over price.
Blake2b: principles over capture.
https://t.co/30X8nOM6gK
@Dimi_h@MiningRabid Temporary or not, the principle stays the same.
Nodes decide the rules. Miners that start recreating the exact centralization the POW change was designed to kill don't get a free pass just because the chain is young.
@MiningRabid Nodes set the rules. Miners follow them or get left behind.
A pool dominating the chain that was created to escape industrial capture, while refusing DATUM, isn't some free-speech martyr. Rejecting that power grab isn’t "censorship". It's the network refusing to get owned again.
@Ahkilleux@NeoxaPortal XBT isn't a random or bad pick.
It's the actual ISO 4217 currency code for Bitcoin (same as XAU for gold).
BTCB2 was just a temporary descriptive label for Blake2b. XBT is the formal standards based ticker and been used for Bitcoin in traditional finance for years.
It's *not* an inside job.
Andy wasn't running a Ponzi Scheme and Blockstream absolutely did *not* pull off a fake hack, stealing their own money and giving it back to themselves minus the money they needed (~$50m or so) to keep the game of musical chairs going.
It's totally a thing for a "white hat" to take a $50m cut for themselves.
Thanks Bitcoin Core. We used to have a monetary network. Now we have the world's most expensive, immutable Discord for whitehats and the companies they just drained.
Maybe Core's next upgrade: on-chain group therapy and dating profiles, if not worse.
@NotSatoshiDeSu Yes. they fixed the bug in the code and merged it publicly on Sept 1. Basically, the patch commits were visible to everyone.
It seems someone reverse engineered the fix and exploited it.
Liquid got LIQUIDATED!
Liquid's BTC reserves just got drained 95%.
Blockstream had the fix on Sept 1.
They made the patch public.
They never released it, instead They left the network running the vulnerable code.
https://t.co/SZFAUORcdW