Matt Corallo

> It wasn't a warning, but a hard failure. Oh! That's the source of a lot of confusion here, I think. What version of wasm-ld are you using? Locally that's...

> As mentioned, it was rust-lld that failed on me Ah, I missed that, thanks for calling it out. IIUC rust-lld is the same as system-lld, but built from the...

``` $ lld lld is a generic driver. Invoke ld.lld (Unix), ld64.lld (macOS), lld-link (Windows), wasm-ld (WebAssembly) instead ``` Its possible rust-lld is actually completely different, then, or its just...

I was actually using `clang` for linking for cross-language LTO, not building directly with `cargo`, so my experience is definitely not 100% representative (and I originally pushed for the wasi...

But the sender knows how much it's overpaying, so there's no issue with the onion needing to be flexible. I agree I'm not aware of a reason why this needs...

IIUC you're suggesting overpaying by reducing the amount in the onion. You shouldn't do this - this allows the second-to-last node to steal the overpayment amount. This isn't a huge...

Without looking at it, I thought the htlc-min was set by a node and applied for incoming HTLCs. ie you're always protected cause you apply it when you receive an...

Then I don't understand your original comment - a node can require overpayment through the htlc_min in the `channel_update`, yes, but no matter what it cannot under-forward because the values...

> I don't think interpreting fees as signed integers and rounding up to zero can do any harm. It also doesn't allow anyone to experiment materially with negative fees. This...

As mentioned on the call, I'm a bit dubious of the need for signaling today - it materially hurts privacy across the network, so unless we have a need to...