ClownSpider



Offline



Activity: 570

Merit: 504







Hero MemberActivity: 570Merit: 504 Me panicing because of a Core crash. Now I have to redownload the chain. Lame. July 28, 2015, 08:21:47 AM

Last edit: August 02, 2015, 03:29:30 AM by ClownSpider #1 FUCK!!!

OK, I have ***+ BTC.

On 7-22 I spent 0.********** on Purse.io Transaction accepted and completed on record, goods delivered.



Status: conflicted

Date: 7/22/15 05:**

To: 16aWEopdE*******************

Debit: -0.***** BTC

Transaction fee: -0.00001908 BTC

Net amount: -0.**** BTC

Transaction ID: *******************



On 7-20 I spent 0.************* BTC ALSO on Purse.io Transaction accepted and completed on record, goods delivered.

Status: conflicted

Date: 7/20/15 13:56

To: 16aWEo*****************

Debit: -0.********* BTC

Transaction fee: -0.00004079 BTC

Net amount: -0.********* BTC

Transaction ID: a3e523d1*********************



Today I open Bitcoin Core 10.2 and it takes a long time, then says ERROR, and crashed.

I open again. Blockchain data fucked, must redownload everything.

Error? How? Did blockchain.info rewrite the blockchain logs to backdate and steal? HOW?



Because I go to blockchain.info to check my only known account, sometimes I use blockchain.info only to look at my account balance by searching my BTC receiving address. Is this address a secret??



Suddenly my account is $0.00!!!!!!!

It says all my money was sent to another account on 2015-07-18!!

Then another, then another, then another... etc and then parked at a new wallet that is unknown to me.



HOW? How could I be broke on the 18th, when I made transactions on the 20th and 22nd?

My money was still mine and I was still using it to buy stuff on purse.io on the 20th and 22nd.

According to Blockchain.info I have been at ZERO since the 18th!!



Now my transactions say "conflicted", but my blockchain is not finished downloading and will not be for many days.



I spent the money on Purse, received the goods, and paid.



Did someone rewire the logs to make it say I went broke on the 18th and just make the 20th and 22nd transactions conflict?

WTF is going on?

Or does the blockchain just randomly reassign me new wallet addresses and I will see this after the blockchain updates?

How the fuck?

And why the heck does it need to redownload the blockchain when it still has 46.8GB of blocks?

This is stupid that the BTC Core crashes so easy then requires a full re-download! Seriously?

Whose dumb idea was that?



I am freaking out because blockchain.info has ALWAYS shown my balance just fine, until now.

ClownSpider



Offline



Activity: 570

Merit: 504







Hero MemberActivity: 570Merit: 504 Re: I think I was robbed for 48 bitcoin! Blockchain log HACKED? July 28, 2015, 10:06:12 PM #7

I was in a panic and very unhappy.

I do have a backup.

I did create a new wallet and moved BTC, then backed up wallet.dat.



The fact that I spent money after the 18th was comforting because I knew I wasnt really broke on that day.

This is the first time my only receiving address shows as empty, and as if it had forwarded the BTC elsewhere for no reason.



Quote from: Newar on July 28, 2015, 09:02:44 AM *(for future reference, it's better practice to not use the same address over and over again)



Why is it better to use a different address every time? Doesnt that just spam the blockchain with more crap data and collectively result in making it take a week to download because everyone thinks they need to keep making up new BTC addresses for each transaction?



Quote from: plarkplark on July 28, 2015, 11:42:39 AM Chill out. I'm 80% sure you're alright and the coins are safe, 95% sure if you have a few backups.



3) do a rescan with bitcoin-qt.exe -rescan (this takes HOURS)



My tipjar: 1GoodRkQnQBsTPnZDvpxCcZYw7KR98arjb



Thanks.

I will try a rescan, but it wants to redownload the "chainstate" folder.

I am not sure if it is possible to rescan that, if the core deleted it to rewrite it.

Wallet file is still here, and I did make a backup, encrypted and put someplace else.



I hate that the BTC Core is so stupid it has to rewrite perfectly good data just because one small part went bad with the BTC crash. It cant just find and rewrite that one part, or go back one day or at least back to the day of the most recent transaction when everything must have been ok, and start from that time, it has to go back to day 1! wtf.



BTC Core needs to assume the date of the last confirmed transaction was good, and only go back to that date. Not back 6+ years. Ok Thank you guys!I was in a panic and very unhappy.I do have a backup.I did create a new wallet and moved BTC, then backed up wallet.dat.The fact that I spent money after the 18th was comforting because I knew I wasnt really broke on that day.This is the first time my only receiving address shows as empty, and as if it had forwarded the BTC elsewhere for no reason.Why is it better to use a different address every time? Doesnt that just spam the blockchain with more crap data and collectively result in making it take a week to download because everyone thinks they need to keep making up new BTC addresses for each transaction?Thanks.I will try a rescan, but it wants to redownload the "chainstate" folder.I am not sure if it is possible to rescan that, if the core deleted it to rewrite it.Wallet file is still here, and I did make a backup, encrypted and put someplace else.I hate that the BTC Core is so stupid it has to rewrite perfectly good data just because one small part went bad with the BTC crash. It cant just find and rewrite that one part, or go back one day or at least back to the day of the most recent transaction when everything must have been ok, and start from that time, it has to go back to day 1! wtf.BTC Core needs to assume the date of the last confirmed transaction was good, and only go back to that date. Not back 6+ years.

ClownSpider



Offline



Activity: 570

Merit: 504







Hero MemberActivity: 570Merit: 504 Re: I think I was robbed for 48 bitcoin! Blockchain log HACKED? July 28, 2015, 10:28:44 PM #9 Ok, well now I cannot buy anything for a week now that the blockchain is redownloading the entire thing because of one little crash.

Glad the money is hopefully still mine.

But I cant use it now.

One day the blockcain will be so large that any crash may take a month to download.

I have very fast internet, but the blockchain data is a very slow download.

achow101

Legendary



Offline



Activity: 2254

Merit: 3456





bc1qshxkrpe4arppq89fpzm6c0tpdvx5cfkve2c8kl







ModeratorLegendaryActivity: 2254Merit: 3456bc1qshxkrpe4arppq89fpzm6c0tpdvx5cfkve2c8kl Re: I think I was robbed for 48 bitcoin! Blockchain log HACKED? July 28, 2015, 10:57:18 PM #12 Quote from: ClownSpider on July 28, 2015, 10:06:12 PM Why is it better to use a different address every time? Doesnt that just spam the blockchain with more crap data and collectively result in making it take a week to download because everyone thinks they need to keep making up new BTC addresses for each transaction?

Nope, it doesn't spam the blockchain with more crap. It doesn't make a difference to that at all. The reason for using different addresses for everything is for security. It makes it more difficult for people to track your payments to places and it makes it easier for you to track payments to you. Also, by using multiple addresses, it is more difficult for people to know how much Bitcoin you actually have.



Quote from: ClownSpider on July 28, 2015, 10:06:12 PM I hate that the BTC Core is so stupid it has to rewrite perfectly good data just because one small part went bad with the BTC crash. It cant just find and rewrite that one part, or go back one day or at least back to the day of the most recent transaction when everything must have been ok, and start from that time, it has to go back to day 1! wtf.

It can't because LevelDB (the database type used by Bitcoin Core) is not all that great with recovery. Once it corrupts, the data may still be readable, but parts of it won't be, and it does not know where. The corruption would not only be just at the end where the latest transactions are, but could be throughout depending on what was open at the time. The corruption also prevents Bitcoin Core from being able to open and read the database as it should. While humans can open the file and read it(with the right tools), the computer is not able to interpret the data since it comes linearly. Humans can jump around and look at the data to find stuff that we need, but the computer processes things linearly. If it receives data it doesn't recognize, then it will crash and error out. The corruption causes this erroring and it can't be fixed without rebuilding the whole database.



Quote from: ClownSpider on July 28, 2015, 10:06:12 PM BTC Core needs to assume the date of the last confirmed transaction was good, and only go back to that date. Not back 6+ years.

Since the data is read linearly, it won't ever be able to get to the point where it can read good data. Due to the corruption, it will error out and take the safe route of having to reindex the whole thing. Nope, it doesn't spam the blockchain with more crap. It doesn't make a difference to that at all. The reason for using different addresses for everything is for security. It makes it more difficult for people to track your payments to places and it makes it easier for you to track payments to you. Also, by using multiple addresses, it is more difficult for people to know how much Bitcoin you actually have.It can't because LevelDB (the database type used by Bitcoin Core) is not all that great with recovery. Once it corrupts, the data may still be readable, but parts of it won't be, and it does not know where. The corruption would not only be just at the end where the latest transactions are, but could be throughout depending on what was open at the time. The corruption also prevents Bitcoin Core from being able to open and read the database as it should. While humans can open the file and read it(with the right tools), the computer is not able to interpret the data since it comes linearly. Humans can jump around and look at the data to find stuff that we need, but the computer processes things linearly. If it receives data it doesn't recognize, then it will crash and error out. The corruption causes this erroring and it can't be fixed without rebuilding the whole database.Since the data is read linearly, it won't ever be able to get to the point where it can read good data. Due to the corruption, it will error out and take the safe route of having to reindex the whole thing. GitHub | GPG Key Fingerprint 0x17565732E08E5E41 Bitcoin Core contributor | Tip Me!: bc1qshxkrpe4arppq89fpzm6c0tpdvx5cfkve2c8kl

ClownSpider



Offline



Activity: 570

Merit: 504







Hero MemberActivity: 570Merit: 504 Re: I think I was robbed for 48 bitcoin! Blockchain log HACKED? July 29, 2015, 12:26:51 AM #16 Quote from: knightdk on July 28, 2015, 11:12:00 PM

Well the linear stuff is not just the database, but computers in general. They can't just jump around and process multiple things in different orders like humans do. What Bitcoin Core can do is migrate to a more ACID (Atomicity, Consistency, Isolation, Durability) database. That would allow it to recover better from crashes and not have to reindex every time the database corrupts. The only problem is that changing databases would require a huge rewrite of the code to support a different database and then that new version would most certainly not be backwards compatible. It would have to reindex the first time.



I wouldn't even call this jumping around. I would call it going back to a confirmed transaction and looking for the error after that point. The next version would hopefully be backwards compatible, read the current DB/chain on the system and write it locally into the new format, so that it does not need to redownload.



The download is the problem. 6 days, because the bandwidth of bitcoin's network is so slow.

So I cant buy anything for 5 more days. =(



Still better than those mother fuckers at paypal that do chargebacks 25 days after the fact. I wouldn't even call this jumping around. I would call it going back to a confirmed transaction and looking for the error after that point. The next version would hopefully be backwards compatible, read the current DB/chain on the system and write it locally into the new format, so that it does not need to redownload.The download is the problem. 6 days, because the bandwidth of bitcoin's network is so slow.So I cant buy anything for 5 more days. =(Still better than those mother fuckers at paypal that do chargebacks 25 days after the fact.

achow101

Legendary



Offline



Activity: 2254

Merit: 3456





bc1qshxkrpe4arppq89fpzm6c0tpdvx5cfkve2c8kl







ModeratorLegendaryActivity: 2254Merit: 3456bc1qshxkrpe4arppq89fpzm6c0tpdvx5cfkve2c8kl Re: I think I was robbed for 48 bitcoin! Blockchain log HACKED? July 29, 2015, 12:39:33 AM #17 Quote from: ClownSpider on July 29, 2015, 12:26:51 AM I wouldn't even call this jumping around. I would call it going back to a confirmed transaction and looking for the error after that point. The next version would hopefully be backwards compatible, read the current DB/chain on the system and write it locally into the new format, so that it does not need to redownload.

For a computer, that is jumping around. It is not in order that it is reading the file in. In order to go back to a confirmed transaction, it first needs to get through the corrupted data, which it will have no idea what that data is, before it can reach any good data. Even so, depending on what it was reading, it may be corrupted in multiple places in the database. The corruption might also might not be of the transactions, but of the file and database structure itself. If that was corrupted (which is probably the case since bad transactions can just be redownloaded) then having good transactions means nothing as it cannot read them or understand the format of the data. Just to be safe, it will reindex. Reindexing guarantees that the data it reads is not corrupted. Otherwise, the data might be corrupted and such a corruption can negatively affect the entire program.



Quote from: ClownSpider on July 29, 2015, 12:26:51 AM The download is the problem. 6 days, because the bandwidth of bitcoin's network is so slow.

So I cant buy anything for 5 more days. =(

Reindexing does not mean it is downloading. It might appear that way, but it is in fact reading the data off of the blk files and indexing them into a database in ldb files. If you were stupid enough to delete the blk files then it will be redownloading. Even so, it isn't the bandwidth of Bitcoin's network, it is your own internet bandwidth that limits the download. The bottleneck for you right now is your CPU and RAM. Reindexing is all on the CPU and the RAM. If you don't have a good CPU and enough RAM, then it will take a long time. For me, I can have a reindex done in about 15 hours. Some people have them done in 1 or 2 hours, others a few days. But the problem is on your computer, not the network. For a computer, that is jumping around. It is not in order that it is reading the file in. In order to go back to a confirmed transaction, it first needs to get through the corrupted data, which it will have no idea what that data is, before it can reach any good data. Even so, depending on what it was reading, it may be corrupted in multiple places in the database. The corruption might also might not be of the transactions, but of the file and database structure itself. If that was corrupted (which is probably the case since bad transactions can just be redownloaded) then having good transactions means nothing as it cannot read them or understand the format of the data. Just to be safe, it will reindex. Reindexing guarantees that the data it reads is not corrupted. Otherwise, the data might be corrupted and such a corruption can negatively affect the entire program.Reindexing does not mean it is downloading. It might appear that way, but it is in fact reading the data off of the blk files and indexing them into a database in ldb files. If you were stupid enough to delete the blk files then it will be redownloading. Even so, it isn't the bandwidth of Bitcoin's network, it is your own internet bandwidth that limits the download. The bottleneck for you right now is your CPU and RAM. Reindexing is all on the CPU and the RAM. If you don't have a good CPU and enough RAM, then it will take a long time. For me, I can have a reindex done in about 15 hours. Some people have them done in 1 or 2 hours, others a few days. But the problem is on your computer, not the network. GitHub | GPG Key Fingerprint 0x17565732E08E5E41 Bitcoin Core contributor | Tip Me!: bc1qshxkrpe4arppq89fpzm6c0tpdvx5cfkve2c8kl

ClownSpider



Offline



Activity: 570

Merit: 504







Hero MemberActivity: 570Merit: 504 Re: Me panicing because of a Core crash. Now I have to redownload the chain. Lame. July 29, 2015, 02:42:36 AM #18 Quote from: knightdk on July 29, 2015, 12:39:33 AM Reindexing does not mean it is downloading. It might appear that way, but it is in fact reading the data off of the blk files and indexing them into a database in ldb files. If you were stupid enough to delete the blk files then it will be redownloading. Even so, it isn't the bandwidth of Bitcoin's network, it is your own internet bandwidth that limits the download. The bottleneck for you right now is your CPU and RAM. Reindexing is all on the CPU and the RAM. If you don't have a good CPU and enough RAM, then it will take a long time. For me, I can have a reindex done in about 15 hours. Some people have them done in 1 or 2 hours, others a few days. But the problem is on your computer, not the network.



Fortunately I did not delete the block files, all 46.8GB and growing.

Perhaps the BTC network data passing through my system is new stuff and not part of the reprocessing of all blocks.

My CPU has an average of 88% CPU idle. I have a quad core MBP with 16GB Ram, my CPU is not slow.

BTC Core is using under 350MB of Ram... and an average of 40% CPU. Not using much.

My bandwidth at home is 120 MB/s up and down.



How can I speed this up if it is all CPU, it should be done quickly.



Some command line settings I should try? Fortunately I did not delete the block files, all 46.8GB and growing.Perhaps the BTC network data passing through my system is new stuff and not part of the reprocessing of all blocks.My CPU has an average of 88% CPU idle. I have a quad core MBP with 16GB Ram, my CPU is not slow.BTC Core is using under 350MB of Ram... and an average of 40% CPU. Not using much.My bandwidth at home is 120 MB/s up and down.How can I speed this up if it is all CPU, it should be done quickly.Some command line settings I should try?

philipma1957



Offline



Activity: 2786

Merit: 2636









LegendaryActivity: 2786Merit: 2636 Re: Me panicing because of a Core crash. Now I have to redownload the chain. Lame. July 29, 2015, 03:12:47 AM #19 Quote from: ClownSpider on July 29, 2015, 02:42:36 AM Quote from: knightdk on July 29, 2015, 12:39:33 AM Reindexing does not mean it is downloading. It might appear that way, but it is in fact reading the data off of the blk files and indexing them into a database in ldb files. If you were stupid enough to delete the blk files then it will be redownloading. Even so, it isn't the bandwidth of Bitcoin's network, it is your own internet bandwidth that limits the download. The bottleneck for you right now is your CPU and RAM. Reindexing is all on the CPU and the RAM. If you don't have a good CPU and enough RAM, then it will take a long time. For me, I can have a reindex done in about 15 hours. Some people have them done in 1 or 2 hours, others a few days. But the problem is on your computer, not the network.



Fortunately I did not delete the block files, all 46.8GB and growing.

Perhaps the BTC network data passing through my system is new stuff and not part of the reprocessing of all blocks.

My CPU has an average of 88% CPU idle. I have a quad core MBP with 16GB Ram, my CPU is not slow.

BTC Core is using under 350MB of Ram... and an average of 40% CPU. Not using much.

My bandwidth at home is 120 MB/s up and down.



How can I speed this up if it is all CPU, it should be done quickly.



Some command line settings I should try?

Fortunately I did not delete the block files, all 46.8GB and growing.Perhaps the BTC network data passing through my system is new stuff and not part of the reprocessing of all blocks.My CPU has an average of 88% CPU idle. I have a quad core MBP with 16GB Ram, my CPU is not slow.BTC Core is using under 350MB of Ram... and an average of 40% CPU. Not using much.My bandwidth at home is 120 MB/s up and down.How can I speed this up if it is all CPU, it should be done quickly.Some command line settings I should try?



ssd's are one way. but not this time. the slower rebuild is the best way to go.







like it or not you have enough coins (48)



to consider a few pc's that mainly hold your coins and do nothing else. 48 coins is close to 14,500 usd.



A pc with just bitcore will speed thing up I have a pc with an older quad core 16gb ram and a 250 gb ssd .



It can do a reindex in under 10 hours.



You could consider having 2 wallets with blockchain.info one with 2 or less coins one with 4 to 8 coins.



and then the rest of the coins in a safe wallet. ssd's are one way. but not this time. the slower rebuild is the best way to go.like it or not you have enough coins (48)to consider a few pc's that mainly hold your coins and do nothing else. 48 coins is close to 14,500 usd.A pc with just bitcore will speed thing up I have a pc with an older quad core 16gb ram and a 250 gb ssd .It can do a reindex in under 10 hours.You could consider having 2 wallets with blockchain.info one with 2 or less coins one with 4 to 8 coins.and then the rest of the coins in a safe wallet. I see BTC as the super highway and alt coins as taxis and trucks needed to move transactions.