ok, there is a way to fix the fact that i need to resync after pruning if i want to use another wallet? if not can this be fixed in the future please? it's really a pain to download again each time
There isn't really a way to fix that because in order to use another wallet, it must scan the blockchain for all of its transactions. Unfortunately you can't scan the blockchain if you don't have all of it when pruned. 
Topic: Bitcoin Core version 0.13.0 Released (Read 12375 times)
how it work with other wallet? if i want to run another wallet that already used sync in the last version, can i do it again after pruning? or i need to resynch each time?
Upgrading will not affect your wallets or the downloaded blockchain. It does not affect any data used by Bitcoin Core except for the executable itself.ok, there is a way to fix the fact that i need to resync after pruning if i want to use another wallet? if not can this be fixed in the future please? it's really a pain to download again each time
1) when pruning is enable, you can not create a new wallet with an private key (need entery blockchain to scan and retrieve funds).
2) when pruning is enable, you can not use P2Pool server to mine.
2) when pruning is enable, you can not use P2Pool server to mine.
how it work with other wallet? if i want to run another wallet that already used sync in the last version, can i do it again after pruning? or i need to resynch each time?
Upgrading will not affect your wallets or the downloaded blockchain. It does not affect any data used by Bitcoin Core except for the executable itself.
how it work with other wallet? if i want to run another wallet that already used sync in the last version, can i do it again after pruning? or i need to resynch each time?
Quote
cleaning using CCleaner
and you discover a day that your wallet without encrypt password is empty.CCleaner is not a open-source code readable.
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. 
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 .
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. 
Hy i am new here plz guide me how i work it ?
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.
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. 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."
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."
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
Can someone please tell me which version of OpenSSL BTC use for client communication?
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!
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.
You obviously need to have an account though.
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?
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? No problem with the older builds but when I try with 0.13.0 it stops after ~30min
Jump to: