Next scheduled rescrape ... never
Version 1
Last scraped
Edited on 27/09/2025, 16:55:01 UTC
Quote
Bitcoin shouldn't have anything but base58 addresses that begin with an 1.
Then tell me, should it have P2PK? Because in the Genesis Block, and in many blocks after it, coins were sent to public keys, not addresses.

Quote
the fact that an attacker needs less bits to steal all funds vs a non-HD wallet has not been disputed
Of course, because every HD wallet is in practice a single key, that is expanded in deterministic way. And if you somehow break that key, then you will access everything. But good luck with that. The famous puzzle from transaction 08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 also used HD wallet.

And more than that: public keys from 161-bit to 256-bit range were revealed. Many private keys with lower ranges, up to 70-bit, are known. So what? Over 900 BTC is waiting for you, so just break a single key, and grab them all. Hmm, you don't know how? Well, maybe because it is not so easy, to compromise a HD wallet. So, don't worry too much about HD wallet security. This challenge can prove you, that HD wallets can be safe, otherwise you would sweep all of that instantly, if you would know some weakness.

Quote
no excuse to not support it
But they are supported. You can have a descriptor wallet, and load each and every key from WIF manually. So, what exactly is your problem?

Edit: For example, let's assume that you are purist, who wants to use only compressed P2PK with descriptor wallet:
Code:
createwallet "" false true
{
  "name": ""
}
listdescriptors true
{
  "wallet_name": "",
  "descriptors": [
  ]
}
getdescriptorinfo "pk(KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU73sVHnoWn)"
{
  "descriptor": "pk(0279be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798)#gn28ywm7",
  "checksum": "c6fur0yd",
  "isrange": false,
  "issolvable": true,
  "hasprivatekeys": true
}
importdescriptors '[{"desc":"pk(KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU73sVHnoWn)#c6fur0yd","timestamp":"now","label":"one"}]'
[
  {
    "success": true
  }
]
listdescriptors true
{
  "wallet_name": "",
  "descriptors": [
    {
      "desc": "pk(KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU73sVHnoWn)#c6fur0yd",
      "timestamp": 1231006505,
      "active": false
    }
  ]
}
See? It works. If you replace "pk" with "pkh", then you will get your favourite addresses, starting with one. So, just migrate your old wallet, and enjoy it. And you can still use the old wallet, if you want to. Nobody would stop you. Or you can call "createwallet" manually each time, when you want to get a new address. It is up to you.
Original archived Re: What is the rationale behind dropping old wallet.dat support exactly?
Scraped on 20/09/2025, 16:54:34 UTC
Quote
Bitcoin shouldn't have anything but base58 addresses that begin with an 1.
Then tell me, should it have P2PK? Because in the Genesis Block, and in many blocks after it, coins were sent to public keys, not addresses.

Quote
the fact that an attacker needs less bits to steal all funds vs a non-HD wallet has not been disputed
Of course, because every HD wallet is in practice a single key, that is expanded in deterministic way. And if you somehow break that key, then you will access everything. But good luck with that. The famous puzzle from transaction 08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 also used HD wallet.

And more than that: public keys from 161-bit to 256-bit range were revealed. Many private keys with lower ranges, up to 70-bit, are known. So what? Over 900 BTC is waiting for you, so just break a single key, and grab them all. Hmm, you don't know how? Well, maybe because it is not so easy, to compromise a HD wallet. So, don't worry too much about HD wallet security. This challenge can prove you, that HD wallets can be safe, otherwise you would sweep all of that instantly, if you would know some weakness.

Quote
no excuse to not support it
But they are supported. You can have a descriptor wallet, and load each and every key from WIF manually. So, what exactly is your problem?