Bitcoin 0.12 release

[Jet Cash]

2016-02-01
-----------
- Release 0.12.0 final (aim)

Wladimir

I really want to try this upgrade. Are we still on-target for it to be available tomorrow?

[1714872821]

1714872821

[1714872821]

1714872821

[1714872821]

1714872821

[1714872821]

1714872821

[1714872821]

1714872821

[Carlton Banks]

Go to https://bitcoin.org/bin/bitcoin-core-0.12.0/ if you would like to try the release candidate today. I think they're up to rc2 now.

[Jet Cash]

Thanks for that link, but we seem so close to the real thing, that I thought I'd wait. As a relative newbie to Bitcoin, I don't feel capable of resolving any oddities in the release candidate. I'm keen to try pruning on a second computer for example.

[Carlton Banks]

Well, the irony there is that if you did discover an oddity, the development team (and any fellow sufferers) would likely really appreciate you reporting it on https://github/bitcoin/bitcoin (having checked first the issue has not already been identified). Whether that constitutes speeding the release up or slowing it down is subjective ("but it's more work to fix" v.s. "but known bugs==unfinished release"), but I can tell you that the software seems pretty robust at both rc1 & rc2 for me on Xen/Debian Linux.

[pedrog]

I've also been running rc1 on Debian without any issue, syncing speed has improved a lot, and wallet now available with pruning mode enable.

Updating to rc2.

[achow101]

I think there will be an rc3 that will come out this week. Then the final version will be next week.

[unamis76]

It seems that block relaying is still disabled with pruned nodes, unfortunately. I'll be skipping these RC's. One thing at a time, I guess... Good that it can be used as a wallet, pretty handy for those who like to use Core as their daily wallet.

[Moloch]

I've also been running rc1 on Debian without any issue, syncing speed has improved a lot, and wallet now available with pruning mode enable.

Updating to rc2.

Have you tried running in pruned mode yet?  I'm curious how much disk space bitcoin uses with that feature enabled

[achow101]

It seems that block relaying is still disabled with pruned nodes, unfortunately. I'll be skipping these RC's. One thing at a time, I guess... Good that it can be used as a wallet, pretty handy for those who like to use Core as their daily wallet.

It is not disabled. New blocks will be relayed by pruned nodes. Says it here: https://github.com/bitcoin/bitcoin/blob/0.12/doc/release-notes.md#direct-headers-announcement-bip-130

[Carlton Banks]

Good that it can be used as a wallet, pretty handy for those who like to use Core as their daily wallet.

Possibly a 2016 LTE phone could be capable of running 0.12 in pruned mode. Seems inevitable that will happen at some point, if not this year.

[unamis76]

It seems that block relaying is still disabled with pruned nodes, unfortunately. I'll be skipping these RC's. One thing at a time, I guess... Good that it can be used as a wallet, pretty handy for those who like to use Core as their daily wallet.

It is not disabled. New blocks will be relayed by pruned nodes. Says it here: https://github.com/bitcoin/bitcoin/blob/0.12/doc/release-notes.md#direct-headers-announcement-bip-130

Guess I messed that section on the release notes. I went straight ahead to the pruning part to see if block relaying was enabled or not and it redirects to the release notes of v0.11.0, so I assumed that everything related to pruning was still pretty much the same as it is on 0.11. My bad

Regarding BIP 130, all clients 0.10+ support this? That's what I gather from reading it...

Additional constraints

As support for sendheaders is optional, software that implements this may also optionally impose additional constraints, such as only honoring sendheaders messages shortly after a connection is established.

Backward compatibility

Older clients remain fully compatible and interoperable after this change.

Good that it can be used as a wallet, pretty handy for those who like to use Core as their daily wallet.

Possibly a 2016 LTE phone could be capable of running 0.12 in pruned mode. Seems inevitable that will happen at some point, if not this year.

That wouldn't be bad at all

[achow101]

Guess I messed that section on the release notes. I went straight ahead to the pruning part to see if block relaying was enabled or not and it redirects to the release notes of v0.11.0, so I assumed that everything related to pruning was still pretty much the same as it is on 0.11. My bad

Regarding BIP 130, all clients 0.10+ support this? That's what I gather from reading it...

No, only 0.12+ because the sendHeaders message does not exist prior to 0.12.

[unamis76]

Guess I messed that section on the release notes. I went straight ahead to the pruning part to see if block relaying was enabled or not and it redirects to the release notes of v0.11.0, so I assumed that everything related to pruning was still pretty much the same as it is on 0.11. My bad

Regarding BIP 130, all clients 0.10+ support this? That's what I gather from reading it...

No, only 0.12+ because the sendHeaders message does not exist prior to 0.12.

Then we're back to square one, at least until pretty much everyone updates. Good thing about this it will probably make most people update

[rikrikrik]

Will the pruneing reduce the 60GB needed atm?

[unamis76]

Will the pruneing reduce the 60GB needed atm?

Yes, a pruned Core install takes much less space

[Erkallys]

Will the pruneing reduce the 60GB needed atm?

Yes, a pruned Core install takes much less space

How many GB can you save with this feature ? Also, will the pruned nodes still be considered as full nodes ? I'm pretty sure that the asnwer is no, but maybe...

[Carlton Banks]

Will the pruneing reduce the 60GB needed atm?

Yes, a pruned Core install takes much less space

How many GB can you save with this feature ? Also, will the pruned nodes still be considered as full nodes ? I'm pretty sure that the asnwer is no, but maybe...

With prune=550, the blocks and chainstate folder use about 2GB in total.

[Erkallys]

Will the pruneing reduce the 60GB needed atm?

Yes, a pruned Core install takes much less space

How many GB can you save with this feature ? Also, will the pruned nodes still be considered as full nodes ? I'm pretty sure that the asnwer is no, but maybe...

With prune=550, the blocks and chainstate folder use about 2GB in total.

Wow ! That's awesome ! And what about the full node status of the Bitcoin Core wallet ? With such a pruning, I'm sure that it is no longer considered as a full node, but maybe, with some magic...

[shorena]

Will the pruneing reduce the 60GB needed atm?

Yes, a pruned Core install takes much less space

How many GB can you save with this feature ? Also, will the pruned nodes still be considered as full nodes ? I'm pretty sure that the asnwer is no, but maybe...

With prune=550, the blocks and chainstate folder use about 2GB in total.

Wow ! That's awesome ! And what about the full node status of the Bitcoin Core wallet ? With such a pruning, I'm sure that it is no longer considered as a full node, but maybe, with some magic...

You still:

# verify all transactions
# verify all blocks
# relay transactions
# relay recent blocks (not old ones though)

the only thing you cant do with a purned node is help someone else to become a node, but thats not a requirement of a full node IMHO.

[rikrikrik]

Wow , now to post a question for rokos