pull down to refresh

0 sats \ 3 replies \ @denationalized OP 8 Dec \ parent \ on: Have your payments faile more frequently in Q3-Q4 of 2024 than previously? lightning
You wrote in this guide:
Use several LN wallets, not just one, spreading your liquidity on few channels, I would say 2-3 channels per wallet/node. No need for more. Do not open tiny channels like 10k-20k-50k-100k. Open like min 500k-1M-2M per channel. Depends also of your spending habits, if you have large amounts moving or small amounts. Think in how much a channel can handle a payment of yours, in and out. Try to have each LN wallet for a specific spending habit (one for zaps, tips,small donations, one for buying beers, groceries, one for buying sats from exchanges, one for swaps etc as you desire). Always move around funds from those channels ! Do not keep them with more than 50% of the balance on the peer side. If you know that will not use a depleted channel anymore, but you hope that someday (you don't know when) you will use it to receive more sats, better just close it and buy an inbound channel on the fly from many other LSP that are already offering on the fly inbound channels. If you already bought such "inbound channel" and you have a contract for 6 months or 1 year with the LSP, you better use it in this period.
I treated my core lightning wallet as a spending wallet whenever there were any merchants willing to accept sats. 7 channels with maximum amounts. But over the last months the lightning payments started to fail. I am now forced to use onchain Bitcoin for my living expenses.
write
preview
0 sats \ 2 replies \ @DarthCoin 8 Dec
You imply that the whole LN is not working anymore, when in fact is your own single node that is not doing well. Consider changing your node policies. LN is just fine.
reply
0 sats \ 1 reply \ @denationalized OP 8 Dec
Due to my circumstances, I am rarely online - every couple of days when I need to spend sats I am online for a couple of hours. But being rarely online was never a problem when it came to spending sats in previous years. I use default settings. As an attempt of dealing with the problem I even created a channel with a non-onion node (with wallet of satoshi) and tried to pay over IPv4 instead of over Tor. All this top no avail. The payments do not go through and I always get this type of message:
 "code": 210,
   "message": "Ran out of routes to try after 4 attempts: see `paystatus`",
   "attempts": [
      {
         "status": "failed",
         "failreason": "failed: WIRE_TEMPORARY_CHANNEL_FAILURE (reply from remote)",
         "partid": 0,
         "amount_msat": 50000000
      },
      {
         "status": "failed",
         "failreason": "failed: WIRE_TEMPORARY_CHANNEL_FAILURE (reply from remote)",
         "partid": 1,
         "amount_msat": 50000000,
         "parent_partid": 0
      },
      {
         "status": "failed",
         "failreason": "failed: WIRE_TEMPORARY_CHANNEL_FAILURE (reply from remote)",
         "partid": 2,
         "amount_msat": 50000000,
         "parent_partid": 1
      },
      {
         "status": "failed",
         "failreason": "failed: WIRE_TEMPORARY_CHANNEL_FAILURE (reply from remote)",
         "partid": 3,
         "amount_msat": 50000000,
         "parent_partid": 2
      }
   ]
}
reply
10 sats \ 0 replies \ @DarthCoin 9 Dec
Check the logs for you LN graph sync. I think you are not synced correctly and that's why you get WIRE_TEMPORARY_CHANNEL_FAILURE (reply from remote)
reply