Matt Corallo
Matt Corallo
> I think that pattern-matching / imbuing v3 is doable (that sounds like a concept ack for v3?). Assuming sibling eviction in v3, so far, it seems like it applies...
Looking at my code, I see `version: 2`, `lock_time: (0x20
That would still result in an HTLC getting sent a few hops to a blinded path introduction point and then holding liquidity on those hops into the recipient comes online.
Even in that case I don't think its really acceptable - senders really need to be aware that their capital is about to be locked up for potentially-hours before they...
Can't lnd also send an error message in addition to the bogus channel _reestablish? That would make it robust both with existing nodes and older nodes.
I guess I don't understand why that's a requirement? If you're closing using an SCB, your setup is hosed. Having to upgrade as a step in that process doesn't seem...
> from the PoV there's been no sort of feature bit shift or feature negotiation. FWIW, `error` messages have always been the spec-mandated way to close a channel and request...
> Do y'all also interpret this section as such? Fwiw, our change here shouldn't have broken SCB, by my read of the code, we do some initial sanity checks first,...
Not necessarily? If they're erroring on the bogus message they should disconnect (or at least that's historically been their interpretation of the spec, not sure what it says anymore), and...
Looks like on Intel, assuming that MSR is userspace-reachable, we can just set that and move on. If not, we need a kernel API which doesn't exist yet.