Lagrang3

The problem with the bad memory access in your version is making the plugin fail before it can produce a useful log message that could be helpful to know what...

After patching the bad memory access I can make the plugin break by calling `renepay` with the same invoice on two different terminals at the same time: ``` 2024-02-06T08:40:52.807Z DEBUG...

I found a race condition. The chain of events after an rpc call to `renepay` are the following: ``` (rcp) renepay | | json_pay: parses the invoice | | (rpc)...

Hi @pratapc65 , is likely that transaction `a8c998d1ba872bc8003386ffda397c73acf60d74242af8ea0bce4dc8438cae24` is not in your node's mempool. Definitely is not in mine's ```bash $ cln getutxout a8c998d1ba872bc8003386ffda397c73acf60d74242af8ea0bce4dc8438cae24 0 { "amount": null, "script": null...

Trying to re-broadcast the transaction ```bash $ bitcoin-cli sendrawtransaction 020000000001012ad6a1f4fdf62b638defdd95cbfea66509a9c4522bad0e7a877cc35c8ff3a22001000000000c46af80028f62000000000000160014c02712a2d3f09e7efadfce3d4c76501ba53ed561650426000000000022002059cfd4bad3f6c8d6899b5bae169de4e3e3ff4a1e2a158a1bfd2f038e2ac50896040047304402206c3afe012479a046fe380785a64c0cccc2e928915a979ba9cb5453daa58acd8402200150871c063b95a625b9c887890d4308a617798f8bcba64e4896398780bf726c0147304402203bffba3835de33c37ae26d3b496e6625b54dbd39194c566b4b3138289604ef1602207f6469897e7971961d165280a2c4cd14bfde84849d5697b1aa207db96bcc8b7c014752210207c263af1717e8df4790d5dc3d433aefa98c0169286ad78ff46b17430d4bcdfa210239b38299018f11e10ec3deb11534da31d8cfc650b056fc70afc92299963a5fa452ae5835c120 error code: -26 error message: mempool min fee not met, 273 < 524 ``` I think *package relay* (https://bitcoinops.org/en/topics/package-relay/) is...

> @Lagrang3 `minrelaytxfee` can be used to reduce the minimum relay txn feerate in the mempool, right? Nah, the problem was the mempool size that day. After 300MB (`maxmempool`) small...

I think the problem is with the parallel channels. On `l2` `channeld` is only seeing one channel with his peer `l1`. I can see that `lightningd`'s peer structure has a...

There is a channel selection in `lightningd` before forwarding: https://github.com/ElementsProject/lightning/blob/9d88ce3b592ca42a01104758313b9b2806d40230/lightningd/peer_htlcs.c#L1215 Is that a good idea, why wouldn't we try to forward right on the channels we have been requested to?...

Though non-strict forwarding is allowed: https://github.com/lightning/bolts/blob/master/04-onion-routing.md#non-strict-forwarding

You closed the channel unilaterally, therefore the output sending funds to you has a timelock. You can get the value of this timelock with the command ``` lightning-cli listpeerchannels |...