Bitcoin Core version 0.13.0 Released

[achow101]

I don't understand anything about this Bitcoin core. Some one should please help out.

It's a Bitcoin wallet. It requires downloading and syncing the entire blockchain. To run, just download, install, and run. It does everything automatically.

[Meuh6879]

and you loose 90Go on your hard drive.  just to finalize the answer.

[awesome31312]

The other day somebody in the Armory subsection helped me update

I can't find the instructions to do that anymore, what do I do when I go on the page? There's no download button

[achow101]

The other day somebody in the Armory subsection helped me update

I can't find the instructions to do that anymore, what do I do when I go on the page? There's no download button

Click on one of the links to download the file of the same name. Choose the one for your OS. The zip and tar files are either just the binaries or the source. If you want the installer, download one of the other files (dmg or exe).

[Dabs]

and you loose 90Go on your hard drive.  just to finalize the answer.

That shrinks to about 2 to 3 GB if you use pruning; but you still have to go through the entire blockchain so watch out for bandwidth costs.

[Meuh6879]

and you loose 90Go on your hard drive.  just to finalize the answer.

That shrinks to about 2 to 3 GB if you use pruning; but you still have to go through the entire blockchain so watch out for bandwidth costs.

i need :
- import private
- restore wallet.dat
- mining

i can not prune.

[Real-Duke]

Did someone here manage to compile the update on a Raspberry PI or a banana PI?
No problem with the older builds but when I try with 0.13.0 it stops after ~30min
End of Log:

Code:

 CXX      script/libbitcoinconsensus_la-script_error.lo
  CXX      libbitcoinconsensus_la-uint256.lo
  CXX      libbitcoinconsensus_la-utilstrencodings.lo
make[3]: Entering directory '/root/bitcoin/bitcoin/src/secp256k1'
gcc -I. -g -O2 -Wall -Wextra -Wno-unused-function -c src/gen_context.c -o gen_context.o
gcc gen_context.o -o gen_context
./gen_context
  CC       src/libsecp256k1_la-secp256k1.lo
  CCLD     libsecp256k1.la
make[3]: Leaving directory '/root/bitcoin/bitcoin/src/secp256k1'
  CXXLD    libbitcoinconsensus.la
  CXX      bitcoind-bitcoind.o
  CXX      libbitcoin_server_a-addrman.o
  CXX      libbitcoin_server_a-bloom.o
  CXX      libbitcoin_server_a-blockencodings.o
  CXX      libbitcoin_server_a-chain.o
  CXX      libbitcoin_server_a-checkpoints.o
  CXX      libbitcoin_server_a-httprpc.o
  CXX      libbitcoin_server_a-httpserver.o
  CXX      libbitcoin_server_a-init.o
  CXX      libbitcoin_server_a-dbwrapper.o
  CXX      libbitcoin_server_a-main.o
g++: internal compiler error: Getötet (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.9/README.Bugs> for instructions.
Makefile:5064: recipe for target 'libbitcoin_server_a-main.o' failed
make[2]: *** [libbitcoin_server_a-main.o] Error 4
make[2]: Leaving directory '/root/bitcoin/bitcoin/src'
Makefile:8338: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/root/bitcoin/bitcoin/src'
Makefile:667: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
make  1552,75s user 54,73s system 98% cpu 27:05,93 total
2 root@bitcoinnode ~/bitcoin/bitcoin (git)-[v0.13.0] #   

Used Compiler:

Code:

root@bitcoinnode ~ # g++ --version
g++ (Debian 4.9.2-10) 4.9.2
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


1 root@bitcoinnode ~ # gcc -v                                                Sad
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: ../src/configure -v --with-pkgversion='Debian 4.9.2-10' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.9 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libitm --disable-libquadmath --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-armhf --with-arch-directory=arm --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-sjlj-exceptions --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=hard --with-mode=thumb --enable-checking=release --build=arm-linux-gnueabihf --host=arm-linux-gnueabihf --target=arm-linux-gnueabihf
Thread model: posix
gcc version 4.9.2 (Debian 4.9.2-10)

I have posted the same logs some time ago in our german main thread about the banana pi bitcoin node: https://bitcointalk.org/index.php?topic=973628.0;all

Any help is really appreciated  

[achow101]

Did someone here manage to compile the update on a Raspberry PI or a banana PI?
No problem with the older builds but when I try with 0.13.0 it stops after ~30min

Interesting. Try opening an issue on the github page. Also, have you tried using the new ARM builds?

[Real-Duke]

Interesting. Try opening an issue on the github page. Also, have you tried using the new ARM builds?

hmm don't know how to do that on github page...but the next step for me is to look for a precompiled working binary.
My OS is called "Bananian" https://www.bananian.org/
What is the correct ARM build for testing on Banana Pi M1 with ARM Cortex-A7 Dual-core (ARMv7-A) 1 GHz CPU?

[Lauda]

Interesting. Try opening an issue on the github page. Also, have you tried using the new ARM builds?

hmm don't know how to do that on github page...but the next step for me is to look for a precompiled working binary.

Navigate to the Bitcoin Core Github page and then press the button "New Issue":



You obviously need to have an account though.

[Real-Duke]

You obviously need to have an account though.

Thanks I have open a ticket! https://github.com/bitcoin/bitcoin/issues/8778
Hopefully the devs can help on this.

Edit: Problem solved!

[EBK1000]

Can someone please tell me which version of OpenSSL BTC use for client communication?

[achow101]

Can someone please tell me which version of OpenSSL BTC use for client communication?

OpenSSL isn't used for client communication. At this point it is only used for the PRNG and maybe something else. It is mostly being phased out.

Bitcoin Core uses 1.0.1k

[Dabs]

OpenSSL isn't used for client communication. At this point it is only used for the PRNG and maybe something else. It is mostly being phased out.

What library or procedure will be used for the PRNG? That's an important one. If Linux, there's dev/random or one of the hardware RNGs. If Windows, there's the Real Time High Resolution Timer thing (QueryPerformanceCounter? or RDTSC?) and crypto.dll or whatever is the "microsoft standard".

Maybe there should be an option to seed the PRNG from your own external source, or a file. Since Bitcoin Core is no longer a "newbie" wallet, I think, so knowledgeable people who know even a little bit about how crypto works, they should know what's a good source for seeding the PRNG.

There's the "old fashioned" keystrokes and mouse movement thing. You'd only do it once. A small dialog or option "Would you like to provide additional entropy?".

Or something crazy like "Please roll the dice one hundred times."

[achow101]

OpenSSL isn't used for client communication. At this point it is only used for the PRNG and maybe something else. It is mostly being phased out.

What library or procedure will be used for the PRNG? That's an important one. If Linux, there's dev/random or one of the hardware RNGs. If Windows, there's the Real Time High Resolution Timer thing (QueryPerformanceCounter? or RDTSC?) and crypto.dll or whatever is the "microsoft standard".

Maybe there should be an option to seed the PRNG from your own external source, or a file. Since Bitcoin Core is no longer a "newbie" wallet, I think, so knowledgeable people who know even a little bit about how crypto works, they should know what's a good source for seeding the PRNG.

There's the "old fashioned" keystrokes and mouse movement thing. You'd only do it once. A small dialog or option "Would you like to provide additional entropy?".

Or something crazy like "Please roll the dice one hundred times."

I'm not sure.. I know that it was talked about in the past to phase out OpenSSL, primarily for the signature and hashing functions. Those were replaced by libsecp256k1. I don't know what work is going to be done for the PRNG.

[calkob]

I have verified the hash and everything is what it should be. Honestly speaking, this is the first time ever I check the client software before installing it.

It was quite naive from me to assume that when I download the client from bitcoin.org that everything would be 100% safe. Now I know better of course.

I am in the same boat..... to be honest i never knew that i should until this release, was really easy to follow the guide.

[ADEELTARIQ]

Hy i am new here plz guide me how i work it ?

[achow101]

Hy i am new here plz guide me how i work it ?

Make sure you have at least 80Gb of free space on your hard drive. Download Bitcoin Core. Install it. Run it. Let it sync. Then use.

[OmegaStarScream]

I'm not sure what was the exact issue but I was able to fix the notification problem by simply Uninstalling Bitcoin core , cleaning using CCleaner and Reinstalling the wallet once again .

[achow101]

I'm not sure what was the exact issue but I was able to fix the notification problem by simply Uninstalling Bitcoin core , cleaning using CCleaner and Reinstalling the wallet once again .

There was probably some Qt temp file or something that was causing the problem and CCleaner got rid of it so it fixed it.