Matt Corallo
Matt Corallo
> Correct me if I'm missing something, but I believe the only thing we want to know is: "is this channel update supposed to stay private between me and my...
> The issue is that an additional isPrivate flag cannot be backwards-compatible with existing nodes (who will set it to 0 even for private channels), while a uses_alias flag can...
Seems like the meeting conclusion here was to either use a flag to mean "not public channel update" or have two flags as I'd proposed. Is that what you took...
LGTM, I don't have strong feelings about the field name.
That isn't something the spec should really concern itself with - the node that realized its out of date has to do *something*, but what that is is up to...
> Concept ACK, If we are going to propose a solution with minisketch I think the solution is to keep as-is with graph dump to avoid some implementation to do...
Note that with our anchor implementation we are somewhat likely to go with a "one UTXO for all anchor spends" model to avoid a lot of the complexity of managing...
Note that with package relay in bitcoin Core it’s substantially easier to implement BYO fees without needing one-output-per-channel. The current proposal for package relay should allow for one output to...
If anything we probably should be thinking of going the other direction - failing payments which are near the channel balance to make balance probing more difficult. > On Jul...