1 2016-02-22 00:02:47 <kanzure> phantomcircuit: thanks for the email to -discuss
 2 2016-02-22 00:03:20 <phantomcircuit> kanzure, lol'd at his response
 3 2016-02-22 00:03:40 <kanzure> profound, right?
 4 2016-02-22 00:06:28 <kanzure> "That is false and you know it, Patrick.  " hahaha what
 5 2016-02-22 00:06:42 <kanzure> in fact it is true and phantomcircuit is well aware of its truthfulness
 6 2016-02-22 00:06:54 <kanzure> i am worried that these antics are going to cause me brain damage
 7 2016-02-22 00:35:50 <kanzure> morcos: sorry for sending to bitcoin-discuss again. you were right. i thought bitcoin-discuss was not in my "To:" line. sorry, i'll cease.
 8 2016-02-22 01:01:46 <wallet42> where are the ops?
 9 2016-02-22 01:03:28 <phantomcircuit> wallet42, on vacation
10 2016-02-22 01:03:35 <phantomcircuit> why?
11 2016-02-22 01:27:01 <wallet42> just wondering
12 2016-02-22 16:55:09 <coin_trader> hey guys - any tips on repairing or salvaging keys from a corrupted core wallet?
13 2016-02-22 16:55:11 <coin_trader> 93meg wallet
14 2016-02-22 16:55:40 <coin_trader> -zapwallettxes did nothing..
15 2016-02-22 16:56:26 <coin_trader> 2016-02-22 16:27:12 Salvage(aggressive) found 336171 records
16 2016-02-22 16:56:26 <coin_trader> 2016-02-22 16:27:17 Warning: Warning: wallet.dat corrupt, data salvaged! Original wallet.dat saved as wallet.{timestamp}.bak in "/root/.bitcoin"; if your balance or transactions are incorrect you should restore from a backup.
17 2016-02-22 16:56:40 <coin_trader> that's bout as far as can be gotten... advice/tips?
18 2016-02-22 17:02:14 <sturles> Did you try -salvagewallet (iirc)?
19 2016-02-22 17:02:49 <sturles> Or just restore a good version from backup.
20 2016-02-22 17:02:57 <coin_trader> how far back can the backup work?
21 2016-02-22 17:03:01 <coin_trader> i have a 19meg version of the wallet
22 2016-02-22 17:03:04 <coin_trader> but core isn't HD is it?
23 2016-02-22 17:04:13 <sturles> A backup will work fine up to ~100 transactions back.  Depends on your keypool.
24 2016-02-22 17:05:16 <coin_trader> yea that's not an option
25 2016-02-22 17:05:20 <coin_trader> this is a heavily used node...
26 2016-02-22 17:05:32 <coin_trader> way more than the default keypool size of 10001 since that old backup
27 2016-02-22 17:05:56 <coin_trader> salvage doesn't seem to help
28 2016-02-22 17:06:10 <sturles> Is the wallet encrypted?
29 2016-02-22 17:06:19 <coin_trader> don't believe so
30 2016-02-22 17:06:46 <sturles> There is a script somewhere on the interwebs which will search your entire disk for private keys, and try to reconstruct a wallet.
31 2016-02-22 17:07:10 <sturles> Google will probably find it faster than I can..
32 2016-02-22 17:10:40 <sturles> Have you been running a self-compiled version, btw?  Possibly using a newer version of libdb?
33 2016-02-22 17:10:44 <coin_trader> nope
34 2016-02-22 17:10:46 <coin_trader> stock core
35 2016-02-22 17:10:53 <sturles> OK
36 2016-02-22 17:11:06 <coin_trader> i'm a little agitated to be honest... because this is stock core, and it's a heavily used node, and it should be more than OK to handle what it's doing
37 2016-02-22 17:11:22 <coin_trader> the fact i have a corrupted wallet with possibly lost coins is very unsettling since it's apparently not HD
38 2016-02-22 17:11:32 <helo> nothing substitutes for a proper backup regimen
39 2016-02-22 17:11:44 <sturles> Ehm, yes.  Backups are recommended..
40 2016-02-22 17:12:48 <sturles> I make sure my keypool match my backup schedule with margin for a few missed backups..
41 2016-02-22 17:13:27 <coin_trader> so... barring backups, what are ways of extracting private keys from this garbage?
42 2016-02-22 17:13:30 <sturles> If keypoololdest is newer than your last backup, you should worry.
43 2016-02-22 17:13:45 <sturles> Google for the script I mentioned.
44 2016-02-22 17:18:37 <coin_trader> sturles: is it this one? https://gist.github.com/msm595/7595164
45 2016-02-22 17:20:45 <sturles> Try it.  The one I found via bitcointalk a few years back could work with entire partitions.
46 2016-02-22 17:21:10 <sturles> In case your file system is b0rken as well.
47 2016-02-22 18:48:53 <coin_trader> sturles: found it & it succeeded. thanks very much for your earlier help - actually wound up finding .02 BTC from some unknown tx in the wallet too!
48 2016-02-22 19:21:43 <sturles> W00t!  Perhaps I should try the same. :-)
49 2016-02-22 21:38:34 <TZander> Someone here know a bit more about SW?  I'm wondering how a node that gets an old block can validate the transactoions in them to be valid if the signatures etc are not available in the block.
50 2016-02-22 21:46:06 <TD-Linux> TZander, you mean an old node that doesn't understand SW? a new node will have all of the signatures
51 2016-02-22 21:47:08 <TZander> TD-Linux: For instance a newly synching node. It does do SW. Where does it find the, for instance, 2 months old signatures?
52 2016-02-22 21:50:11 <bitanarchy> TZander: right now I suppose the signatures are still in the block... but with segwit they can also not be in the block??
53 2016-02-22 21:51:51 <TZander> Its not supposed to be in the block anymore, is it?  Thats kinda the point, I though.
54 2016-02-22 21:53:19 <helo> it just moves the signature data out of what is hashed to create the transaction id
55 2016-02-22 21:53:48 <TD-Linux> TZander, take a look at the BIP: https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki
56 2016-02-22 21:56:35 <TD-Linux> TZander, and actually this BIP might more directly answer your question: https://github.com/bitcoin/bips/blob/master/bip-0144.mediawiki
57 2016-02-22 21:59:03 <TZander> TD-Linux: no, the first is best. The second doesn't show what goes into blocks.
58 2016-02-22 22:00:02 <TD-Linux> but yeah basically the signatures are transmitted and available