Bitcoin 0.12 release

[Jet Cash]

The two disadvantages to running a full node seem to be storage and bandwidth (unless you run some cpu intensive programs). Storage isn't really a problem with modern hard drives. So bandwidth seems to be the big disincentive. At the moment I'm running a full node for around eight hours a day with no inbound connections. This is part of my mobile computing research. Hopefully, this is of some samll benefit to the Bitcoin system.

[1713562463]

1713562463

[1713562463]

1713562463

[TierNolan]

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

It should fallback to inv messages in that case.  Is there a reason for not doing that?

[achow101]

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

It should fallback to inv messages in that case.  Is there a reason for not doing that?

Not sure. That is just what I understood from the release notes and the bip. I suppose a more definitive answer could be gotten by looking at the code.

[TierNolan]

Not sure. That is just what I understood from the release notes and the bip. I suppose a more definitive answer could be gotten by looking at the code.

It could just be that they assume that most will update reasonably quickly.  Once most people are using 0.12, pruning nodes will be connected to 0.12 nodes anyway.

It looks like they have a "revert to inv" flag which is set if the node doesn't prefer headers.

https://github.com/bitcoin/bitcoin/blob/master/src/main.cpp#L5411

The only thing the fPruneMode flag does is stop it going back to far when sending blocks.  So, I guess, nevermind then .

[Karartma1]

This could be the greatest plus thing we need and then I would be more than happy in contributing again.
When you talk about future, how far is this future? thanks 

I think it would be done now, if not for all the drama in the last year.

In 0.12 you can run a pruned node and you'll at least relay blocks on the tip.

I hope to see more sophistication maybe towards then end of the year; I'm hesitant to give any concrete numbers in the current climate.

In any case something like theymos said sound awesome to me, maybe because I first heard the word Bitcoin linked to Bittorrent (I don't even remember how and when).
Don't worry about giving some dates, no rush. Let the talking continue. Thanks

[watashi-kokoto]

We tested rc5 on Debian. it seems to work ok

[MedaR]

Can someone please post Bitcoin.conf? I'm not sure how this must look like now.
I'm interested for prune mode..I don't want synchronization 7 years..
as i understood this is gonna take about 2 gb space on hd, is this stable and safe?

I have downloaded version for Windows , 32 bit.
https://bitcoin.org/bin/bitcoin-core-0.12.0/

[7788bitcoin]

Can someone post please Bitcoin.conf? I'm not sure how this must look like now.
I'm interested for prune mode..I don't want synchronization 7 years..
as i understood this is gonna take about 2 gb space on hd, is this stable and safe?

I have downloaded version for Windows , 32 bit.
https://bitcoin.org/bin/bitcoin-core-0.12.0/

Just create a shortcut with the "Target" changed to "C:\Program Files\Bitcoin\bitcoin-qt.exe -prune=8000" (as an example). Just adding the "-prune=8000" at the end. 8000 means 8GB.

By the way, you will still need to download the entire 50GB blockchain, and the software prune the chain as it is being downloaded.

[MedaR]

Can someone post please Bitcoin.conf? I'm not sure how this must look like now.
I'm interested for prune mode..I don't want synchronization 7 years..
as i understood this is gonna take about 2 gb space on hd, is this stable and safe?

I have downloaded version for Windows , 32 bit.
https://bitcoin.org/bin/bitcoin-core-0.12.0/

Just create a shortcut with the "Target" changed to "C:\Program Files\Bitcoin\bitcoin-qt.exe -prune=8000" (as an example). Just adding the "-prune=8000" at the end. 8000 means 8GB.

By the way, you will still need to download the entire 50GB blockchain, and the software prune the chain as it is being downloaded.

The name  "C:\Program Files\Bitcoin\bitcoin-qt.exe -prune=8000" specified in the Target box is not valid.Make sure..

But i also need to download entire blockchain so i have much time to figur it out. Very stupid from me.

[Thura]

Bitcoin Core 0.12.0 release candidate 5 binaries available:

http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-February/012448.html

[thejaytiesto]

Bitcoin Core 0.12.0 release candidate 5 binaries available:

http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-February/012448.html

Im very tempted to try it by myself because I can't wait to test the increased speed on the software, but I think right now it would be a waste of time for me and I would rather wait. They should be releasing it pretty soon. Hopefully this is the last RC version but I don't mind a bunch of RC versions as long as the final is as solid as possible.

[mmortal03]

Can someone please post Bitcoin.conf? I'm not sure how this must look like now.
I'm interested for prune mode..I don't want synchronization 7 years..
as i understood this is gonna take about 2 gb space on hd, is this stable and safe?

I have downloaded version for Windows , 32 bit.
https://bitcoin.org/bin/bitcoin-core-0.12.0/

You still have to synchronize the full 7 years with a pruned node.

[achow101]

Bitcoin 0.12.0 has finally been tagged. The official release should be in a day or two after all of the gitian builds are finished.

[pereira4]

Bitcoin 0.12.0 has finally been tagged. The official release should be in a day or two after all of the gitian builds are finished.

I saw the news on reddit, I cant wait to see how fast it is compared to the current release thanks to the improvements.
Actually gmaxwell said that it's done and that version is the final one and that if there is any problems, they will fix it on 0.12.1

https://www.reddit.com/r/Bitcoin/comments/46f67s/bitcoin_v0120_has_been_tagged_for_release/d05hmkz

But I will wait until its listed here just in case:

https://bitcoin.org/en/bitcoin-core/

So please someone update the website soon.

[theymos]

But I will wait until its listed here just in case:

https://bitcoin.org/en/bitcoin-core/

So please someone update the website soon.

Bitcoin.org will probably update sometime between today and Monday - I'm not sure when.

If you're really itching to try 0.12.0, I uploaded the binaries here:
https://mega.nz/#F!Q9MUgQZD!Wq44qDAtHzGEvifAxQIZbA

Verify them against the available gitian sigs. (Ie. look at the out_manifest section of the assert files in the gitian.sigs repo, compare those hashes to the files you download, and also gpg-verify the signatures on the assert files.)

[Watercooler]

Looking forward upgrading to the final 0.12.0 version, been running the 0.12.0RC versions for several weeks now
without any problems 

[jmintuck1912]

Core RC3 is good so far. I am synching right now, and I believe when I launched it, was 7 years and a few weeks behind. 10 minutes later, 5 years behind. SEEMS better at synching now than before.

[achow101]

Core RC3 is good so far. I am synching right now, and I believe when I launched it, was 7 years and a few weeks behind. 10 minutes later, 5 years behind. SEEMS better at synching now than before.

Use the latest official release, rc5, or grab a build of the final. You can use Theymos's posted above or use mine at https://github.com/achow101/bitcoin/releases/tag/v0.12.0. Make sure you verify the checksums against the sigs at https://github.com/bitcoin/gitian.sigs.

[dooglus]

I'm interested for prune mode..I don't want synchronization 7 years..

You still have to synchronize the full 7 years with a pruned node.

I expect someone will make a torrent available of a fully pruned .bitcoin/ folder. You would need to trust them, but it would be a good fast way of getting your "full node" initialized if you do.

[Jet Cash]

I expect someone will make a torrent available of a fully pruned .bitcoin/ folder. You would need to trust them, but it would be a good fast way of getting your "full node" initialized if you do.

I don't think that will work, as you have to customise the pruning to your wallet. You can also set the pruning size, and I don't think all people will use the same value.