Corrupted database? · Issue #2305 · bitcoin/bitcoin · GitHub

Why I stopped using Bitcoin-Qt. The database eventually gets corrupted and it takes days to reindex.

Why I stopped using Bitcoin-Qt. The database eventually gets corrupted and it takes days to reindex. submitted by Bitcoin_TPS_Report to Bitcoin [link] [comments]

Can you fix the LevelDB database corruption bug affecting Bitcoin-Qt on some platforms? 5+ BTC bounty.

Can you fix the LevelDB database corruption bug affecting Bitcoin-Qt on some platforms? 5+ BTC bounty. submitted by theymos to Bitcoin [link] [comments]

Another bitcoin noob. I went to open my bitcoin-qt wallet and it says I have a corrupt database and asks if I want to rebuild it. What should I do?

I'm on OsX and have opened the wallet numerous times to allow it to update the blockchain info but today I got the error. I don't know what version of the wallet I have. I need help.
submitted by liberty4u2 to Bitcoin [link] [comments]

Block database corruption on Bitcoin-Qt

I recently upgraded Bitcoin-Qt on my Mac to version 0.8.1. (if I recall, it was necessary because of an issue with the bitcoin protocol?)
Since then, I have had it give me an error reading the block database a few times, which requires the block chain to be reindexed. The wallet data itself is intact, and usable once this is done. However, it takes several hours to reindex the block chain on my system, and I can't do any transactions until this is done.
Any idea what might be causing a problem like this, or anything I can try to clear out what might be causing problems? Thanks.
submitted by MultiUseAccount to BitcoinBeginners [link] [comments]

Dogecoin 1.5.1 Released - Upgrade Now!

We’re happy to announce the release of Dogecoin version 1.5.1!
This release incorporates a range of updates from community contributors, some much needed bug fixes, plus some cool treats brought down-stream from the recent Bitcoin 0.9 release candidate.
Thanks to everyone who helped make this release possible, the entire community appreciates it. We recommend all users update to the latest version and please report any issues you may encounter. As always, backup your wallet.dat file before updating (just to be safe).
Downloads: Windows Installer Windows Archive Mac OS X App
Release highlights: - Switched to Boost 1.55 to fix network connectivity issues on Windows - Removal of reliance on IRC for discovering nodes - Support for URL protocol, eg. dogecoin:addr?amount=xxx&(see Bitcoin’s implementation) - Ability to automatically look up transactions on Dogechain from your client - Working Windows setup script and installer - Opt-in debug logging via -debuglog (to save disk space and stop constant writing) - Fixed Mac Splashscreen’s greedy desktop behavior - Reimplemented testnet, fixing RPC crash due to no genesis block being present - Allow user to load any wallet from data directory specified using -wallet=mywallet.dat - Updated to LevelDB 1.15 to address blockchain database corruption issues - Allow user to send change only to specified address(es) using -change= (one -change parameter per address) - Fixed RPC difficulty look up
Troubleshooting
If anyone experiences issues, delete all 1.4 data (apart from your backed up wallet.dat file) and do a fresh 1.5.1 install.
Enjoy!
submitted by Laika1954 to dogecoin [link] [comments]

PIVX Core v3.0.6 released (November 30th) - Optional Upgrade

Github release info and binaries
Forum Post
Important information about the automint and zPIV backup requirements

How to Upgrade

This release is optional but recommended. The latest mandatory upgrade is v3.0.5.1, but if you have any problems with earlier versions the latest version is recommended.
If you are running an older version, gracefully shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/PIVX-Qt (on Mac) or pivxd/pivx-qt (on Linux).
There are no special steps needed like config file changes but a backup is always a good idea.
A note from presstab in case it gets buried in the comments
Command line install and upgrade guide

Notable Changes

(but you should still read the release notes on Github)

Automated Database Corruption Repair

There have been cases of blockchain database corruption that can occur when PIVX client is not closed gracefully. The most common cases of corruption have been identified and the wallet will now automatically fix most of these corruptions. Certain corruption states are still unable to be fixed, but now provide more detailed error messages to the user as well as prompting the user to reindex their database.

More Accurate Error Messages

Some error messages in the wallet have been too vague and done little to help developers and the support team properly identify issues. Error messages have been refined and are now more specific.

Reduction of Debug Log Spam

Many 3rd party services have reported that their debug logs have been overloaded with messages about unknown transaction types. This log spam has been fixed.

Removal of Heavy Running Transaction Search Code

Many areas of the block validation code use a "slow" transaction search, which searches redundantly for transactions. This "slow" search has been removed upstream in Bitcoin and is now removed in PIVX. This provides a more efficient syncing process and generally better performing wallet.

Sync Fix for Block 908000

Many wallets were having trouble getting past block 908000. This block recalculates certain aspects of the money supply and zPIV transactions, and is known to take longer to sync. Code has been added to allow block 908000 to be validated without the user needing to enter any special commands into the debug console.

Working Testnet

Testnet is now accessible with this release of the wallet. Testnet can be accessed using the -testnet startup flag.

zPIV Spending Fix

zPIV that were minted between block 891730 and 895400 were experiencing an error initializing the accumulator witness data correctly, causing an inability to spend those mints. This has been fixed.

Credits

Thanks to everyone who directly contributed to this release:
As well as everyone that helped translating on Transifex.
submitted by turtleflax to pivx [link] [comments]

A Guide to Keeping Keys Offline Using Armory +rPi

Hi Redditors.
I am going to post in this thread my experiences in getting my Desktop (Debian) machine running Armory in watch-only mode, and coupling that with an offline Raspberry Pi (which holds my private keys) for signing the transactions previously made in watch-only mode.
I actually compiled Armory from source directly on my Pi. This guide is probably more for the bitcoin 'power user', as to run Armory online, and broadcast the signed transactions, you need to have a bitcoin full node running (bitcoind).
Basic requirements:
Aimed-for Setup:
I'll post the guide in digestible sections...

Section 1

I should begin by saying I installed source code from git, and got Armory to build the DB on my desktop initially, WITHOUT creating a wallet.. (This allowed me to debug what was going on a little!)
Go to Bitcoin.org, select Armory..
It leads to a Download from Git:
https://github.com/goatpig/BitcoinArmory/releases
Followed the procedure for Linux Debian verify code, compile, install, all straight-forward..
Began by running bitcoind, and telling Armory where to find it. This is the command I used, obviously it was all on one line and didn't include the arrows/explanations!:
python ArmoryQt.py \ --satoshi-datadir=/BlockChain/chain20180414/blocks \ # <-----(where my bitcoind blocks live) --datadir=/ArmoryDataDi \ # <-----(this is instead of ~/.armory) --dbdir=/ArmoryDataDidatabases # <-------(again, non std. place used for Armory's databases.. my choice.) 
So, on the Desktop, after the initial "build databases"
(NB the initial "Build Databases" took about 1.5h and my two CPUs were maxed the whole time, Temps up to 62C. Not ideal; Im not in a rush!)
I then wanted to import a watch-only wallet.
Before I did this, I took a full backup of the Armory data dir:
/ArmoryDataDi
(or ~/.armory in a default installation).
I'd hate to have to make Armory do another full sync with the bitcoind node!

Section 2

Next step: offline wallet (with Private Keys) is on a Raspberry Pi.
I downloaded the source and managed to compile it on the pi itself! :)
Though there were some gymnastics needed to setup the Pi.
My Pi is running Raspbian based on Wheezy.. quite old!
I did the following on the Pi:
apt-get update apt-get upgrade (<---took about an hour!) apt-get install autotools-dev apt-get install autoconf 
Then I followed the instructions exactly as I had done for my Debian Desktop machine, EXCEPT:
I had to increase the Pi's swap space. I upped it from 100Mb to 400Mb.
The compilation took 7 hours, and my poor SD card got a thrashing.
But after compilation, I put the Swap back to 100Mb and Armory runs ok with about 150Mb of memory (no swap needed).
Swap increase on the Pi:
use your favourite editor, and open the file /etc/dphys-swapfile
add/change the following line:
CONF_SWAPSIZE=400 
Then, REBOOT the Pi:
sudo shutdown -h -P now 
Once the compilation was done on the Pi, put the swap back, rebooted and created an Armory wallet.
I added manual entropy and upped the encryption 'time' from 250ms to 2500ms - since the Pi is slow, but I'll be happy to wait for more iterations in the Key Derivation Function.
Once the wallet was created, it obviously prompts you for backup.
I want to add a private key of my own (i.e. import), so don't do the backup until this is over.
I import my Private Key, and Armory checks that this corresponds to a Public Key, which I check is correct.
This is the point now where the Pi storage medium (e.g an SD card) has to be properly destroyed if you ever get rid of it.
I had thought that now would be a good time to decide if your new wallet will generate Segwit receiving addresses, and also addresses used to receive 'change' after a transaction..
But it seems Armory WON'T let you switch to P2SH-P2WPKH unless your Armory is connected to a node offering "WITNESS" service.
Obviously, my Pi is offline and will never connect to a node, so the following will not work on the Pi:
NB: I thought about setting this on the Debian "watch-only" wallet, but that would surely mean doom, as the Pi would not know about those addresses and backups might not keep them.. who knows...
So, end result:- no segwit for me just yet in my offline funds.

--If anyone can offer a solution to this, I'd be very grateful--

Section 3

Ok, now this is a good point to back up your wallet on the Pi. It has your imported keys. I choose a Digital Backup - and put it on a USB key, which will never touch the internet and will be stored off-site. I also chose to encrypt it, because I'm good with passwords..
NB: The Armory paper backup will NOT back up your imported private keys, so keep those somewhere if you're not sweeping them. It would be prudent to have an Armory paper backup anyway, but remember it will likely NOT help you with that imported key.
Now for the watch-only copy of the wallet. I want to get the "watch-only" version onto my Desktop Debian machine.
On the Pi, I created (exported to a USB key) a "watching-only" copy of my wallet.
I would use the RECOMMENDED approach, export the "Entire Wallet File".
As you will see below, I initially exported only the ROOT data, which will NOT capture the watching-only part of the Private Key I entered manually above (i.e. the public Key!).
Now, back on the Debian Desktop machine...
I stopped all my crontab jobs; just give Armory uninterrupted CPU/memory/disk...
I also stopped bitcoind and made a backup prior to any watch-only wallet being imported.
I already made a backup of Armory on my Desktop, before any wallet import.
(this was needed, as I made a mistake.. see below)
So on the Debian Desktop machine, I begin by firing up bitcoind.
my command for this is:
./bitcoind -daemon -datadir=/BlockChain/chain20180414 -dbcache=400 -maxmempool=400 

Section 4

I try running Armory like this:
(I'm actually starting Armory from a script - StartArm.sh)
Inside the script StartArm.sh, it has the line:
python ArmoryQt.py --ram-usage=4 --satoshi-datadir=/BlockChain/chain20180414/blocks --datadir=/ArmoryDataDi --dbdir=/ArmoryDataDidatabases 
I know from bitter experience that doing a scan over the blockchain for a new wallet takes a looong time and a lot of CPU, and I'd like it to play nicely; not gobble all the memory and swap and run my 2xCPUs both at 100% for four hours...
So... I aim to run with --ram-usage=X and --thread-count=X
(For me in the end, X=1 but I began with X=4)
I began with --ram-usage=4 (<--- = 4x128Mb)
The result is below...
TypeError: cannot concatenate 'str' and 'int' objects 
It didn't recognise the ram-usage and carried on, crippling my Debian desktop PC.
This is where it gets dangerous; Armory can gobble so much memory and CPU that the windowing environment can cease up, and it can take over 30 minutes just to exit nicely from bitcoind and ArmoryDB.
So, I ssh to the machine from another computer, and keep an eye on it with the command
"free -h" 
I'd also be able to do a "sudo reboot now" if needed from here.

Section 5

So, trying to get my --ram-usage command recognised, I tried this line (added quotes):
python ArmoryQt.py --ram-usage="4" --satoshi-datadir=/BlockChain/chain20180414/blocks --datadir=/ArmoryDataDi --dbdir=/ArmoryDataDidatabases 
But no, same error...
Loading Armory Engine: Armory Version: 0.96.4 Armory Build: None PyBtcWallet Version: 1.35 Detected Operating system: Linux OS Variant : ('debian', '9.4', '') User home-directory : /home/ Satoshi BTC directory : /BlockChain/chain20180414 Armory home dir : /ArmoryDataDi ArmoryDB directory : /ArmoryDataDidatabases Armory settings file : /ArmoryDataDiArmorySettings.txt Armory log file : /ArmoryDataDiarmorylog.txt Do wallet checking : True (ERROR) ArmoryUtils.py:3723 - Unsupported language specified. Defaulting to English (en) (ERROR) ArmoryQt.py:1833 - Failed to start Armory database: cannot concatenate 'str' and 'int' objects Traceback (most recent call last): File "ArmoryQt.py", line 1808, in startArmoryDBIfNecessary TheSDM.spawnDB(str(ARMORY_HOME_DIR), TheBDM.armoryDBDir) File "/BitcoinArmory/SDM.py", line 387, in spawnDB pargs.append('--ram-usage=' + ARMORY_RAM_USAGE) TypeError: cannot concatenate 'str' and 'int' objects 

Section 6

So, I edit the Armory python file SDM.py:
if ARMORY_RAM_USAGE != -1: pargs.append('--ram-usage=4') #COMMENTED THIS, SO I CAN HARDCODE =4 # ' + ARMORY_RAM_USAGE) 
Running it, I now have acknowledgement of the --ram-usage=4:
(WARNING) SDM.py:400 - Spawning DB with command: /BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/BlockChain/chain20180414/blocks" --datadir="/ArmoryDataDi" --dbdir="/ArmoryDataDidatabases" --ram-usage=4 
Also, even with ram-usage=4, it used too much memory, so I told it to quit.
It took over 30 minutes to stop semi-nicely. The last thing it reported was:
ERROR - 00:25:21: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version 
But that didn't seem to matter or corrupt the Armory Database, so I think it's ok.
So, I get brave and change SDM.py as below, and I make sure my script has a command line for --ram-usage="ABCDE" and --thread-count="FGHIJ"; the logic being that these strings "ABCDE" will pass the IF criteria below, and my hardcoded values will be used...
if ARMORY_RAM_USAGE != -1: pargs.append('--ram-usage=1') #COMMENTED THIS, SO I CAN HARDCODE =1 # ' + ARMORY_RAM_USAGE) if ARMORY_THREAD_COUNT != -1 pargs.append('--thread-count=1') #COMMENTED THIS, SO I CAN HARDCODE =1 #' + ARMORY_THREAD_COUNT) 
So, as usual, I use my script and start this with: ./StartArm.sh
(which uses command line:)
python ArmoryQt.py --ram-usage="ABCDE" --thread-count="FGHIJ" --satoshi-datadir=/BlockChain/chain20180414/blocks --datadir=/ArmoryDataDi --dbdir=/ArmoryDataDidatabases 
(this forces it to use my hard-coded values in SDM.py...)
So, this is the command which it reports that it starts with:
(WARNING) SDM.py:400 - Spawning DB with command: /BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/BlockChain/chain20180414/blocks" --datadir="/ArmoryDataDi" --dbdir="/ArmoryDataDidatabases" --ram-usage=1 --thread-count=1 
Again, this is where it gets dangerous; Armory can gobble so much memory and CPU that the windowing environment can cease up. So I ssh to the machine and keep an eye on it with:
"free -h" 

Section 7

So, on the Debian Desktop PC, I inserted the USB stick with the watch-only wallet I exported from the Pi.
Start Armory...
Import "Entire Wallet File" watch-only copy.
Wait 4 hours..
YAY!!!
After running Armory for about 30m, the memory usage dropped by 400m... wierd...
It took ~2 hours to get 40% completion.
After 3.5 hours it's almost there...
The memory went up to about 1.7Gb in use and 900Mb of Swap, but the machine remained fairly responsive throughout, apart from a few (10?) periods at the start, where it appeared to freeze for 10-30s at a time.
(That's where my ssh session came in handy - I could check the machine was still ok with a "free -h" command)
Now, I can:
Create an unsigned transaction on my Desktop,
Save the tx to USB stick,
Move to the Pi,
Sign the tx,
Move back to the Desktop,
Broadcast the signed tx.

Section 8

My initial Mistake:
This caused me to have to roll-back my Armory database, using the backup. so you should try to avoid doing this..
On the Pi, I exported only the ROOT data, which will NOT capture the watching-only part of the Private Key
It is RECOMMENDED to use the Digital Export of Entire Wallet File from the Pi when making a watch-only copy. If you just export just the "ROOT data", not the "Entire Wallet File", you'll have problems if you used an imported Private Key in the offline wallet, like I did.
Using the ROOT data text import, after it finished... my balance was zero. So,. I tried a Help->Rescan Balance (Restart Armory, takes 1minute to get back up and running) No Luck. Still zero balance.
So, I try Rescan Databases.. This will take longer. Nah.. no luck.
So, I tried again, thinking it might be to do with the fact that I imported the text "root data" stuff, instead of following the (Recommended) export of watching-wallet file.
So, I used my Armory backup, and wound back the ArmoryDataDi to the point before the install of the (zero balance) wallet. (you should not need to do this, as you will hopefully use the RECOMMENDED approach of exporting the "Entire Wallet File"!)
submitted by fartinator to Bitcoin [link] [comments]

Lost most of my Doge late 2013. There may be one last solution to getting some back. Does anyone have a copy of "DogeCoin version v0.6.4.0-unk-beta" or know which release it is directly linked to?

My keys corrupted and i didn't have a recent backup, after the upgrade lost all the doges.

I think there might be one more hope of finding some, and would appreciate if anyone knows which version " v0.6.4.0-unk-beta" which is on the debug.log output.

Noticed after all this time after digging through Bitcoin release notes that before bip32/hd wallets came in or as a matter of fact As they came in too (thanks devs). Most if not everyone i asked thought backing up the wallet.dat file is good enough, or the old --salvagewallet nor -zapwalletxes. They either aggressively scrambled the wallet making it more likely destroy even more keys, sure saved a few coins but most of the addresses in the keypool which has a size of 100 didn't have a corresponding private key anywhere in the wallet AFAIKT,
Sorry before i rant, i just need some info on if this wallet if linked to a specific Dogecoin version and just happens to say v0.6.4.0 in the debug log file.

I can't update directly to any other version without the wallet breaking up. Apparently i need the exact version that was last used, and turn it off extra safely so the log files which hold some parts of the keys go back to the Wallet.dat or something.

I tried all solutions, this might just work. from the "Bitcoin version 0.7.1 Readme file."
How to Upgrade
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).
If you were running on Linux with a version that might have been compiled with a different version of Berkeley DB (for example, if you were using an Ubuntu PPA version), then run the old version again with the -detachdb argument and shut it down; if you do not, then the new version will not be able to read the database files and will exit with an error.
Explanation of -detachdb (and the new “stop true” RPC command): The Berkeley DB database library stores data in both “.dat” and “log” files, so the database is always in a consistent state, even in case of power failure or other sudden shutdown. The format of the “.dat” files is portable between different versions of Berkeley DB, but the “log” files are not– even minor version differences may have incompatible “log” files. The -detachdb option moves any pending changes from the “log” files to the “blkindex.dat” file for maximum compatibility, but makes shutdown much slower. Note that the “wallet.dat” file is always detached, and versions prior to 0.6.0 detached all databases at shutdown.
or on shut down the coin client using the -detatchdb comas coins use both log and dat files with berkeley.

Thanks,

D_M


submitted by doge_messiah to dogecoin [link] [comments]

need help. My wallet destroyed just now!

***Finally get back from An old .bak file. The .bak file today still can't open. No loss anyway
Thank you my friends.
However, I strongly urge Bitcoin foundation who maintains bitcoind improve its security greatly. It's not hard to solve if you see Bitcoin as money, as people's wealth.
Also, just now I sent the btc to my main wallet. and set the"change" to go to a coinbase address. But after being sent, I saw there is a remind "unknown address", and the 0.00xx btc now lies in the software. WTF?
Could you give users some better experience, Bitcoin Foundation? Bitcoin is no longer a toy, it's now money, you know? You need fear while dealing with things about money.
You can do much better.
Bitcoin as a science is perfect, But the related business/foundation as a technology don't deserve the honor. I know it feels cynicism. But they don't love & don't fear users.
Ok, it seems that I become the new victim of "salvaged fail". 15% of Life savings oh.
I no longer want to accuse Bitcoin foundation. They don't care, so do I.
The story: My laptop ran out of power while Bicoind was running. So the wallet corrupt for ever. Then I was so nervous that I copy another wallet.dat to make a backup without stopping bitcoind, then the 2nd wallet corrupt for ever.
I no longer, no longer want to accuse. i lost strength to accuse.
I ever thought 15% did not deserve to care enough, until one day I lost it.
Sorry, i am too sad
I use windows. SSD (macbook pro)
It seems the reason why this occured is that my laptop ran out of power while the bitcoind runing.
  1. I don't have any backup file.
  2. I have used this wallet.dat for more than one year. And in the past 5 months, I never use it.
  3. just now, I opened the bitcoind with the command -salvagewallet, and it says it needs to reindex, i choose "no". S it closed. And said “salvage failed"
  4. I saw the wallet.dat disappeared, and there appears a new file "wallet.*****(timestamp).bak", which I can't open.
I tried to relaunch bitcoind several times, with or without "-salvagewallet", every time failed.
I still have hope because One webpage I searched says "Warning: wallet.dat corrupt, data salvaged! Original wallet.dat saved as wallet.{timestamp}.bak in /root/.c-note; if your balance or transactions are incorrect you should restore from a backup."
But what I saw is "salvage failed", So I am a little nervous.
Shall I use the "-loadblock=wallet.14***(timestamp).bak" command? thanks
  1. So what can I do now to get my coins back?
is it able to get .dat from this new-generated .bak?thanks
thank you very much.
Anyone knows how to get bitcoin qt to recognise the presence of the corrupted wallet? thanks conf?
DB.LOG
file unknown has LSN 1/263145, past end of log at 1/198476 Commonly caused by moving a database from one database environment to another without clearing the database LSNs, or by removing all of the log files from a database environment Page 0: metadata page corrupted Page 0: could not check metadata page wallet.dat: DB_VERIFY_BAD: Database verification failed file unknown has LSN 1/263145, past end of log at 1/199524 Commonly caused by moving a database from one database environment to another without clearing the database LSNs, or by removing all of the log files from a database environment wallet.1428881042.bak: DB_VERIFY_BAD: Database verification failed
submitted by binghamtonbitcoin to Bitcoin [link] [comments]

Armory Wallet Has Failed Me! Can I recover BTC?

So I opted to migrate from coinbase to a local wallet.
Naturally, I download Armory and shoot it a send for 1BTC. 225 confirmations on the SEND, but wallet never receives it.
Turns out, running Armory wallet has been corrupting my database. Every time I run it a background process it spawns causes Bitcoin-QT to fail.
I've tried uninstalling and re-installing bitcoin, armory wallet three times. I've deleted my bitcoin directory in %appdata%, ensured downloads are never interrupted.
Is there any way at all for me to recover the BitCoin I sent to armory wallet provided I can never get armory wallet to work correctly?
Any help appreciated. Here is the errors:
2015-08-21 14:48:15 init message: Activating best chain... 2015-08-21 14:49:23 Corruption: block checksum mismatch 2015-08-21 14:49:23 *** System error while flushing: Database corrupted
submitted by andhof-mt to Bitcoin [link] [comments]

I'm tired of bitcoin-qt

Mini rant. I was happy using bitcoin-qt for quite a few months now, It had gave me a few headaches, sometimes the database was corrupted or something, just re-index it. It worked fine.
I always exit bitcoin-qt before shutting down the computer, to never let this happen again, but it happens from time to time.
Anyway, five days ago, it started again with the database problem. I tried to reindex it, delete last blocks and reindex it, nothing was working. So, OK, screw it, delete all (except wallet file) and let download the whole blockchain again. ... Well... it stopped syncing after a while. It tells me that I need to update the client. Other times I it tells me it's syncing, but it shows a 0 blocks indexed (and no arrows icon on bottom-right).
After 5 days, I just delete everything (again) and started from 0.
I don't like the idea of thin client, but for the moment I've downloaded MultiBit, I read that Armory works on top of bitcoin-qt, should I try it or I will have the same problems?
I know this is my problem, not a problem with bitcoin-qt itself, it worked very good for months. I don't think it's a network problem (I have a good connection), not a software problem (Debian Squeeze), as I said, I exit the program before the computer. Just a mini-rant about all this.
I'm also concerned this happens to less techie people, they could easily delete the wallet file, or just get tired of bitcoins because of similar problems with the programs.
submitted by still_unregistered to Bitcoin [link] [comments]

HELP! Bitcoin qt client crashed on my computer with a database error! Lost all my bitcoins?!

hey guys,
The bitcoin qt client was catching up with the blockchain (5 days worth), when after maybe 15 minutes, it comes up with an error, "database corrupted" or something along the lines of that. I looked it up and users said to delete everthing in my %appdata/roaming/bitcoin% directy except the wallet.dat file.
So I did that, and downloaded the latest bitcoin qt client, but as it's got 252 weeks to catch up on, it shows 0 btc, is this normal? Will it show my bitcoins whilst it's done updating?
It should show it at the end, right? Once it's seen the transactions on the blockchain? Sorry, I'm just ultra panicky atm from not seeing my bitcoins :S
EDIT: GOT MY BITCOINS. For anyone that has this problem in the future, it's 99.99% likely it's a RAM problem. Took my dodgy ram stick out and used a rescan tag & it was all good to go! You can also import the boostrap.dat file.
submitted by TheNewHero to Bitcoin [link] [comments]

New wallet?

Hello, i'm considering switching wallet since i don't have time to always update my bitcoinQT database (wich is also keep getting corrupted pretty often....) and i wonder if there is any wallets that you guys would recommend. The only requirement i have is that it should not be a mobile wallet. If its a wallet that works on the pc and the mobilephone it would be great.
Being able to have it in cold storage would be a +
Thanks in advance.
submitted by GBG-glenn to Bitcoin [link] [comments]

Corrupted wallet.dat with 18 btc - Possible to restore bitcoins?

I have a wallet from yore, had 18 btc that got corrupted and I kind of just lost interest in bitcoins. Well now that 18 is woth $2K or so and I fired up a new bitcoin-qt wallet with that wallet.dat file to see if it would read it. Well it almost did.
The GUI read 18 unverified bitcoins at first, and as the blockchain neared completion, it verified every bitcoin. I was so excited. But then it crashed with a runaway exception "can't open database file wallet.dat -30974"
I get that error when I try to send a bitcoin too. Any chance of restoring this near-working wallet?
EDIT: Bitcoins have been recovered!!!!!!! The final solution was provided by musicbunny, to which I am extremely greatful for his out-of-the box solution. I think pywallet suggested by eof would have done the trick too. The keys probably could have been extracted, but I was running into trouble with my version of Python. Maybe it needed Python 2?
submitted by bitbeast to Bitcoin [link] [comments]

Reminder - bitcoin is beta software! Corrupt wallets, bugs, errors, oh my! I dodged a bullet today, make sure you are prepared for disaster too!

Hello everyone,
This is a public service announcement brought to you by a fellow bitcoiner who dodged a bullet today.
I'm very adamant about backups, having lost data many years ago, I always try to make sure I have backups of backups now. External hard drives, raids, the cloud, leverage anything and everything to insure you won't lose data.
Well today it all came to fruition. If I was not so strong willed about keeping backups, I might have lost all my bitcoins today. Last night I went to sleep with the bitcoin program working perfectly on my computer. I run debian, nothing fancy or crazy or custom, just a stock os with a stock bitcoin install.
I wake up today and bitcoin has quit itself last night. I load bitcoin-qt and I get the, "your database has corrupted, would you like to try to fix" dialogue box. I select yes, it looks like it's working but gets near the end and dies. This looks like the same issue I had weeks ago. I alerted sipa, one of the main developers about it and was informed it was probably an os level instability on my end. This was weeks ago, so I reinstalled my system entirely, did memory checks and checked the hard drive for bad blocks or corruption to rule out hardware issues.
So here we are, on a brand new os install, with a brand new bitcoin install, with a fresh blockchain, and yes it totally corrupted itself in the middle of the night without any user interaction on my part.
So back to the story, I keep a copy of the blockchain before any corruptions occur on an external hard drive so I can easily reload in case this exact situation occurs. So I nuke the old one, load this existing blockchain, and am greeted with this lovely dialogue box I've never seen before, "wallet.dat corrupt, salvage failed". My heart skips a beat. Really? My wallet is also corrupted? Great.
Luckily I keep encrypted incremental backups on one of my external drives, decrypt, load that, and am up and running again.
To all those who live dangerously without backups, you are playing with fire and WILL get burned eventually. If you are not making daily backups to multiple sources, you are doing it wrong. If I wasn't so careful, I'd currently be out hundreds of bitcoins, and possibly posting on the forums on how to fix a corrupt wallet.
If anybody is curious, the link below is the bug I ran into. I'm not sure if this is directly related to the wallet corruption. I'm guessing its at least related to the blockchain corruption though, because this is the exact same error I received last time my blockchain corrupted itself. I alerted one of the main developers to my issue, so at least they are aware of it.
https://github.com/bitcoin/bitcoin/issues/2402
submitted by dodgedABullet_ to Bitcoin [link] [comments]

SSD Wear Leveling discussion.

I am not quite sure where this post belongs but I figured this was as good a place as any, if that is not so please tell me and I will remove or move the post.
So I have recently had some issues with the Bitcoin-QT block database coming up as corrupted every time I restarted the program, in the process of trying to find the cause I went and started running some diagnostics on my Samsung SSD using the Gnome Disk's utility and noticed that the wear-leveling-count (SMART value 177) read 455.
After a great deal of research I came to the conclusion that this means that all the memory devices in the SSD have reached 455 erase cycles out of their 1024 max design spec.
Here is where things get strange and I get confused, both of the articles I read during my research [1] [2]. Indicated that it would be nearly impossible to reach that sort of value over the course of my two years of ownership unintentionally.
To top the mystery off, where both [1] and [2] show actual SMART data from their tested disks it shows the "normalized" or "raw" value as being calculated by (1024-wearcount)/1024 aka a percentage of total wearcount within spec remaining.
This means my normalized value should be 55 right? But its instead 87.
Further reading shows the wear-leveling-count is actually defined as the highest number of read/write cycles any single memory element has been subjected to, not necessarily the number all memory elements have been subjected to. But in a situation where wear leveling is working properly these values should be just about one and the same.
Both my setup and use style of this machine may be the cause of this little conundrum. When I installed Ubuntu a year or so ago now I enabled both LVM encryption and Home folder encryption, I was interested in the performance impact, it seems both systems take advantage of the AES hardware in the processor because no amount of benching could show any extra load or generate any problems.
Since there where no issues, I continued dual booting Windows and Ubuntu like that for a long time till I recreated the Ubuntu setup without windows when I went all linux.
At the end of the day this whole problem is a pretty idle question, with about 3000 writes till actual failure [2] the device will either fail in about 8 years or 15 depending on which value you trust.
submitted by ttk2 to linux4noobs [link] [comments]

When importing a wallet.dat file from an encrypted Bitcoin-QT to blockchain, does the password of bitcoin-qt become the password on the blockchain wallet?

What I'm trying to do is move my coins from bitcoin-qt to my Electrum wallet because the block database got corrupted and I'm tired of having to always rebuild it when this happens.
I'm quite nervous about moving my coins around like this without knowing exactly what I'm getting into. Is there a better way of doing this?
submitted by ImBigOnReddit to Bitcoin [link] [comments]

Bitcoin QT not launching, please help

In hindsight I relized my title is wrong so..
"QT is not able to sync with the blockchain"
Hi,
I've been trying to launch my bitcoin-qt for weeks now, but every time it tries to download the blockchain it ends at a random point saying its database is corrupted. I've deleted and reinstalled everything at least 3 times. including the appdata subfolder. What else can I do? There seems to be some issue with storing or downloading the blockchain, thus the client will not launch. Any constructive advice would be great, thanks
My OS is win7 64bit
submitted by ESTeGo to Bitcoin [link] [comments]

How Do I Move My Wallet To Multibit?

I currently use the Bitcoin-QT wallet. however, sometime in the past hour, some clown decided to put a virus signature in the blockchain. This caused my antivirus to spazz out and corrupt my block database. How can I move my Bitcoin wallet to multibit? I have encrypted backups with a passphrase.
Thanks in advance.
edit: Are there any good lightweight alternatives to multibit? Forgot it had issues.
submitted by skilliard4 to Bitcoin [link] [comments]

Facilitating Discussion of 0.9.0 FINAL of Bitcoin Core (aka Bitcoin QT)

To facilitate a detailed discussion of some of the finer points of this update, I added numbering to each bullet in release notes, and also posted it to RapGenius, where people can annotate it if they'd like.
I'm not a programmer, but I'm curious to hear what programmers and other people smarter than me have to say about all the new changes.
http://rapgenius.com/The-bitcoin-dev-team-bitcoin-090-final-lyrics
EDIT1 : Doh! Reddit detroyed all the formatting and now i'm on baby duty so can't fix it. EDIT 2: Nap time! Just fixed the formatting :)
---- 0.9.0 RELEASE NOTES ----
Part 1. RPC:
1.1 - New notion of 'conflicted' transactions, reported as confirmations: -1
1.2 - 'listreceivedbyaddress' now provides tx ids
1.3 - Add raw transaction hex to 'gettransaction' output
1.4 - Updated help and tests for 'getreceivedby(account|address)'
1.5 - In 'getblock', accept 2nd 'verbose' parameter, similar to getrawtransaction, but defaulting to 1 for backward compatibility
1.6 - Add 'verifychain', to verify chain database at runtime
1.7 - Add 'dumpwallet' and 'importwallet' RPCs
1.8 - 'keypoolrefill' gains optional size parameter
1.9 - Add 'getbestblockhash', to return tip of best chain
1.10 - Add 'chainwork' (the total work done by all blocks since the genesis block) to 'getblock' output
1.11 - Make RPC password resistant to timing attacks
1.12 - Clarify help messages and add examples
1.13 - Add 'getrawchangeaddress' call for raw transaction change destinations
1.14 - Reject insanely high fees by default in 'sendrawtransaction'
1.15 - Add RPC call 'decodescript' to decode a hex-encoded transaction script
1.16 - Make 'validateaddress' provide redeemScript
1.17 - Add 'getnetworkhashps' to get the calculated network hashrate
1.18 - New RPC 'ping' command to request ping, new 'pingtime' and 'pingwait' fields in 'getpeerinfo' output
1.19 - Adding new 'addrlocal' field to 'getpeerinfo' output
1.20 - Add verbose boolean to 'getrawmempool'
1.21 - Add rpc command 'getunconfirmedbalance' to obtain total unconfirmed balance
1.22 - Explicitly ensure that wallet is unlocked in importprivkey
1.23 - Add check for valid keys in importprivkey
Part 2. Command-line options:
2.1 - New option: -nospendzeroconfchange to never spend unconfirmed change outputs
2.2 - New option: -zapwallettxes to rebuild the wallet's transaction information
2.3 - Rename option '-tor' to '-onion' to better reflect what it does
2.4 - Add '-disablewallet' mode to let bitcoind run entirely without wallet (when built with wallet)
2.5 - Update default '-rpcsslciphers' to include TLSv1.2
2.6 - make '-logtimestamps' default on and rework help-message
2.7 - RPC client option: '-rpcwait', to wait for server start
2.8 - Remove '-logtodebugger'
2.9 - Allow -noserver with bitcoind
Part 3. Block-chain handling and storage:
3.1 - Update leveldb to 1.15
3.2 - Check for correct genesis (prevent cases where a datadir from the wrong network is accidentally loaded)
3.3 - Allow txindex to be removed and add a reindex dialog
3.4 - Log aborted block database rebuilds
3.5 - Store orphan blocks in serialized form, to save memory
3.6 - Limit the number of orphan blocks in memory to 750
3.7 - Fix non-standard disconnected transactions causing mempool orphans
3.8 - Add a new checkpoint at block 279,000
Part 4. Wallet:
4.1 - Bug fixes and new regression tests to correctly compute the balance of wallets containing double-spent (or mutated) transactions
4.2 - Store key creation time. Calculate whole-wallet birthday
4.3 - Optimize rescan to skip blocks prior to birthday
4.4 - Let user select wallet file with -wallet=foo.dat
4.5 - Consider generated coins mature at 101 instead of 120 blocks
4.6 - Improve wallet load time
4.7 - Don't count txins for priority to encourage sweeping
4.8 - Don't create empty transactions when reading a corrupted wallet
4.9 - Fix rescan to start from beginning after importprivkey
4.10 - Only create signatures with low S values
Part 5. Mining:
5.1 - Increase default -blockmaxsize/prioritysize to 750K/50K
5.2 - 'getblocktemplate' does not require a key to create a block template
5.3 - Mining code fee policy now matches relay fee policy
Part 6. Protocol and network:
6.1 - Drop the fee required to relay a transaction to 0.01mBTC per kilobyte
6.2 - Send tx relay flag with version
6.3 - New 'reject' P2P message (BIP 0061, see https://gist.github.com/gavinandresen/7079034 for draft)
6.4 - Dump addresses every 15 minutes instead of 10 seconds
6.5 - Relay OP_RETURN data TxOut as standard transaction type
6.6 - Remove CENT-output free transaction rule when relaying
6.7 - Lower maximum size for free transaction creation
6.8 - Send multiple inv messages if mempool.size > MAX_INV_SZ
6.9 - Split MIN_PROTO_VERSION into INIT_PROTO_VERSION and MIN_PEER_PROTO_VERSION
6.10 - Do not treat fFromMe transaction differently when broadcasting
6.11 - Process received messages one at a time without sleeping between messages
6.12 - Improve logging of failed connections
6.13 - Bump protocol version to 70002
6.14 - Add some additional logging to give extra network insight
6.15 - Added new DNS seed from bitcoinstats.com
Part 7. Validation:
7.1 - Log reason for non-standard transaction rejection
7.2 - Prune provably-unspendable outputs, and adapt consistency check for it
7.3 - Detect any sufficiently long fork and add a warning
7.4 - Call the -alertnotify script when we see a long or invalid fork
7.5 - Fix multi-block reorg transaction resurrection
7.6 - Reject non-canonically-encoded serialization sizes
7.7 - Reject dust amounts during validation
7.8 - Accept nLockTime transactions that finalize in the next block
Part 8. Build system:
8.1 - Switch to autotools-based build system
8.2 - Build without wallet by passing --disable-wallet to configure, this removes the BerkeleyDB dependency
8.3 - Upgrade gitian dependencies (libpng, libz, libupnpc, boost, openssl) to more recent versions
8.4 - Windows 64-bit build support
8.5 - Solaris compatibility fixes
8.6 - Check integrity of gitian input source tarballs
8.7 - Enable full GCC Stack-smashing protection for all OSes
Part 9. GUI:
9.1 - Switch to Qt 5.2.0 for Windows build
9.2 - Add payment request (BIP 0070) support
9.3 - Improve options dialog
9.4 - Show transaction fee in new send confirmation dialog
9.5 - Add total balance in overview page
9.6 - Allow user to choose data directory on first start, when data directory ismissing, or when the -choosedatadir option is passed
9.7 - Save and restore window positions
9.8 - Add vout index to transaction id in transactions details dialog
9.9 - Add network traffic graph in debug window
9.10 - Add open URI dialog
9.11 - Add Coin Control Features
9.12 - Improve receive coins workflow: make the 'Receive' tab into a form to request payments, and move historical address list functionality to File menu
9.13 - Rebrand to Bitcoin Core
9.14 - Move initialization/shutdown to a thread. This prevents "Not responding" messages during startup. Also show a window during shutdown
9.15 - Don't regenerate autostart link on every client startup
9.16 - Show and store message of normal bitcoin:URI
9.17 - Fix richtext detection hang issue on very old Qt versions
9.18 - OS X: Make use of the 10.8+ user notification center to display Growl-like notifications
9.19 - OS X: Added NSHighResolutionCapable flag to Info.plist for better font rendering on Retina displays
9.20 - OS X: Fix bitcoin-qt startup crash when clicking dock icon
9.21 - Linux: Fix Gnome bitcoin: URI handler
Part 10. Miscellaneous:
10.1 - Add Linux script (contrib/qos/tc.sh) to limit outgoing bandwidth
10.2 - Add '-regtest' mode, similar to testnet but private with instant block generation with 'setgenerate' RPC
10.3 - Add 'linearize.py' script to contrib, for creating bootstrap.dat
10.4 - Add separate bitcoin-cli client
submitted by WhiteyFisk to Bitcoin [link] [comments]

PSA: Added Step May Be Needed When Restoring a Backup Encrypted wallet.dat to Bitcoin Core

TL;DR: To successfully restore an encrypted wallet.dat file, the instance of Bitcoin Core getting restored to needs to first have Encryption turned on and possibly the same Passphrase set as the wallet.dat file you are restoring. It seems this must be done before you restore your encrypted wallet.dat from backup, or Bitcoin Core will just show a zero balance.
For the record, the set-up for this situation was as follows: Bitcoin Core (formerly Bitcoin-Qt) 0.9.2.1, Windows x86 version, on Windows XP Pro patched for 2019 PoS updates.
Recently, my Bitcoin Core hot wallet had been acting up and crashing after about 6 to 12 hours of uptime. I thought that there was possibly some corruption in Core's database files, so I backed up my wallet.dat and started deleting block chain data/index files to see if a rescan or reindex would correct the problem. I tried to save time by not deleting everything, only certain file types. I managed to somehow screw up and got the dreaded "wallet.dat corrupt, salvage failed" message.
Since I had a backup, I didn't bother trying the "-salvagewallet" command-line option (which might have actually corrected my problem.) Instead, I went straight for a restore from backup.
Some time ago, and on a much older version of Bitcoin-Qt I had familiarized myself with the wallet.dat backup and restore process. I never had a problem with it. But thinking back, I may have done all of my testing with unencrypted wallet.dat files.
In this case, I uninstalled Core, deleted everything in the Bitcoin data directory, reinstalled Core, used bootstrap.dat to catch up as much of the block chain as possible, and let the new install finish syncing from the Internet. Once Core was up-to-date, I closed it and restored my encrypted wallet.dat from backup.
In my previous experience, I'd be done at this point. The next time I started the wallet, it would have automatically rescanned, and I'd be back in business. This time, when the wallet finally started up again, it showed no errors, the block chain was still fully synced up, but the wallet showed a zero balance. Not a good feeling.
I thought maybe I'd need to manually start Core using the "-rescan" command-line option. I tried this, but got the same result.
After mulling things over, I finally guessed that the problem might have something to do with Core's wallet.dat encryption.
I again deleted the wallet.dat file from the Bitcoin data directory and restarted Core. Once it finished generating a new wallet.dat file, I enabled Encryption and set the same Passphrase as the wallet.dat file I was trying to restore. Core shut itself down to complete encrypting the new wallet.dat file. Next, I started Core once again to make sure all was OK with new encrypted but empty wallet.dat. I then closed Core and replaced the zero-balance wallet.dat file with my recent backup. That finally did the trick. On the next start, Core automatically did a rescan and my balance reappeared.
I don't know for sure if this behavior is the same across all the different flavors of Bitcoin Core 0.9.2.1 (x64, OSX, Linux), but I suspect it might be. Also, it might work just to enable Encryption, but it might not be necessary to have the same Passphrase. I can only confirm that it worked in my case with the same Passphrase.
This little adventure was unnerving, particularly since Core issues no errors and just insists there's a zero balance. I thought I should relate what I learned in case someone else encounters the same situation.
Cheers, and to the moon!
EDIT: At least a couple posts so far report not seeing the same behavior I did. I'm glad if it's a non-issue, and I can't explain why it happened to me. I can just suggest if you have similar issues, it might be worth it to give this method a try.
submitted by chinawat to Bitcoin [link] [comments]

Bitcoin Core 0.11.0 released | Wladimir J. van der Laan | Jul 12 2015

Wladimir J. van der Laan on Jul 12 2015:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Bitcoin Core version 0.11.0 is now available from:
<https://bitcoin.org/bin/bitcoin-core-0.11.0/>
This is a new major version release, bringing both new features and
bug fixes.
Please report bugs using the issue tracker at github:
<https://github.com/bitcoin/bitcoin/issues>
The entire distribution is also available as torrent:
magnet:?xt=urn:btih:82f0d2fa100d6db8a8c1338768dcb9e4e524da13&dn;=bitcoin-core-0.11.0&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Fopen.demonii.com%3A1337&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F 
Upgrading and downgrading

How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).
Downgrade warning
Because release 0.10.0 and later makes use of headers-first synchronization and
parallel block download (see further), the block files and databases are not
backwards-compatible with pre-0.10 versions of Bitcoin Core or other software:
  • Blocks will be stored on disk out of order (in the order they are
received, really), which makes it incompatible with some tools or
other programs. Reindexing using earlier versions will also not work
anymore as a result of this.
  • The block index database will now hold headers for which no block is
stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data
directory. Without this your node will need start syncing (or importing from
bootstrap.dat) anew afterwards. It is possible that the data from a completely
synchronised 0.10 node may be usable in older versions as-is, but this is not
supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility. There are no
known problems when downgrading from 0.11.x to 0.10.x.
Important information

Transaction flooding
At the time of this release, the P2P network is being flooded with low-fee
transactions. This causes a ballooning of the mempool size.
If this growth of the mempool causes problematic memory use on your node, it is
possible to change a few configuration options to work around this. The growth
of the mempool can be monitored with the RPC command getmempoolinfo.
One is to increase the minimum transaction relay fee minrelaytxfee, which
defaults to 0.00001. This will cause transactions with fewer BTC/kB fee to be
rejected, and thus fewer transactions entering the mempool.
The other is to restrict the relaying of free transactions with
limitfreerelay. This option sets the number of kB/minute at which
free transactions (with enough priority) will be accepted. It defaults to 15.
Reducing this number reduces the speed at which the mempool can grow due
to free transactions.
For example, add the following to bitcoin.conf:
minrelaytxfee=0.00005 limitfreerelay=5 
More robust solutions are being worked on for a follow-up release.
Notable changes

Block file pruning
This release supports running a fully validating node without maintaining a copy
of the raw block and undo data on disk. To recap, there are four types of data
related to the blockchain in the bitcoin system: the raw blocks as received over
the network (blk???.dat), the undo data (rev???.dat), the block index and the
UTXO set (both LevelDB databases). The databases are built from the raw data.
Block pruning allows Bitcoin Core to delete the raw block and undo data once
it's been validated and used to build the databases. At that point, the raw data
is used only to relay blocks to other nodes, to handle reorganizations, to look
up old transactions (if -txindex is enabled or via the RPC/REST interfaces), or
for rescanning the wallet. The block index continues to hold the metadata about
all blocks in the blockchain.
The user specifies how much space to allot for block & undo files. The minimum
allowed is 550MB. Note that this is in addition to whatever is required for the
block index and UTXO databases. The minimum was chosen so that Bitcoin Core will
be able to maintain at least 288 blocks on disk (two days worth of blocks at 10
minutes per block). In rare instances it is possible that the amount of space
used will exceed the pruning target in order to keep the required last 288
blocks on disk.
Block pruning works during initial sync in the same way as during steady state,
by deleting block files "as you go" whenever disk space is allocated. Thus, if
the user specifies 550MB, once that level is reached the program will begin
deleting the oldest block and undo files, while continuing to download the
blockchain.
For now, block pruning disables block relay. In the future, nodes with block
pruning will at a minimum relay "new" blocks, meaning blocks that extend their
active chain.
Block pruning is currently incompatible with running a wallet due to the fact
that block data is used for rescanning the wallet and importing keys or
addresses (which require a rescan.) However, running the wallet with block
pruning will be supported in the near future, subject to those limitations.
Block pruning is also incompatible with -txindex and will automatically disable
it.
Once you have pruned blocks, going back to unpruned state requires
re-downloading the entire blockchain. To do this, re-start the node with
  • -reindex. Note also that any problem that would cause a user to reindex (e.g.,
disk corruption) will cause a pruned node to redownload the entire blockchain.
Finally, note that when a pruned node reindexes, it will delete any blk???.dat
and rev???.dat files in the data directory prior to restarting the download.
To enable block pruning on the command line:
  • - -prune=N: where N is the number of MB to allot for raw block & undo data.
Modified RPC calls:
    • getblockchaininfo now includes whether we are in pruned mode or not.
    • getblock will check if the block's data has been pruned and if so, return an
error.
  • - getrawtransaction will no longer be able to locate a transaction that has a
UTXO but where its block file has been pruned.
Pruning is disabled by default.
Big endian support
Experimental support for big-endian CPU architectures was added in this
release. All little-endian specific code was replaced with endian-neutral
constructs. This has been tested on at least MIPS and PPC hosts. The build
system will automatically detect the endianness of the target.
Memory usage optimization
There have been many changes in this release to reduce the default memory usage
of a node, among which:
    • Accurate UTXO cache size accounting (#6102); this makes the option -dbcache
    precise where this grossly underestimated memory usage before
    • Reduce size of per-peer data structure (#6064 and others); this increases the
    number of connections that can be supported with the same amount of memory
    • Reduce the number of threads (#5964, #5679); lowers the amount of (esp.
    virtual) memory needed
Fee estimation changes
This release improves the algorithm used for fee estimation. Previously, -1
was returned when there was insufficient data to give an estimate. Now, -1
will also be returned when there is no fee or priority high enough for the
desired confirmation target. In those cases, it can help to ask for an estimate
for a higher target number of blocks. It is not uncommon for there to be no
fee or priority high enough to be reliably (85%) included in the next block and
for this reason, the default for -txconfirmtarget=n has changed from 1 to 2.
Privacy: Disable wallet transaction broadcast
This release adds an option -walletbroadcast=0 to prevent automatic
transaction broadcast and rebroadcast (#5951). This option allows separating
transaction submission from the node functionality.
Making use of this, third-party scripts can be written to take care of
transaction (re)broadcast:
    • Send the transaction as normal, either through RPC or the GUI
    • Retrieve the transaction data through RPC using gettransaction (NOT
    getrawtransaction). The hex field of the result will contain the raw
    hexadecimal representation of the transaction
    • The transaction can then be broadcasted through arbitrary mechanisms
    supported by the script
One such application is selective Tor usage, where the node runs on the normal
internet but transactions are broadcasted over Tor.
For an example script see [bitcoin-submittx](https://github.com/laanwj/bitcoin-submittx).
Privacy: Stream isolation for Tor
This release adds functionality to create a new circuit for every peer
connection, when the software is used with Tor. The new option,
-proxyrandomize, is on by default.
...[message truncated here by reddit bot]...
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009400.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

Calibre database corrupted message...need help (2 ... How to run Bitcoin Core 0.9.2.1 on external Hard Drive Helping to restore Bitcoin Wallet, wallet.dat recovery Bitcoin: Kurs-Rallye durch Zahlungs-Revolution? Bitcoin Flash Crash Below $3900, System Failure, $1.5 ...

The bitcoin qt client was catching up with the blockchain (5 days worth), when after maybe 15 minutes, it comes up with an error, "database corrupted" or something along the lines of that. I looked it up and users said to delete everthing in my %appdata/roaming/bitcoin% directy except the wallet.dat file. Try to look in the ~/.bitcoin/db.log file for more information. It is likely that your only solution is to remove the block database (either blk0001.dat, blk0002.dat or blkindex.dat). DO NOT REMOVE YOUR wallet.dat file!!! This means you will have to download the whole block chain again. This other question has tips on how to speed up that download. I'm still fairly new at the BitCoin stuff. I have Windows 7 running an ATI card mining currently on Slush's Pool with a BitCoin-Qt v0.8.1-beta Corrupt Bitcoin-QT blockchain? Close. 0. Posted by. u/HulkSmashRocks. 5 years ago. Archived [HELP!] Corrupt Bitcoin-QT blockchain? I've been using BTC-qt for about 2 weeks now, and the first week everything went fine (after spending 2 days catching up), though I was only dealing in very small amounts of BTC. About 6 days ago, I got a message near the top of client saying "Warning, Displayed ... C:\Program Files\BitcoinCore>"C:\Program Files\BitcoinCore\bin\bitcoin-qt.exe" -debug -dbcache=1024 -txindex. The issue reproduced - CPU/HDD/NET utilization went to 0%, number of processed blocks got stuck, after graceful shutdown of BitcoinCore the block database is corrupted.

[index] [34489] [30606] [45768] [12492] [46697] [30832] [26462] [26747] [33312] [3328]

Calibre database corrupted message...need help (2 ...

Communicate with Bitcoin-qt using C# - .NET. Category Howto & Style; ... Fetch Bitcoin Exchange Data For Beginners Using Websocket - Duration: 20:02. m1xolyd1an 23,293 views. 20:02 . Flat Earthers ... bitcoin p=np forum.bitcoin. pl bitcoin qt bitcoin qr code bitcoin qt synchronizing with network bitcoin qt wallet location bitcoin qt import wallet bitcoin qt synchronizing with network slow ... Der Bitcoin (BTC) hat sich einen guten Ruf als digitales Gold erworben. Doch was wäre, wenn der Bitcoin auch im Zahlungsmarkt stärker Fuß fassen könnte? Zuletzt haben die Entwickler hinter dem ... Calibre database corrupted message...need help Helpful? Please support me on Patreon: https://www.patreon.com/roelvandepaar With thanks & praise to God, and ... How to recover data from a hard drive (stuck heads: buzzing, clicking, etc) - Duration: 10:28. ... How to Set Up a Bitcoin Mining Rig w/ BITMAIN ANTMINER U2 & CGMiner - Duration: 16:19. Rasim ...

#