j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM¥<div class="post"><b><span style="font-size: 9pt !important; line-height: 1.3em;">see <a href="http://bitcointalk.org/index.php?topic=921.0">http://bitcointalk.org/index.php?topic=921.0</a> for continued discussion about backups</span></b><br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=873.msg10725#msg10725">Quote from: nelisky on August 23, 2010, 12:38:10 AM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=873.msg10297#msg10297">Quote from: satoshi on August 19, 2010, 08:14:01 PM</a></div><div class="quote">- Warning not to mess around with your wallet.dat file. It's a database file, it's not as simple as you think. In this Beta version, we haven't had time to try and tinker-proof it yet. It may not work as expected if you start swapping it around.<br/></div><br/>So how simple is it? I'm just now thinking about foolproof backups on the lottery site I posted about yesterday, and I'm struggling to find information on this. Can bitcoind dump it in a safe state, or at least flush it on request? If I backup the file mid transaction, do I loose the whole thing or just the update in progress? When do I need to backup? Every outgoing transfer is obvious, there are key pairs created automagically, but what about transfers received? the key pair we already had, no new address needed to be created afaict. Or does bitcoin do the same change dance on the receive side too?<br/><br/>This part is, I believe, the most critical of them all. While MSE and clock skews may prevent normal program usage, the wallet backup issues have made people loose a bunch of coins which, obviously, sucks and doesn't do much on supporting continued usage.<br/></div><br/>This comment seems worthy of having this thread appear threaded so that discussion could expand exponentially. In the case that this forum is not threaded, however, I will briefly state (without getting offtopic) that there should be some sort of established procedures or mechanisms to handle either regular interval or triggered backups without interrupting the Bitcoin process. It seems that it is essential to "perfect" data reliability/availability as best as possible so as to provide more incentive for adoption.<br/><br/>Actually, it's not so offtopic.<br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=873.msg10297#msg10297">Quote from: satoshi on August 19, 2010, 08:14:01 PM</a></div><div class="quote">- Warning not to mess around with your wallet.dat file. It's a database file, it's not as simple as you think. In this Beta version, we haven't had time to try and tinker-proof it yet. It may not work as expected if you start swapping it around.</div><br/>Instead of introducing a warning or establishing a precedence of caution and delay in handling wallet file or backups, as I suggested above, the implementation for backing up data/wallet file needs more thought/establishment.<br/><br/>I am not familiar with the current process/structure of data flow that occurs, but if someone could write up or draw a diagram or something that shows how the flow of data appears then perhaps with this diagram-liek information, others, like myself, can help to understand how things work and maybe offer suggestions for improvements or to recognize things like after which data sent/received is worthy of implementing a kind of automated/triggered backup or similar action.<br/><br/><b><span style="font-size: 9pt !important; line-height: 1.3em;">see <a href="http://bitcointalk.org/index.php?topic=921.0">http://bitcointalk.org/index.php?topic=921.0</a> for continued discussion about backups</span></b></div> text/html
https://whatsonchain.com/tx/df4fa0f5a2b4b3e8dec089dd4e91205e544c652d4ab0928deb11c8e4bd1cd5cf