--- Log opened Mon Jun 28 00:00:51 2021
02:41 < calvinalvin> A bit unsure about https://github.com/mit-dci/utreexo/pull/280. I'm fairly certain it does a lot for memttldb but not quite sure for positionMap
08:16 < dergoegge> calvinalvin: forgot to ask does btcd have compact blocks? how did you handle that with the proofs?
08:17 < calvinalvin> lol no
08:18 < calvinalvin> Ok I can't find the issue that said "hey let's implement compact blocks"
08:18 < calvinalvin> But yeah that's just one other thing in btcd that hasn't been implemented in years
08:19 < dergoegge> oh ok :D
08:19 < calvinalvin> maybe we should add stuff there and call it btcd++
08:20 < dergoegge> i was kinda hoping that core wouldn't use compact blocks for blocks-only nodes but it does so we have to handle them somehow.
08:22 < dergoegge> for IBD it doesn't really matter
08:22 < calvinalvin> I guess we can just put that on hold for now since mempool stuff isn't working
08:22 < calvinalvin> mempool then worry about compact blocks
08:23 < dergoegge> yeah
08:24 < calvinalvin> hmm that also does mean that we have to implement compact blocks in btcd too
08:25 < dergoegge> not really, it should all work without them
08:25 < calvinalvin> sure, but ideally we'd also want to test it on btcd too
08:26 < calvinalvin> anyways I'll clean up utcd this week
08:26 < dergoegge> they save bandwidth on the proofs as well so at some point it would be good to have them
08:26 < dergoegge> (but only if there is a mempool)
08:27 < calvinalvin> lots to work on :)
11:36 -!- jamesob [sid180710@id-180710.brockwell.irccloud.com] has joined #utreexo
11:36 < jamesob> roping adiabat calvinalvin into a recent assumeutxo thread: https://github.com/bitcoin/bitcoin/pull/15606#issuecomment-869921671
11:36 < jamesob> (thread is mostly irrelevant for you guys, but does talk about internal Core design to facilitate multiple background validation chainstates a la utreexo)
12:07 < adiabat> jamesob: cool thanks will take a look
12:08 < adiabat> calvinalvin: I think I might have just not committed / pushed all the changes to github, oops!
12:08 < adiabat> will try doing client IBD with it on testnet3
12:55 < adiabat> I've reproduced the same block 68088 error
12:56 < adiabat> so thats good I guess.  an error in block, say, 200 would probably be easier to find that something that errors out at block 68000 though
--- Log closed Tue Jun 29 00:00:51 2021