--- Day changed Thu Oct 18 2018 01:29 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket 04:24 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 2.2] 04:29 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket 06:52 -!- quitobro [642558df@gateway/web/freenode/ip.100.37.88.223] has joined #joinmarket 06:53 < quitobro> hmmm so are there any options for "rescanning" the blockchain for wallet history/wallet transactions that are missing from the output of `wallet-tool.py history` invocation? 06:53 < quitobro> if i were running a full node i'd just do a rescan 06:53 < quitobro> but i have a pruned node 06:53 < quitobro> :( 07:27 < belcher> theres a github issue on how to rescan while pruned 07:27 < belcher> it involves having your node download the blocks again 07:27 < belcher> sec 07:27 < belcher> quitobro https://github.com/JoinMarket-Org/joinmarket/issues/431#issuecomment-190683145 07:28 < belcher> there was someone else i linked this to a couple of days ago.. maybe i should reopen that issue 07:29 < waxwing> belcher, quitobro it occurs to me we really should have added the txid to logs/yigen-statement.csv ; obv not the same as history, but at least you could easily audit what joins you did. 07:29 < waxwing> just a side point, probably, but still 07:30 < belcher> yeah could do 07:30 < belcher> one concern is that may encourage people to put all the txids into a blockchain explorer, which might be bad for privacy 07:30 < belcher> but in practice i bet not many people will even check 07:31 < waxwing> yes part of it is, i'm not even sure that many users even know that log exists. still, it's only for makers, they're more likely to know i guess. shrug, not the hugest of deals. 07:32 < belcher> yeah fair enough 07:34 < quitobro> i wonder if i allocated more disk to my prune param e.g. `prune=20480` instead of say `prune=550` that i wouldn't have as many missing transactions? since that would mean i have a larger % of most recent blockchain history? 07:34 < belcher> no thats not how it works 07:35 < belcher> bitcoin core stores information about your transactions inside wallet.dat, so pruning is irrelevant 07:35 < belcher> having a bigger pruning parameter might be useful because you could still rescan the blocks you do have 07:35 < belcher> theres the rpc call rescanblockchain which allows setting a start and end height 07:36 < waxwing> neutrino-izing this app would be nice. i volunteer to do the GCS stuff :) 07:36 < waxwing> ofc it's not working in Core yet, so, no rush :) 07:36 < belcher> yet another way could be to have core just download blocks when you want to rescan 07:37 < belcher> so you call `rescanblockchain` and one of the things it does is download blocks and then delete them 07:38 < belcher> yet another thing we could do is have another kind of blockchaininterface that uses `scantxoutset`, that would work with pruning and never require rescanning (but doesnt give you the history, only current utxos) 07:41 < quitobro> belcher: `rescanblockchain` will scan for JM wallet's addresses or the Bitcoin Core wallet? i guess as long as you've run `wallet-tool.py` and imported your wallet into Core it will work 07:41 < belcher> so the way it works, JM's wallet is just a wrapper around Bitcoin Core's wallet 07:42 < belcher> so rescanblockchain will rescan for transactions and add them to the Bitcoin Core wallet, then when you run wallet-tool they will appear as being in JM's wallet 07:42 < belcher> yes for rescanblockchain to find transactions, you need to already have all your addresses imported as watch-only 07:49 < quitobro> belcher: cool thanks, nice to learn about these RPC calls that i didn't know existed 07:50 < belcher> rescanblockchain was only added in 0.16 btw :p 07:51 < quitobro> super useful that one! 08:00 < quitobro> anyone know if there's a way to add more history to my pruned blocks directory, without doing an entire reindex? 08:00 < quitobro> i.e. i have bumped my prune param in bitcoin.conf 08:00 < quitobro> will my node just "know" to store more history, going backwards from my current pruneheight? 08:01 < quitobro> giving it a whirl anyway ha 08:07 -!- quitobro [642558df@gateway/web/freenode/ip.100.37.88.223] has quit [Ping timeout: 256 seconds] 08:10 < belcher> when he comes back someone ask him to let us know how it goes, posting on that github issue maybe 08:48 -!- quitobro [d0b9b842@gateway/web/freenode/ip.208.185.184.66] has joined #joinmarket 08:49 < quitobro> if anyone replied/commented to my previous comments can you repeat them? lost chat history because it disconnected 08:49 < quitobro> it = IRC client 08:50 < belcher> what was the last message you saw from us? 08:50 < belcher> we saw giving it a whirl anyway ha 08:50 < belcher> im guessing the high cpu usage of rescanblockchain made your computer slow down and your IRC lagged out :p 08:55 < quitobro> yea that's last one i sent, didn't see anything after that 08:56 < quitobro> ha no it was fine for rescan; my issue is i don't have blocks below height 525350 08:56 < quitobro> and i had JM wallet tx's prior to that 08:56 < belcher> i said when he comes back someone ask him to let us know how it goes, posting on that github issue maybe 08:58 < quitobro> oh i just realized `prune=` can take a block height target too right? 08:58 < belcher> no 08:59 < quitobro> Manual block pruning can now be enabled by setting -prune=1. Once that is set, the RPC command pruneblockchain can be used to prune the blockchain up to the specified height or timestamp. 08:59 < quitobro> yea i guess this supposes you have the entire blockchain already 08:59 < quitobro> and are pruning to specific height 08:59 < quitobro> shit i think i have to reindex, again :( 09:01 < belcher> oh, TIL 09:02 < belcher> thats for stuff like armory i guess 10:07 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 2.2] 10:35 -!- quitobro [d0b9b842@gateway/web/freenode/ip.208.185.184.66] has quit [Ping timeout: 256 seconds] 12:05 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 12:08 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Read error: Connection reset by peer] 12:10 -!- belcher [~belcher@unaffiliated/belcher] has joined #joinmarket 12:17 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #joinmarket 12:18 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 260 seconds] 12:40 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket 12:43 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has quit [Remote host closed the connection] 15:18 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 2.2] 16:34 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has joined #joinmarket 17:09 -!- M1 [~Michail@michail.com] has quit [Ping timeout: 268 seconds] 17:14 -!- M1 [~Michail@michail.com] has joined #joinmarket 19:56 -!- lnostdal [~lnostdal@77.70.119.51] has joined #joinmarket 20:04 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 252 seconds] 20:20 -!- lnostdal [~lnostdal@77.70.119.51] has joined #joinmarket 20:40 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 245 seconds] 20:56 -!- lnostdal [~lnostdal@77.70.119.51] has joined #joinmarket