X.KOJIRA.IO
Timeline

Luke Dashjr

[email protected]
npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk
Roman #Catholic, husband, father of 11 children, #Bitcoin developer, and CEO @npub1e3r35vx7yluvn6tn9uhnf5jxuh5lzf2q0qnjwjfs5gxkj6xk63xsjgg6l2 ; INTP;
I condemn fake "Catholics", cryptobros & pedos; see full bio
How does that make any sense?
Bitcoin is back online! Scammers in shock.

nevent1qqszsvgu2az…
blake2b_headline=8-30 NYPost Deride And Conquer
PSA: Potential Bitcoin PoW change Sunday. SHA2 miners should stop mining Saturday.

- nprofile1qqsg3mj8t… 29.4.1rc4 will be released tomorrow, setup for mainnet rehearsal. This locks-in the final SHA2 block.
- After NYPost updates their Sunday morning print online, I'll post the canonical blake2b_headline parameter.
- If things go perfectly, Knots 29.4.1 final will be released Sep 1 on schedule, keeping the Aug 30 blockchain.
- If there's any issues (unlikely at this point), we address them and reset to the last SHA2 block for rc5.

If you intend to mine from day 1, I recommend getting setup with testnet4 (rc3) _now_ so you're ready for mainnet on Sunday.
There's discussion about adding it to RDTS (so expiring)
So here's the plan for selecting Bitcoin's new PoW algorithm:

Nobody knows the new algorithm right now, and nobody will until we all know at the same moment.

At 14:00 UTC August 11th, we will begin watching Bitcoin's Testnet4 chain for new blocks.

The very next block found, look at the block hash.
The last character will choose the new algorithm.
(Note that testnet4 blocks are typically timestamped wrong!)

As soon as I see that block, I will reveal the mapping showing which algorithm that character represents.

Throughout the last 24+ hours, the community has discussed and made a short list of candidate algorithms.
I compiled that list into a weighted (according to their suitability) set of options for the mapping list.

You can prove I didn't rig it, by SHA256 hashing the mapping text file.
It will match 71a7960874f3352f4ba600ce67bd6f8e96702565abea93021fa86349d99a45e8
There's many people able to repeat the attack at this point.
Quite a few people suggesting/using dice to mitigate the Coldcard vulnerability.

Note that common dice are not designed to be cryptographically secure.

If you are going to do this, you probably should buy precision casino dice. And even then, have another source of entropy.
Exactly. Validity is an important requirement. And nodes defined that. Which includes BIP110.
"longest chain wins" is the bcash mantra.
Go back to bcash if you're not ready to accept that nodes are in control
No, UASF is for everything now. Miners don't get to make the decisions.
It's nonsense
I support BIP110 because Bitcoin is essential to the future of mankind and the last 8 months have proven it to be the best immediate solution to the critical injury inflicted by Core 30.
Knots already did years ago
And we shouldn't fork off Taproot, just close the vulnerabilities it introduced
Witness is part of the block....
Removing rules is a hardfork.

That includes scheduled rules like subsidy halvings, and yes, even BIP110.

Rejecting BIP110 is a contentious hardfork attempt.
And unlike softforks, hardforks need consensus to succeed.
There is no consensus on rejecting BIP110.
Scammers and bad actors have been claiming BIP110 was "dead on arrival" or otherwise failed from the first day Dathon Ohm published it.

It was fake news then, and it's fake news now.

BIP110 has consensus and will still succeed if we hold the line.
BIP110 creates a rare opportunity for bitcoiners we should take advantage of:

Unlike most consensus changes, it is extremely simple: with only 5 modified lines of code and 72 added, across 5 source code files, we can explain it in a way anyone can understand.

Take a look. Review BIP110 yourself:

https://bitcoinknots.org/learn/bip110-code-walkthrough.html
Bitcoin today is the result of a few hardforks
Certain bad actors are trying to distract you with lies about me supposedly calling for a hardfork or proof-of-work change/removal.

Let me be perfectly clear: I do not at this time support either.
Haskell isn't bootstrappable so bad for security
The spec for Tonal Bitcoin (TBC) was finished 2011 January 7th

The first wallet to support it was on 2011 January 19th

Knots support was 2012 January
What?
Not interested in your scams.
It takes time to think through, implement, and review a more complicated long term change.

In that time, anyone can just destroy Bitcoin irreversibly.

RDTS protects Bitcoin while we do that longer term R&D
No, it acknowledges BitVM issues are a tradeoff and that is part of why it expires in a year.
BitVM is unlikely to be ready for production within a year anyway.
Miners do not control the network.
60% is what recent data shows. Feel free to do your own analysis.
So no actual bug, just FUD
older →