Bitcoin Forum
January 29, 2020, 03:04:36 PM *
News: Latest Bitcoin Core release: 0.19.0.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: -addresstype=  (Read 138 times)
thejaytiesto
Legendary
*
Offline Offline

Activity: 1358
Merit: 1004


View Profile
April 05, 2018, 04:05:57 PM
 #1

Testing out the latest Bitcoin Core 0.16 now that I got some free time, and it seems it defaults to the nested format, then to the "bech32" format if the box is clicked within the "Receive" tab.

I was only able to use the legacy format when adding -addresstype=legacy to a shortcut, kind of annoying workaround. Is there any way to generate legacy addresses and segwit addresses at will without having to open and close the client? I can't find anything within the command line.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1580310276
Hero Member
*
Offline Offline

Posts: 1580310276

View Profile Personal Message (Offline)

Ignore
1580310276
Reply with quote  #2

1580310276
Report to moderator
achow101
Moderator
Legendary
*
Offline Offline

Activity: 2016
Merit: 3046


bc1qshxkrpe4arppq89fpzm6c0tpdvx5cfkve2c8kl


View Profile WWW
April 05, 2018, 04:48:55 PM
Merited by NeuroticFish (1), dbshck (1), RGBKey (1)
 #2

Bitcoin Core 0.16 intentionally makes it more difficult to generate legacy addresses because we want to move towards segwit by default (particularly bech32). Thus there isn't really an easy way to make legacy addresses from within the GUI.

However you can use the debug console (or RPC interface, i.e. bitcoin-cli) to generate legacy addresses when -addresstype is not set to legacy. getnewaddress has a new address type parameter that lets you specify what type of address to generate.

RGBKey
Hero Member
*****
Offline Offline

Activity: 854
Merit: 630


rgbkey.github.io/pgp.txt


View Profile WWW
April 06, 2018, 02:25:48 AM
 #3

Adding to achow's comment, the point of upgrading software is to make it better. Bitcoin Core 0.16 is an upgrade, because it provides you with addresses that use up less space and therefore are cheaper to transact with, and also keep blocks smaller. That's a straight upgrade, and there's hardly any downside to it.
HCP
Legendary
*
Offline Offline

Activity: 1232
Merit: 2178

<insert witty quote here>


View Profile
April 06, 2018, 04:23:14 AM
 #4

That's a straight upgrade, and there's hardly any downside to it.
Except the large number of services that currently don't support bech32 addresses Wink #devilsAdvocate

Seriously tho, it is indeed a catch-22 situation... services won't start using bech32 until there is widespread adoption among users, users won't start using bech32 until there is widespread adoption among services Roll Eyes Undecided

Personally, I commend the Bitcoin Core team for forging ahead and "encouraging" the migration to SegWit and bech32.

RGBKey
Hero Member
*****
Offline Offline

Activity: 854
Merit: 630


rgbkey.github.io/pgp.txt


View Profile WWW
April 06, 2018, 04:59:04 AM
 #5

That's a straight upgrade, and there's hardly any downside to it.
Except the large number of services that currently don't support bech32 addresses Wink #devilsAdvocate

Seriously tho, it is indeed a catch-22 situation... services won't start using bech32 until there is widespread adoption among users, users won't start using bech32 until there is widespread adoption among services Roll Eyes Undecided

Personally, I commend the Bitcoin Core team for forging ahead and "encouraging" the migration to SegWit and bech32.


I'm talking about segwit. Wrapped P2WKH addresses are still backwards compatible and are described by what I said above. Doesn't have to be bech32, but I have seen an increasing amount of adoption recently.
bob123
Legendary
*
Offline Offline

Activity: 1134
Merit: 1652



View Profile WWW
April 06, 2018, 11:28:49 AM
 #6

I'm talking about segwit. Wrapped P2WKH addresses are still backwards compatible and are described by what I said above. Doesn't have to be bech32, but I have seen an increasing amount of adoption recently.

Segwit nested into P2SH was thought as a way of transition from legacy to segwit (bech32).
While nested segwit does reduce the transaction weight, it is still not as efficient as bech32.

Changing user habits is a tedious process. Moving from legacy to nested segwit is definetely a step in the right direction.
But the goal should be to get widespread bech32 adoption. It doesn't just improve the user experience, but also contributes to the overall network health.


@OP:
Is there a particular reason you want to use an legacy addresse?
General rejection towards segwit?

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!