Bitcoin Forum
November 08, 2024, 11:08:14 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: What could cause an offline wallet.dat file to become worthless?  (Read 1321 times)
canton (OP)
Sr. Member
****
Offline Offline

Activity: 261
Merit: 285



View Profile WWW
August 27, 2011, 05:14:20 PM
 #1

What conditions would have to take place for a well-secured wallet.dat file to lose its meaning/integrity?

Scenario:

1) I transfer 100 BTC to a brand new wallet.dat which I've kept safe from snooping etc.
2) I burn the wallet.dat to CDR and stick it in a safety deposit box, and delete the original.
3) 10 years later, BTC still have value, so I download the latest bitcoin client and the current 2 terabyte or whatever blockchain file and try to load up my wallet.dat file

Will I still necessarily have my 100 BTC? If not, why not?

E.g. what if during the 10 year interim, a government brought 100,000 GPUs online and spoofed the blockchain into oblivion and the Bitcoin community had to come up with a new protocol? Any reason to believe that a pre-spoof-event wallet.dat file would still be legible/valid with whatever new protocol is brought online as a response to interference / quantum computing / cryptographic developments?

Apologies if this is a newbie question, but I couldn't find my answer searching this forum.

jackjack
Legendary
*
Offline Offline

Activity: 1176
Merit: 1280


May Bitcoin be touched by his Noodly Appendage


View Profile
August 27, 2011, 05:33:18 PM
 #2

  • A government brought 100,000 (?) GPUs online and started mining his hidden blockchain before your transaction
  • sha256 & ripemd160 being broken
  • Doomsday

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
joulesbeef
Sr. Member
****
Offline Offline

Activity: 476
Merit: 250


moOo


View Profile
August 27, 2011, 05:36:09 PM
 #3

yes the 100btc will still be there.

well that cdr would probably be toast, especially if you wrote onit with a sharpy and didn't buy achival cds.
Doesnt matter what the gov does, it could erase some of your transaction history but the coins would still be there.

Quote
Any reason to believe that a pre-spoof-event wallet.dat file would still be legible/valid with whatever new protocol is brought online as a response to interference / quantum computing / cryptographic developments?


Not sure if this is answerable. I guess I can say for sure, the answer is maybe.

you miught want to look over known weaknesses

mooo for rent
Callius
Newbie
*
Offline Offline

Activity: 25
Merit: 0


View Profile
August 27, 2011, 05:38:47 PM
 #4

CDs aren't made for long term storage, over 10 years the dye which indicates whats 1 or a 0 could bleed.
FreeMoney
Legendary
*
Offline Offline

Activity: 1246
Merit: 1016


Strength in numbers


View Profile WWW
August 27, 2011, 07:20:05 PM
 #5

yes the 100btc will still be there.

well that cdr would probably be toast, especially if you wrote onit with a sharpy and didn't buy achival cds.
Doesnt matter what the gov does, it could erase some of your transaction history but the coins would still be there.
 

If the government started mining from a block before the one containing his tx and that new chain keeps the lead and doesn't rerecord his tx the coins will not be there.

Play Bitcoin Poker at sealswithclubs.eu. We're active and open to everyone.
Stephen Gornick
Legendary
*
Offline Offline

Activity: 2506
Merit: 1010


View Profile
August 27, 2011, 09:52:01 PM
 #6

sha256 & ripemd160 being broken

Though this would't likely be something that happens overnight.  At a minimum, checking in on things annually would probably be recommended.

Not just should the wallet be archived but kept also should be a bootable o/s installation to be able to read that wallet.dat as well.  It wouldn't be surprising that the client ten years from now might not even use the database engine (BDB) that today's client uses.

This was briefly discussed here:
 - http://bitcointalk.org/?topic=2348.0


Unichange.me

            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █


spruce
Full Member
***
Offline Offline

Activity: 140
Merit: 100


View Profile
August 27, 2011, 10:03:00 PM
 #7

Why trust the optical storage medium like that? Send the money to a paper bitcoin wallet. Paper lasts much longer, even regular paper let alone archival paper. For better security hand-code the private key with an unbreakable one-time code (see link in my sig).
makomk
Hero Member
*****
Offline Offline

Activity: 686
Merit: 564


View Profile
August 27, 2011, 10:37:26 PM
 #8

Some government trying to spoof the blockchain into oblivion using masses of GPUs shouldn't cause your old bitcoins to become invalid unless it wipes out all bitcoins in existence. There are already periodic blockchain lock-ins that fix the block chain prior to that point in stone; if we need to change over to a new protocol whoever designs it could just lock-in the entire classic Bitcoin blockchain up to that point and build from there. Alternatively they could choose to start over from scratch, in which case all Bitcoins will be affected.

The only things that could cause a Bitcoin wallet that's been successfully stored for a long time to be invalid without invalidating all Bitcoins are a serious break in either elliptic curve crypto or SHA-256, or a deliberate consensus to invalidate them on the part of other Bitcoin users and mining pools. For example, if transaction volume gets too high mining pools and other full nodes might decide that storing the full blockchain is too expensive and throw away the older parts, either destroying older Bitcoins that have been sitting idle or making them increasingly hard to spend.

Quad XC6SLX150 Board: 860 MHash/s or so.
SIGS ABOUT BUTTERFLY LABS ARE PAID ADS
canton (OP)
Sr. Member
****
Offline Offline

Activity: 261
Merit: 285



View Profile WWW
August 29, 2011, 04:47:10 PM
 #9

For example, if transaction volume gets too high mining pools and other full nodes might decide that storing the full blockchain is too expensive and throw away the older parts, either destroying older Bitcoins that have been sitting idle or making them increasingly hard to spend.

First of all, thanks for everyone's replies. Although I wasn't really aiming for a discussion re: the survivability of various media, I hadn't considered hardcopy (paper) wallets before. Neat!

Anyway, Makomk, thanks for your insights. One followup question re: what happens if mining pools start ditching the oldest parts of the blockchain:

If I take a wallet out of storage from time to time and send its entire amount of BTC to a new wallet, am I correct in assuming these coins are essentially re-minted as "new" coins that appear later in the blockchain, circumventing this potential problem?

Pieter Wuille
Legendary
*
qt
Offline Offline

Activity: 1072
Merit: 1181


View Profile WWW
August 29, 2011, 04:54:34 PM
 #10

If *anyone* forks off an older part of the block chain, to erase your precious transactions, the whole bitcoin community will notice. Many things can happens surrounding the block chain and the bitcoin's value, but it won't go unnoticed. Furthermore, even if that would happen, and allowed to pass, your own transaction that credited your offline address isn't necessarily invalid.

I do Bitcoin stuff.
kjj
Legendary
*
Offline Offline

Activity: 1302
Merit: 1026



View Profile
August 29, 2011, 06:27:38 PM
 #11

Anyway, Makomk, thanks for your insights. One followup question re: what happens if mining pools start ditching the oldest parts of the blockchain:

If I take a wallet out of storage from time to time and send its entire amount of BTC to a new wallet, am I correct in assuming these coins are essentially re-minted as "new" coins that appear later in the blockchain, circumventing this potential problem?

Your questions seem to come from a misunderstanding of the way this all works.  Don't feel bad, it is a big system and hard to get your head around.

There are no coins.

A transaction redeems one or more previous transactions, and has one or more outputs.  Redeemed transactions are redeemed as a whole, never in parts.  If the redeemed transactions have more value than the combined value of the outputs, the difference is a mining fee.

There is a safe way to discard old transactions, and that is to delete transactions that were redeemed more than X blocks in the past, where X is large enough that you feel confident that the chain can't be reverted that deeply.  Recent reports suggest that around 75% of old transactions could be pruned in this way.

If that isn't good enough, and some miners want to discard old transactions that haven't been redeemed yet, those miners will see transactions that attempt to redeem them as invalid and won't include them in new blocks.  This practice is unlikely to become dominant though, because they will be missing out on potential fees when those transactions are eventually redeemed, so other miners will have even more inventive to keep them.  Actually, I doubt that even a single miner will ever do unsafe pruning for that reason.

And yes, if you send your balance to a new wallet, the new wallet will have a newly created and verified transaction.  In that sense, the "coins" will be new.  In the other sense, either the coins still don't exist, or they are just as old as before.

17Np17BSrpnHCZ2pgtiMNnhjnsWJ2TMqq8
I routinely ignore posters with paid advertising in their sigs.  You should too.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!