So here's the plan for selecting Bitcoin's new PoW algorithm...

Luke Dashjr

npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk

hex

3f859c0e5b04b0ecbbfa2699209bb90628f714ab27863359633601ac57f96523

nevent

nevent1qqsrlpvupedsfv8vh0azdxfqnwusv28hzj4j0p3nt93nvqdv2luk2gcprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs0m40g76hqmwqhhc9hrk3qfxxpsp5k3k9xgk24nsjf7v305u6xffczvn0jh

Kind-1 (TextNote)

2026-08-11T13:09:25Z

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

原始 JSON

{
  "kind": 1,
  "id": "3f859c0e5b04b0ecbbfa2699209bb90628f714ab27863359633601ac57f96523",
  "pubkey": "fdd5e8f6ae0db817be0b71da20498c1806968d8a6459559c249f322fa73464a7",
  "created_at": 1786453765,
  "tags": [
    [
      "client",
      "Amethyst"
    ]
  ],
  "content": "So here's the plan for selecting Bitcoin's new PoW algorithm:\n\nNobody knows the new algorithm right now, and nobody will until we all know at the same moment.\n\nAt 14:00 UTC August 11th, we will begin watching Bitcoin's Testnet4 chain for new blocks.\n\nThe very next block found, look at the block hash.\nThe last character will choose the new algorithm.\n(Note that testnet4 blocks are typically timestamped wrong!)\n\nAs soon as I see that block, I will reveal the mapping showing which algorithm that character represents.\n\nThroughout the last 24+ hours, the community has discussed and made a short list of candidate algorithms.\nI compiled that list into a weighted (according to their suitability) set of options for the mapping list.\n\nYou can prove I didn't rig it, by SHA256 hashing the mapping text file.\nIt will match 71a7960874f3352f4ba600ce67bd6f8e96702565abea93021fa86349d99a45e8",
  "sig": "83ff6b9d0e097a36863dea4a0855980efa540cdb51baa616bdeae49fe057c21ff3d54fe3765b1b70af5962abc53bb9e4ff88c200b35bb60c55a51c2a07f0c470"
}