--- Log opened Wed Nov 04 00:00:07 2020
00:06 < kcalvinalvin> hmm I'm looking to get rid of all the udata stuff and move everything to be included in the bridgenode package
00:08 < kcalvinalvin> Also maybe `LeafData` could be renamed to `sigValData` or something since LeafData doesn't imply that it's also used for sigvalidation
00:10 < kcalvinalvin> Where should BatchProof go? If we have ttls, the proofs sent to the peers would all differ
00:11 < kcalvinalvin> Receive separately from the msgblock?
00:13 < kcalvinalvin> LeafData is awkward too. Include that in the msgblock?
01:56 -!- takinbo [~takinbo@unaffiliated/takinbo] has quit [Ping timeout: 272 seconds]
01:58 -!- takinbo [~takinbo@unaffiliated/takinbo] has joined #utreexo
03:52 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #utreexo
03:55 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 272 seconds]
03:57 -!- belcher_ is now known as belcher
08:05 < adiabat> what does "sigVal" mean?
08:05 < adiabat> oh signature validation?  It's more than that though
08:06 < adiabat> you need it to compute the leaf hash, as well as to check the signature, and also check the amount, height, other things
08:07 < adiabat> I wouldn't focus on "sig" as that's just one part, and actually if we have the compact leafdata (or whatever to call it) it's not even needed to check signaures
08:07 < adiabat> in that case it's mostly the amount
08:07 < adiabat> agree that in general the names are not great
08:08 < adiabat> Ublock and Udata are... confusing.  Also the "u" I guess stands for utreexo but... eh
12:29 < ja> seems like massachussetts passed that right-to-repair bill :)
19:02 < kcalvinalvin> hmm the hash is a commitment to all the data needed for tx validation
19:04 < kcalvinalvin> ValData? idk I guess the names matter less vs what to put in where
22:13 -!- adiabat [~adiabat@63.209.32.102] has quit [Ping timeout: 260 seconds]
22:19 -!- adiabat [~adiabat@63.209.32.102] has joined #utreexo
--- Log closed Thu Nov 05 00:00:07 2020