Matt Corallo
Matt Corallo
Ha, sorry, this was indeed unclear. I meant "which node in the path has to meet the provided htlc_min/htlc_max/cltv_expiry". The spec doesn't specify.
Wait, the two of you just said different things, though - @thomash-acinq said that the HTLC that arrives at the *first* node must satisfy the requirements but then @t-bast said...
The specific case where it came up for us may be illustrative - we are treating the blinded path as a single hop for pathfinding purposes, but our fuzzer decided...
Sure, that was my understanding as well, but I was noting that the BOLTs are unclear and wanted to make sure people were doing the same thing (and it sounds...
Either way, point is the BOLTs need to be clarified.
Hmm, the examples you listed I think are bad reasons for this. Is there a stronger reason to want this? > In the Hold Invoice case, this information could prevent...
Yea, its just a bit hard to evaluate without that change - there's presumably some state that can move into the flow handler...
> We're calling send_peer_storage from ChainMonitor, which doesn't have access to entropy_source to derive random_bytes. Is there any other way to generate random bytes? We'll need to provide `ChainMonitor` with...
Needs rebase now :tada:
Oops, was travelling last week. > Of course using only functional blocks as spans makes it less able to answer the types of questions I think you specifically want, eg...