Bitcoin Core 0.17.1 unable to create non segwit adresses

[asche]

Hello all,

I have noticed something with Bitcoin Core's latest version.

Not sure if it's a problem with me, or with the app, maybe you can help me out here.

So until now I had only used non segwit adresses. Now I seem to be unable to generate new non segwit adresses. I only get segwit (starting with 3) or native segwit - bech32 (starting with bc).

Neither of which I can use to sign a message obviously.





Can you help me, or is this a bug?

[1714791071]

1714791071

[1714791071]

1714791071

[Carlton Banks]

You need to start Bitcoin with -addresstype=legacy added to the command. Then the wallet will generate the old style addresses.

[asche]

You need to start Bitcoin with -addresstype=legacy added to the command. Then the wallet will generate the old style addresses.

thank you man.

[darosior]

Hi,

since you are on windows maybe you don't start bitcoin-core using the command line. You can still generate new legacy addresses by typing

Code:

getnewaddress "testLegacy" legacy

on the debug window.

Ref : https://bitcoincore.org/en/doc/0.17.0/rpc/wallet/getnewaddress/

[achow101]

You need to start Bitcoin with -addresstype=legacy added to the command. Then the wallet will generate the old style addresses.

It can be added to the bitcoin.conf file as addresstype=legacy. No need to change the startup command, especially for users who don't know how to do that.

[bones261]

You need to start Bitcoin with -addresstype=legacy added to the command. Then the wallet will generate the old style addresses.

It can be added to the bitcoin.conf file as addresstype=legacy. No need to change the startup command, especially for users who don't know how to do that.

Can you start up your node with the switch; generate a legacy address; sign a message; close the wallet; then open the wallet normally; and go back to generating segwit addresses? I'm thinking to OP only wants to generate a P2PKH to sign a message.

[achow101]

You need to start Bitcoin with -addresstype=legacy added to the command. Then the wallet will generate the old style addresses.

It can be added to the bitcoin.conf file as addresstype=legacy. No need to change the startup command, especially for users who don't know how to do that.

Can you start up your node with the switch; generate a legacy address; sign a message; close the wallet; then open the wallet normally; and go back to generating segwit addresses? I'm thinking to OP only wants to generate a P2PKH to sign a message.

Certainly. It's not a setting in the wallet file itself so this isn't persisted. Or OP can just use the getnewaddress command mentioned earlier.

[buwaytress]

Sorry to ask a stupid question, but does this mean it's possible to have legacy and SegWit addresses in one wallet? From the discussions seems it's possible but I had always thought this couldn't be the case and still maintain 2 wallets. Or does the getnewaddress command also generate a new wallet? If Bitcoin Core could do that then it solves one of my old issues (providing legacy address but maintaining in same wallet).

[asche]

Sorry to ask a stupid question, but does this mean it's possible to have legacy and SegWit addresses in one wallet? From the discussions seems it's possible but I had always thought this couldn't be the case and still maintain 2 wallets. Or does the getnewaddress command also generate a new wallet? If Bitcoin Core could do that then it solves one of my old issues (providing legacy address but maintaining in same wallet).

Yes it is possible to have both - see screenshot.
I think it is because Segwit is backwards compatible (being a soft fork).

[HeRetiK]

Sorry to ask a stupid question, but does this mean it's possible to have legacy and SegWit addresses in one wallet? From the discussions seems it's possible but I had always thought this couldn't be the case and still maintain 2 wallets. Or does the getnewaddress command also generate a new wallet? If Bitcoin Core could do that then it solves one of my old issues (providing legacy address but maintaining in same wallet).

Yes it is possible to have both - see screenshot.
I think it is because Segwit is backwards compatible (being a soft fork).

SegWit being a soft fork has nothing to do with the way Bitcoin addresses are generated.

Good question though. From what I've gathered so far P2SH-SegWit and native Bech32 SegWit addresses follow different derivation paths, but I guess legacy addresses and P2SH-SegWit addresses share the same derivation path? Or maybe that's just specific to Bitcoin Core's HD Wallet implementation?

[asche]

SegWit being a soft fork has nothing to do with the way Bitcoin addresses are generated.

Good question though. From what I've gathered so far P2SH-SegWit and native Bech32 SegWit addresses follow different derivation paths, but I guess legacy addresses and P2SH-SegWit addresses share the same derivation path? Or maybe that's just specific to Bitcoin Core's HD Wallet implementation?

It actually does in my opinion. Their use is backwards compatible. Being able to receive through non segwit and send through segwit or the other way around is dependent to the fact it is a soft fork.

A hard fork would indeed make you have two wallets since there is no compatibility.

[achow101]

Sorry to ask a stupid question, but does this mean it's possible to have legacy and SegWit addresses in one wallet?

Yes.

Or does the getnewaddress command also generate a new wallet?

No, it does not generate a new wallet.

Good question though. From what I've gathered so far P2SH-SegWit and native Bech32 SegWit addresses follow different derivation paths, but I guess legacy addresses and P2SH-SegWit addresses share the same derivation path? Or maybe that's just specific to Bitcoin Core's HD Wallet implementation?

Bitcoin Core does not use different derivation paths for different address types. They are all derived using the same derivation path because keys are derived before the address type is known.

[buwaytress]

@achow thanks for that. Am quite surprised to learn this only now... Been using two different wallets just to have both Segwit and legacy. Now understand that Electrum has separate derivation paths.

Do you know of any other client other than Bitcoin Core that allows for this? (Legacy amd Segwit address in 1 wallet)

[Lauda]

Do you know of any other client other than Bitcoin Core that allows for this? (Legacy amd Segwit address in 1 wallet)

Not sure about desktop clients, but Samurai has this capability (Mobile). You can turn Segwit address generation on/off with 1 checkbox.

[achow101]

Do you know of any other client other than Bitcoin Core that allows for this? (Legacy amd Segwit address in 1 wallet)

IIRC Armory allows you to have both address types in one wallet. This is because they also generate keys before the address type is known.