Bitcoin Forum
April 20, 2018, 01:31:19 AM *
News: Latest stable version of Bitcoin Core: 0.16.0  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: 1 2 [All]
  Print  
Author Topic: Bitcoin Core 0.16.0 binaries available  (Read 242 times)
Royse777
Hero Member
*****
Offline Offline

Activity: 684
Merit: 554


★ Only one,but a lion ★


View Profile
February 26, 2018, 10:50:55 AM
Merited by LoyceV (1)
 #1

https://bitcoin.org/bin/bitcoin-core-0.16.0/

Check the sha256sums.asc pgp yourself pls. I checked and with me the checksum was correct.

If i am correct this should have full Segwit support.

«He who works all day,there is no time to make money.» John Rockefeller
1524187879
Hero Member
*
Offline Offline

Posts: 1524187879

View Profile Personal Message (Offline)

Ignore
1524187879
Reply with quote  #2

1524187879
Report to moderator
1524187879
Hero Member
*
Offline Offline

Posts: 1524187879

View Profile Personal Message (Offline)

Ignore
1524187879
Reply with quote  #2

1524187879
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1524187879
Hero Member
*
Offline Offline

Posts: 1524187879

View Profile Personal Message (Offline)

Ignore
1524187879
Reply with quote  #2

1524187879
Report to moderator
jrian
Jr. Member
*
Offline Offline

Activity: 35
Merit: 4


View Profile
February 26, 2018, 12:59:08 PM
 #2

https://bitcoin.org/bin/bitcoin-core-0.16.0/

Check the sha256sums.asc pgp yourself pls. I checked and with me the checksum was correct.

If i am correct this should have full Segwit support.


Segwit by default, and you can choose Bech32. Will install it right now Smiley

ps. someone have to change  this news:
Code:
News: Latest stable version of Bitcoin Core: 0.15.1 (https://bitcoin.org/en/download)
Royse777
Hero Member
*****
Offline Offline

Activity: 684
Merit: 554


★ Only one,but a lion ★


View Profile
February 26, 2018, 01:22:07 PM
 #3

https://bitcoin.org/bin/bitcoin-core-0.16.0/

Check the sha256sums.asc pgp yourself pls. I checked and with me the checksum was correct.

If i am correct this should have full Segwit support.


Segwit by default, and you can choose Bech32. Will install it right now Smiley

ps. someone have to change  this news:

Code:
News: Latest stable version of Bitcoin Core: 0.15.1 (https://bitcoin.org/en/download)

Don't know if it is a stable version yet

«He who works all day,there is no time to make money.» John Rockefeller
jrian
Jr. Member
*
Offline Offline

Activity: 35
Merit: 4


View Profile
February 26, 2018, 02:28:05 PM
 #4

Don't know if it is a stable version yet


Its stable. Here is changes: https://bitcoin.org/en/release/v0.16.0
cellard
Legendary
*
Offline Offline

Activity: 980
Merit: 1050


View Profile
February 26, 2018, 03:43:22 PM
 #5

Don't know if it is a stable version yet


Its stable. Here is changes: https://bitcoin.org/en/release/v0.16.0

Don't expect the news to be updated anytime soon. Whoever is in charge of that takes a long time to update when new versions are out. Possibly mid week or even next week.

Anyone that has an old wallet.dat from early Bitcoin-qt days has tested it by the way? Any problems?

Do legacy and segwit addresses show up fine the GUI? got some screenshots to see how it looks like? I can't install it currently, im out and will not be back home for a while.

       ▀
   ▄▄▄   ▄▀
   ███ ▄▄▄▄  ██
       ████
    ▄  ▀▀▀▀
▄▄
      ██    ▀▀
██▄█▄▄▄████████
▄▄▄▄▄▄▄▄▀▀███▀▀▀
██████████████████
████▄▀▄▀▄▀███▀▀▀▀▀
████▄▀▄▀▄▀███ ▀
████▄▀▄▀▄▀████████
▀█████████████████
]
,CoinPayments,
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
TheQuin
Hero Member
*****
Offline Offline

Activity: 518
Merit: 554


Freebitco.in Forum Dude https://bit.ly/2I9BVS2


View Profile WWW
February 26, 2018, 03:53:50 PM
 #6

Anyone that has an old wallet.dat from early Bitcoin-qt days has tested it by the way? Any problems?

Do legacy and segwit addresses show up fine the GUI? got some screenshots to see how it looks like? I can't install it currently, im out and will not be back home for a while.

The old wallet loaded OK but it is empty so I couldn't test beyond that. To use Segwit you need a new wallet anyway so I renamed that and it made a new Segwit one automatically. Getting a new receiving address give a Segwit one start '3'. I'm still trying to work out how to get a bech32 address.

Edit: Official release thread has appeared https://bitcointalk.org/index.php?topic=3024763.0

achow101
Moderator
Legendary
*
Offline Offline

Activity: 1372
Merit: 1269


3F1Y9yquzvY6RWvKbw2n2zeo9V5mvBhADU


View Profile WWW
February 26, 2018, 04:10:37 PM
 #7

To use Segwit you need a new wallet anyway
It shouldn't.

I'm still trying to work out how to get a bech32 address.
Start with (or add to your bitcoin.conf) -addresstype=bech32. Or in the Receive tab, check the "Bech32 address" checkbox and get a new address from there.

BitCryptex
Member
**
Offline Offline

Activity: 182
Merit: 29

Quit complaining about merit, deal with it.


View Profile WWW
February 26, 2018, 04:18:26 PM
Merited by DooMAD (2)
 #8

This version is definitely a huge step forward. I was quite surprised when I saw news about the new version. I browsed Github some time ago and I saw a discussion where someone said that 0.16.0 was supposed to be released somewhere around May. Full SegWit support was one of the most demanded features. What a shame that BIP 173 addresses aren't default ones. I know that there might be still some compatibility issues but it could at least force exchanges, wallet providers and other services to start supporting them.

Getting a new receiving address give a Segwit one start '3'. I'm still trying to work out how to get a bech32 address.

If you still can't find it here's a picture of it.

#BitcoinCore
Sr. Member
****
Offline Offline

Activity: 392
Merit: 287


✪FOXBIT | Exchange✪


View Profile
February 26, 2018, 04:23:59 PM
 #9

But the private keys of the segwit addresses (both P2SH and bech32) are the same as those of a legacy address when you export a private key from a segwit address in Bitcoin Core and import into Electrum, it appears that you imported a legacy address instead of segwit P2SH or bech32). Do the tests yourself






███████████   ▄▄███████▄▄    ▄█▄      ▄█▄   █████████▄▄   ████  ██████████████
████▀▀▀▀▀▀▀  █████████████  ▀████▄  ▄████▀  ████▀▀▀▀████  ████  ▀▀▀▀▀████▀▀▀▀▀
████        ███████████████   ▀████████▀    ████    ▄███  ████       ████
█████████   ███████████████     ██████      ███████████   ████       ████
████▀▀▀▀▀   ███████████████   ▄████████▄    ████    ▀███  ████       ████
████        ▄█████████████  ▄████▀  ▀████▄  ████▄▄▄▄████  ████       ████
████      ▄███ ▀▀██████▀▀    ▀█▀      ▀█▀   █████████▀▀   ████       ████
         ▐███▌       ▄▄▄▄
         ▐█████▄▄▄███▀  ▀█▄
          ▀██████████▄▀▀▀▀█▄
            ▀█████▀▀
██
║║
║║
║║
██
██
██
║║
║║
║║
██
██
║║
║║
║║
██
██
██
║║
║║
║║
██

▄████████████████▄
███████████▀▀▀▀███
█████████▀     ███
█████████   ██████
███████        ███
█████████   ██████
█████████   ██████
▀████████   █████▀



 █████████████████
████████▀██████████
████████   ▀███████
████████   ▄███████
████████▄██████████
 █████████████████
TheQuin
Hero Member
*****
Offline Offline

Activity: 518
Merit: 554


Freebitco.in Forum Dude https://bit.ly/2I9BVS2


View Profile WWW
February 26, 2018, 04:30:27 PM
 #10

To use Segwit you need a new wallet anyway
It shouldn't.

I'm still trying to work out how to get a bech32 address.
Start with (or add to your bitcoin.conf) -addresstype=bech32. Or in the Receive tab, check the "Bech32 address" checkbox and get a new address from there.

Thanks for clearing up my misunderstanding. I just opened with my old wallet and it all works.

achow101
Moderator
Legendary
*
Offline Offline

Activity: 1372
Merit: 1269


3F1Y9yquzvY6RWvKbw2n2zeo9V5mvBhADU


View Profile WWW
February 26, 2018, 04:33:55 PM
Merited by Xynerise (1)
 #11

But the private keys of the segwit addresses (both P2SH and bech32) are the same as those of a legacy address when you export a private key from a segwit address in Bitcoin Core and import into Electrum, it appears that you imported a legacy address instead of segwit P2SH or bech32). Do the tests yourself
That is a known problem. Fixing it requires a new private key format because the private keys do not actually specify what kind of address you should create with them. It is important to note that private keys only create public keys, and a public key can be transformed into several different addresses now. The private key does not specify what kind of address to create from the public key.

Carlton Banks
Legendary
*
Offline Offline

Activity: 1974
Merit: 1140



View Profile
February 26, 2018, 04:50:37 PM
 #12

But the private keys of the segwit addresses (both P2SH and bech32) are the same as those of a legacy address when you export a private key from a segwit address in Bitcoin Core and import into Electrum, it appears that you imported a legacy address instead of segwit P2SH or bech32). Do the tests yourself
That is a known problem. Fixing it requires a new private key format because the private keys do not actually specify what kind of address you should create with them. It is important to note that private keys only create public keys, and a public key can be transformed into several different addresses now. The private key does not specify what kind of address to create from the public key.

What prevents wallet software from spending from non-segwit addresses using the segwit address corresponding to a common public key?

Vires in numeris
#BitcoinCore
Sr. Member
****
Offline Offline

Activity: 392
Merit: 287


✪FOXBIT | Exchange✪


View Profile
February 26, 2018, 05:01:31 PM
 #13

Quote
That is a known problem. Fixing it requires a new private key format because the private keys do not actually specify what kind of address you should create with them. It is important to note that private keys only create public keys, and a public key can be transformed into several different addresses now. The private key does not specify what kind of address to create from the public key.
Yes I know this, when we give the command RPC dumpwallet "destination", in the document just below the private keys, each segwit P2SH address has its redemscript but I do not know how to use it and I do not even know what the utility of that redemscript is. The Electrum wallet shows the new private format of the private keys of the segwit addresses, but no other wallet recognizes, only Electrum, if we import bitcoin-QT a bech32 private key generated in the Electrum of the error, because bitcoin-QT does not recognize the private key of bech32 address of Electrum






███████████   ▄▄███████▄▄    ▄█▄      ▄█▄   █████████▄▄   ████  ██████████████
████▀▀▀▀▀▀▀  █████████████  ▀████▄  ▄████▀  ████▀▀▀▀████  ████  ▀▀▀▀▀████▀▀▀▀▀
████        ███████████████   ▀████████▀    ████    ▄███  ████       ████
█████████   ███████████████     ██████      ███████████   ████       ████
████▀▀▀▀▀   ███████████████   ▄████████▄    ████    ▀███  ████       ████
████        ▄█████████████  ▄████▀  ▀████▄  ████▄▄▄▄████  ████       ████
████      ▄███ ▀▀██████▀▀    ▀█▀      ▀█▀   █████████▀▀   ████       ████
         ▐███▌       ▄▄▄▄
         ▐█████▄▄▄███▀  ▀█▄
          ▀██████████▄▀▀▀▀█▄
            ▀█████▀▀
██
║║
║║
║║
██
██
██
║║
║║
║║
██
██
║║
║║
║║
██
██
██
║║
║║
║║
██

▄████████████████▄
███████████▀▀▀▀███
█████████▀     ███
█████████   ██████
███████        ███
█████████   ██████
█████████   ██████
▀████████   █████▀



 █████████████████
████████▀██████████
████████   ▀███████
████████   ▄███████
████████▄██████████
 █████████████████
cellard
Legendary
*
Offline Offline

Activity: 980
Merit: 1050


View Profile
February 26, 2018, 06:32:51 PM
 #14

Anyone that has an old wallet.dat from early Bitcoin-qt days has tested it by the way? Any problems?

Do legacy and segwit addresses show up fine the GUI? got some screenshots to see how it looks like? I can't install it currently, im out and will not be back home for a while.

The old wallet loaded OK but it is empty so I couldn't test beyond that. To use Segwit you need a new wallet anyway so I renamed that and it made a new Segwit one automatically. Getting a new receiving address give a Segwit one start '3'. I'm still trying to work out how to get a bech32 address.

Edit: Official release thread has appeared https://bitcointalk.org/index.php?topic=3024763.0


Well I remember reading achow101 saying that if you had an old bitcoin-qt wallet.dat and opened it with 0.16 it will automatically convert it to the new format and you don't need to do anything annoying like creating an empty one and sending all of your coins over the new wallet.dat which is hell.

And also I got some coins on a bech32 electrum address, I've read I can't export it because it will not work properly... when this will be fixed?

I guess I will leave them on electrum's wallet for the time being.

Im also still paranoid about the new format. I assume the seed is impossible to see and therefore safer than electrum's hd format right?

       ▀
   ▄▄▄   ▄▀
   ███ ▄▄▄▄  ██
       ████
    ▄  ▀▀▀▀
▄▄
      ██    ▀▀
██▄█▄▄▄████████
▄▄▄▄▄▄▄▄▀▀███▀▀▀
██████████████████
████▄▀▄▀▄▀███▀▀▀▀▀
████▄▀▄▀▄▀███ ▀
████▄▀▄▀▄▀████████
▀█████████████████
]
,CoinPayments,
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
RGBKey
Hero Member
*****
Offline Offline

Activity: 700
Merit: 589


PGP: 5688A943


View Profile WWW
February 26, 2018, 08:04:10 PM
 #15

Anyone that has an old wallet.dat from early Bitcoin-qt days has tested it by the way? Any problems?

Do legacy and segwit addresses show up fine the GUI? got some screenshots to see how it looks like? I can't install it currently, im out and will not be back home for a while.

The old wallet loaded OK but it is empty so I couldn't test beyond that. To use Segwit you need a new wallet anyway so I renamed that and it made a new Segwit one automatically. Getting a new receiving address give a Segwit one start '3'. I'm still trying to work out how to get a bech32 address.

Edit: Official release thread has appeared https://bitcointalk.org/index.php?topic=3024763.0


Well I remember reading achow101 saying that if you had an old bitcoin-qt wallet.dat and opened it with 0.16 it will automatically convert it to the new format and you don't need to do anything annoying like creating an empty one and sending all of your coins over the new wallet.dat which is hell.

And also I got some coins on a bech32 electrum address, I've read I can't export it because it will not work properly... when this will be fixed?

I guess I will leave them on electrum's wallet for the time being.

Im also still paranoid about the new format. I assume the seed is impossible to see and therefore safer than electrum's hd format right?

What do you mean "impossible to see"? The seed still has to be stored in the encrypted wallet.dat

EcuaMobi
Legendary
*
Offline Offline

Activity: 1400
Merit: 1171


https://Ecua.Mobi


View Profile WWW
February 26, 2018, 08:19:13 PM
 #16

I've updated my Bitcoin Core to 0.16.0 and created a few new bech32 address with the command
Code:
getnewaddress -addresstype bech32

I've then tried to sign a message with that address but I get the error "The entered address does not refer to a key":

(Address cut in the screenshot for privacy reasons)

However, it is possible to sign and verify this kind of addresses with Electrum (as long as it's not multisign):

(Address cut in the screenshot for privacy reasons)

I can't find the official documentation regarding signing arbitrary messages with these addresses. Can anyone enlighten me?
Did electrum implement its own or an unofficial standard? Will this be supported by Core?

PGP: KeyBase.io/EcuaMobi [Verify / Encrypt] • 37D06E1D43EC62B874DD56868DAFD805AE6D5F7A
Bitcoin full node: node.ecua.mobiUserscripts for bitcointalk: Improved imagesShort URLs
Domains for sale: Current auctionFull list
TryNinja
Hero Member
*****
Online Online

Activity: 616
Merit: 592

ChipMixer's Badge of Honor


View Profile
February 26, 2018, 08:38:18 PM
 #17

I can't find the official documentation regarding signing arbitrary messages with these addresses. Can anyone enlighten me?
Did electrum implement its own or an unofficial standard? Will this be supported by Core?

That's all I could find with my limited knowledge:
My doubt, regarding signing in segwit address is if this is a "bug" and will soon be corrected, or is it an abandoned feature?
It is neither a bug nor an abandoned feature. It is just that we are still working on creating a more generalized signing scheme that lets people sign with things like P2SH addresses (e.g. sign with a multisig address). There is simply no standard yet for signing with such scripts or with Segwit.

Note that you don't actually sign with an address. You sign with a public-private keypair and your wallet interprets it as an address. Your wallet could just as easily interpret it as a segwit address. We are working on creating something that actually specifies the address type, and more generally, allows signing with scripts.

EcuaMobi
Legendary
*
Offline Offline

Activity: 1400
Merit: 1171


https://Ecua.Mobi


View Profile WWW
February 26, 2018, 08:43:54 PM
 #18

I can't find the official documentation regarding signing arbitrary messages with these addresses. Can anyone enlighten me?
Did electrum implement its own or an unofficial standard? Will this be supported by Core?

That's all I could find with my limited knowledge:
My doubt, regarding signing in segwit address is if this is a "bug" and will soon be corrected, or is it an abandoned feature?
It is neither a bug nor an abandoned feature. It is just that we are still working on creating a more generalized signing scheme that lets people sign with things like P2SH addresses (e.g. sign with a multisig address). There is simply no standard yet for signing with such scripts or with Segwit.

Note that you don't actually sign with an address. You sign with a public-private keypair and your wallet interprets it as an address. Your wallet could just as easily interpret it as a segwit address. We are working on creating something that actually specifies the address type, and more generally, allows signing with scripts.

I hadn't seen that. Thanks.
I wonder what electrum implemented if there's no standard yet. But I see that's been asked/wondered there

PGP: KeyBase.io/EcuaMobi [Verify / Encrypt] • 37D06E1D43EC62B874DD56868DAFD805AE6D5F7A
Bitcoin full node: node.ecua.mobiUserscripts for bitcointalk: Improved imagesShort URLs
Domains for sale: Current auctionFull list
achow101
Moderator
Legendary
*
Offline Offline

Activity: 1372
Merit: 1269


3F1Y9yquzvY6RWvKbw2n2zeo9V5mvBhADU


View Profile WWW
February 26, 2018, 11:58:43 PM
 #19

What prevents wallet software from spending from non-segwit addresses using the segwit address corresponding to a common public key?
Nothing. Whoops, misread that question.

Yes I know this, when we give the command RPC dumpwallet "destination", in the document just below the private keys, each segwit P2SH address has its redemscript but I do not know how to use it and I do not even know what the utility of that redemscript is. The Electrum wallet shows the new private format of the private keys of the segwit addresses, but no other wallet recognizes, only Electrum, if we import bitcoin-QT a bech32 private key generated in the Electrum of the error, because bitcoin-QT does not recognize the private key of bech32 address of Electrum
You can't use it in another wallet unless they support explicitly setting a redeemScript or explicitly saying that a given private key should be used for segwit.

Interwallet compatibility with importing/exporting private keys is not very good and it never really was something that was worked on in the past. There is ongoing work to standardize a format for segwit private keys.

Well I remember reading achow101 saying that if you had an old bitcoin-qt wallet.dat and opened it with 0.16 it will automatically convert it to the new format and you don't need to do anything annoying like creating an empty one and sending all of your coins over the new wallet.dat which is hell.
No, you either misunderstand or misremember what I said. It "converts" the wallet so that it can be used for segwit, but no actual conversion happens because nothing in the wallet format needs to change. It is partially backwards compatible; if you go back to too old a version (older than 0.13.1), your wallet won't work as you expect it to.

I hadn't seen that. Thanks.
I wonder what electrum implemented if there's no standard yet. But I see that's been asked/wondered there
Electrum tends to implement their own formats for things and not get them standardized. They have implemented their own segwit private key, public key, seed, and signature format which is specific only to Electrum (the signature format might work with Trezor).

fabianji
Jr. Member
*
Offline Offline

Activity: 70
Merit: 8


View Profile
February 27, 2018, 01:43:16 AM
 #20

https://bitcoin.org/bin/bitcoin-core-0.16.0/

Check the sha256sums.asc pgp yourself pls. I checked and with me the checksum was correct.

If i am correct this should have full Segwit support.

It does - plus a few smaller features that have been implemented like the bench32 address format and the "replace-by-fee" tag set as default.


▬▬▬▬ THRIVE ▬▬▬▬
THE PREMIUM DECENTRALIZED AD MARKETPLACE
[  Private Round | Jan 15th, 2018  ] (http://ico.thrivelabs.io)
Carlton Banks
Legendary
*
Offline Offline

Activity: 1974
Merit: 1140



View Profile
February 27, 2018, 10:26:56 AM
 #21

What prevents wallet software from spending from non-segwit addresses using the segwit address corresponding to a common public key?
Nothing.

So that means P2PKH or P2SH inputs could be spent respectively as P2WPKH or P2WSH? Transferring to segwit addresses isn't strictly necessary, as wallet software could be programmed to write transactions using the segwit address corresponding to the common public key of legacy addresses holding funds?

Vires in numeris
cellard
Legendary
*
Offline Offline

Activity: 980
Merit: 1050


View Profile
February 27, 2018, 03:23:31 PM
 #22

Anyone that has an old wallet.dat from early Bitcoin-qt days has tested it by the way? Any problems?

Do legacy and segwit addresses show up fine the GUI? got some screenshots to see how it looks like? I can't install it currently, im out and will not be back home for a while.

The old wallet loaded OK but it is empty so I couldn't test beyond that. To use Segwit you need a new wallet anyway so I renamed that and it made a new Segwit one automatically. Getting a new receiving address give a Segwit one start '3'. I'm still trying to work out how to get a bech32 address.

Edit: Official release thread has appeared https://bitcointalk.org/index.php?topic=3024763.0


Well I remember reading achow101 saying that if you had an old bitcoin-qt wallet.dat and opened it with 0.16 it will automatically convert it to the new format and you don't need to do anything annoying like creating an empty one and sending all of your coins over the new wallet.dat which is hell.

And also I got some coins on a bech32 electrum address, I've read I can't export it because it will not work properly... when this will be fixed?

I guess I will leave them on electrum's wallet for the time being.

Im also still paranoid about the new format. I assume the seed is impossible to see and therefore safer than electrum's hd format right?

What do you mean "impossible to see"? The seed still has to be stored in the encrypted wallet.dat

As far as I know, in Bitcoin Core is impossible to show the seed of the wallet for security reasons, while in Electrum is very easy to show the seed and it is shown even in the wizard when creating a wallet. Maybe there is a way to show it with Bitcoin Core on the command line, but I hope not, since it's pretty stupid, I think it just adds an huge exploit possibility. A hacker gets your seed and he gets all future addresses you create... not fun. I would never feel safe that way. Also seed derivation was possible with Electrum if you had a master public key and some other keys I think... im just too paranoid to even bother and I stick to the basics.

Im going to get rid of Electrum as soon as I install 0.16. If I can't import the keys I guess I will need to send the coins to myself.

       ▀
   ▄▄▄   ▄▀
   ███ ▄▄▄▄  ██
       ████
    ▄  ▀▀▀▀
▄▄
      ██    ▀▀
██▄█▄▄▄████████
▄▄▄▄▄▄▄▄▀▀███▀▀▀
██████████████████
████▄▀▄▀▄▀███▀▀▀▀▀
████▄▀▄▀▄▀███ ▀
████▄▀▄▀▄▀████████
▀█████████████████
]
,CoinPayments,
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
█████
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████ ██
█████
achow101
Moderator
Legendary
*
Offline Offline

Activity: 1372
Merit: 1269


3F1Y9yquzvY6RWvKbw2n2zeo9V5mvBhADU


View Profile WWW
February 27, 2018, 03:43:52 PM
 #23

So that means P2PKH or P2SH inputs could be spent respectively as P2WPKH or P2WSH? Transferring to segwit addresses isn't strictly necessary, as wallet software could be programmed to write transactions using the segwit address corresponding to the common public key of legacy addresses holding funds?
No, I misread your question.

The output type is specified by a script since addresses do not exist on the network. So P2PKH and P2SH outputs have a specific script that need to have specific input scriptsigs in order for them to be spent from validly. Likewise, P2WPKH and P2WSH outputs have their own output scripts which need to be spent in a specific way that is different from P2PKH and P2SH outputs.

#BitcoinCore
Sr. Member
****
Offline Offline

Activity: 392
Merit: 287


✪FOXBIT | Exchange✪


View Profile
February 27, 2018, 03:57:08 PM
 #24

Quote
As far as I know, in Bitcoin Core is impossible to show the seed of the wallet for security reasons, while in Electrum is very easy to show the seed and it is shown even in the wizard when creating a wallet. Maybe there is a way to show it with Bitcoin Core on the command line, but I hope not, since it's pretty stupid, I think it just adds an huge exploit possibility. A hacker gets your seed and he gets all future addresses you create... not fun. I would never feel safe that way. Also seed derivation was possible with Electrum if you had a master public key and some other keys I think... im just too paranoid to even bother and I stick to the basics.

Im going to get rid of Electrum as soon as I install 0.16. If I can't import the keys I guess I will need to send the coins to myself.
@cellard The core does not provide the seed of the wallet, but the master private key, and this master key is hidden and encrypted in wallet.dat, to have access to it you must export all the keys of the wallet at once giving the command in the console:
Code:
dumpwallet "destination"
the master key will be at the beginning of the document.






███████████   ▄▄███████▄▄    ▄█▄      ▄█▄   █████████▄▄   ████  ██████████████
████▀▀▀▀▀▀▀  █████████████  ▀████▄  ▄████▀  ████▀▀▀▀████  ████  ▀▀▀▀▀████▀▀▀▀▀
████        ███████████████   ▀████████▀    ████    ▄███  ████       ████
█████████   ███████████████     ██████      ███████████   ████       ████
████▀▀▀▀▀   ███████████████   ▄████████▄    ████    ▀███  ████       ████
████        ▄█████████████  ▄████▀  ▀████▄  ████▄▄▄▄████  ████       ████
████      ▄███ ▀▀██████▀▀    ▀█▀      ▀█▀   █████████▀▀   ████       ████
         ▐███▌       ▄▄▄▄
         ▐█████▄▄▄███▀  ▀█▄
          ▀██████████▄▀▀▀▀█▄
            ▀█████▀▀
██
║║
║║
║║
██
██
██
║║
║║
║║
██
██
║║
║║
║║
██
██
██
║║
║║
║║
██

▄████████████████▄
███████████▀▀▀▀███
█████████▀     ███
█████████   ██████
███████        ███
█████████   ██████
█████████   ██████
▀████████   █████▀



 █████████████████
████████▀██████████
████████   ▀███████
████████   ▄███████
████████▄██████████
 █████████████████
Pages: 1 2 [All]
  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!