send from "1xxx..." to "3xxx..." ?

[OddEvenBets.com]

Hello,

Can I send BTC from old format address "1xxx..." to "3xxx..." ?
Also from "3xxx..." to "1xxx.."?

I use bitcoin core node  "version": 160200

I don't wanna experience.

Thanks.

[1715075291]

1715075291

[1715075291]

1715075291

[1715075291]

1715075291

[TryNinja]

Yes.

P.S: There is no such thing as "old format"; Both formats are fully compatible and usable. The difference is that those starting with a 1 are Legacy addresses and 3 are P2SH addresses (in most cases, multi-sig or nested Segwit).

[OddEvenBets.com]

Yes.

P.S: There is no such thing as "old format"; Both formats are fully compatible and usable. The difference is that those starting with a 1 are Legacy addresses and 3 are P2SH addresses (in most cases, multi-sig or nested Segwit).

Ok,
I installed new bitcoin node and get new address like "3xxx.."

How can I configurate node for Legacy address (I want use Legacy address)?

[TryNinja]

I installed new bitcoin node and get new address like "3xxx.."

How can I configurate node for Legacy address?

Why would you do that? Nested Segwit addresses (3xxx...) are 26% cheaper to send and you also help the network.

There are also NO downsides or negative points on doing this. Meanwhile, on Legacy addresses, you pay more in fees and don't help the network.

[OddEvenBets.com]

I installed new bitcoin node and get new address like "3xxx.."

How can I configurate node for Legacy address?

Why would you do that? Nested Segwit addresses (3xxx...) are 26% cheaper to send and you also help the network.

There are also NO downsides or negative points on doing this. Meanwhile, on Legacy addresses, you pay more in fees and don't help the network.

Because my script not use BTC about 6 month.. I adding BTC again.
In this case I will be use 3xxx.. I did not know about it.

Need setup settxfee? (or new node calculate this fully automatic? )

[European Central Bank]

There are also NO downsides or negative points on doing this. Meanwhile, on Legacy addresses, you pay more in fees and don't help the network.

you're not buying into the good old 'anyone can spend' thing?. me neither.

however if you're interested in bitcoin forks, and there may well be others in future, sorting out segwit private keys has proven to be very problematic in certain cases.

if i was parking coins for a long time with the intention of picking up some future bonuses i'd stick with legacy myself.

[OddEvenBets.com]

There are also NO downsides or negative points on doing this. Meanwhile, on Legacy addresses, you pay more in fees and don't help the network.

you're not buying into the good old 'anyone can spend' thing?. me neither.

however if you're interested in bitcoin forks, and there may well be others in future, sorting out segwit private keys has proven to be very problematic in certain cases.

if i was parking coins for a long time with the intention of picking up some future bonuses i'd stick with legacy myself.

You are right, I have issue now and can not get my private key from Legacy address..

error code: -4
error message:
Private key for address 16gzd25KU6tU89YsNNbGbzshvx3512YL1h is not known

May be need wait full sync?

[European Central Bank]

May be need wait full sync?

nope. a private key is a private key. it doesn't need to be connected to anything or update the blockchain for that to be accessible.

i've never used a core wallet so i wouldn't know what the problem with that is.

[TryNinja]

This usually means that you didn't unlock your wallet (forgot or used the wrong password) or you don't own this address.

[HCP]

Ok, I installed new bitcoin node and get new address like "3xxx.."
How can I configurate node for Legacy address (I want use Legacy address)?

The "default" support for SegWit wallets was added in v0.16. Refer: https://bitcoincore.org/en/2018/02/26/release-0.16.0/#segwit-wallet

You can start the node using the -addresstype argument... it uses values of legacy, p2sh-segwit and bech32 to generate "1-type", "3-type" or "bc1-type" respectively... so you would use the command like this:

Code:

bitcoin-qt -addresstype=legacy

Or you would add this to your bitcoin.conf

Code:

addresstype=legacy

Doing this means that when you use getnewaddress or click the "+New" button on the "Receiving Addresses..." window in the GUI, you will get a "1-type" address.

[bob123]

if i was parking coins for a long time with the intention of picking up some future bonuses i'd stick with legacy myself.

You can't really regard cheap BTC forks as 'bonuses'.
Most of them are worh nothing and only bring the risk of getting private keys compromised by using their one and only wallet.
IMO this is a way too time-consuming process to be worth it.

error code: -4
error message:
Private key for address 16gzd25KU6tU89YsNNbGbzshvx3512YL1h is not known

May be need wait full sync?

If this address is indeed part of your wallet, you have to unlock your wallet first before being able to dump private keys. Use this command:

Code:

walletpassphrase "YourPassword" 600

If you did unlock your wallet prior to using the dumpprivkey-command, it seems like the private key to this address has NOT been created by your wallet.

Because my script not use BTC about 6 month.. I adding BTC again.
In this case I will be use 3xxx.. I did not know about it.

It is always better to update your scripts to match the current state of the technology (note that p2sh addresses (starting with 3..) have been available in the network since the very early early days already).
Using a legacy address simply because your script isn't updated yet, is kind of sad.

[European Central Bank]

You can't really regard cheap BTC forks as 'bonuses'.
Most of them are worh nothing and only bring the risk of getting private keys compromised by using their one and only wallet.
IMO this is a way too time-consuming process to be worth it.

i timed my dumps well and i have over 1 BTC to show for the forks that most people have never heard of. i would have missed out on most of that if i'd had a segwit address.

lightning may well not strike again but if i'm not a regular transactor then i'd rather pay a little more in fees for that one transaction out of my legacy address and leave my line cast just in case.

all anyone has to do is move their BTC out before doing anything fork related.

[bob123]

all anyone has to do is move their BTC out before doing anything fork related.

That's not as easy and convenient as it sounds. At least not if you aren't storing all of your holdings on a desktop or mobile wallet.
If one has a hardware wallet with multiple currencies, it would be a pain in the ass to completely move all funds out, setting up a new seed, moving all funds back in.
You will lose daily access to your old addresses (which might still be needed for signing messages). And you also have the problem of securely storing the coins while you are setting up a new seed.

If, for example, one is only storing his coins on a desktop wallet without many periodically transactions coming in, it is no hassle to change the seed and simply 'forget' about the old wallet/seed.
But for anyone who does need access to his old addresses for signing etc.. such a hassle simply is not worth the few bucks you gain with these forks.. especially nowadays..