Issues with commenting & 1sat payments - self hosted AlbyHub \ stacker news ~meta

pull down to refresh

Issues with commenting & 1sat payments - self hosted AlbyHub

418 sats \ 16 comments \ @Arceris 18 Nov meta

I've been suddenly having trouble posting comments that are priced at 1 sat. I also tested with zaps, and 1sat zaps fail as well. They seem to fail instantly, and show canceled in the wallet history & on AlbyHub (running on my Start9). However, there is no record of the TX failing (or even attempting) in the lightning node itself.

Bigger payments do work, and I tried a 2sat zap which did work. I don't comment too often, but I zap every day, and my zaps are well above 1sat, so I didn't notice until I wanted to write some comments today and they all came back as failing...

Has anyone else seen this? Is there a setting that I somehow messed up? It's odd that the 2sat zap went through fine, and much bigger payments have been working without issue (both outgoing and incoming), so it's not a liquidity issue.

view all related items

12 sats \ 8 replies \ @k00b 18 Nov

Hm given they aren’t showing on your lightning node, I wonder if Alby Hub is enforcing some minimum

0 sats \ 7 replies \ @k00b 18 Nov

@Alby do you know what might cause this?

1152 sats \ 6 replies \ @Arceris OP 18 Nov

I am opening a direct channel to stacker news to see if this will mitigate. I'm seeing "no route" errors in alby:

2024-11-18T14:18:04-07:00 {"app_id":4,"bolt11":"lnbc10n1pnnhtctpp5frtldan6apvdn6ywu2y7nps2lqsn6rfuef785tqs563hn7s0uycqdpg2d8r5gr6v9czqvfqwdshgueqw3hjqgehxuenzdf3cqzzsxqzjcsp5wyalknd26nchkdq0ksl0em56uk5hhw6t0nle34t0nmdpxjrp4j2s9qxpqysgqqf8jlugmgkumygw4vu30xmanglxzxawtyzfs7w60muppu7ewaxt9lpvxz4h6cg7esly4u38rajtlls4nns46gxe73eq40ftvntfwl8sqw4mdnw","level":"info","msg":"Sending payment","request_event_id":1822,"time":"2024-11-18T21:18:04Z"}  
2024-11-18T14:18:04-07:00 {"level":"info","msg":"Received payment failed notification","payment":{"payment_hash":"48d7f6f67ae858d9e88ee289e9860af8213d0d3cca7c7a2c10a6a379fa0fe130","value":1,"creation_date":1731964684,"payment_preimage":"0000000000000000000000000000000000000000000000000000000000000000","value_sat":1,"value_msat":1000,"payment_request":"lnbc10n1pnnhtctpp5frtldan6apvdn6ywu2y7nps2lqsn6rfuef785tqs563hn7s0uycqdpg2d8r5gr6v9czqvfqwdshgueqw3hjqgehxuenzdf3cqzzsxqzjcsp5wyalknd26nchkdq0ksl0em56uk5hhw6t0nle34t0nmdpxjrp4j2s9qxpqysgqqf8jlugmgkumygw4vu30xmanglxzxawtyzfs7w60muppu7ewaxt9lpvxz4h6cg7esly4u38rajtlls4nns46gxe73eq40ftvntfwl8sqw4mdnw","status":3,"creation_time_ns":1731964684062362536,"payment_index":37355,"failure_reason":2},"time":"2024-11-18T21:18:04Z"}  
2024-11-18T14:18:04-07:00 {"level":"info","msg":"Marked transaction as failed","payment_hash":"48d7f6f67ae858d9e88ee289e9860af8213d0d3cca7c7a2c10a6a379fa0fe130","time":"2024-11-18T21:18:04Z"}  
2024-11-18T14:18:04-07:00 {"bolt11":"lnbc10n1pnnhtctpp5frtldan6apvdn6ywu2y7nps2lqsn6rfuef785tqs563hn7s0uycqdpg2d8r5gr6v9czqvfqwdshgueqw3hjqgehxuenzdf3cqzzsxqzjcsp5wyalknd26nchkdq0ksl0em56uk5hhw6t0nle34t0nmdpxjrp4j2s9qxpqysgqqf8jlugmgkumygw4vu30xmanglxzxawtyzfs7w60muppu7ewaxt9lpvxz4h6cg7esly4u38rajtlls4nns46gxe73eq40ftvntfwl8sqw4mdnw","error":"no_route","level":"error","msg":"Failed to send payment","time":"2024-11-18T21:18:04Z"}

But those seem to be limited to the 1 sat HTLCs right now.

17 sats \ 2 replies \ @ek 18 Nov

The direct channel should fix it. Can you confirm?

100 sats \ 1 reply \ @Arceris OP 18 Nov

It appears to be working now, yes.

116 sats \ 0 replies \ @ek 18 Nov

🙌

We still need to consider this case though for anyone who does not have a direct channel. Also thanks from me for bringing this to our attention!

35 sats \ 2 replies \ @k00b 18 Nov

I suspect you have a peer with a strict htlc forwarding config.

; The smallest HTLC we are willing to accept on our channels, in millisatoshi.
; bitcoin.minhtlc=1

; The smallest HTLC we are willing to send out on our channels, in millisatoshi.
; bitcoin.minhtlcout=1000

Thanks for bringing our attention to this! It wasn't something we had considered.

1152 sats \ 1 reply \ @Arceris OP 18 Nov

Ok, I added a channel directly to Stacker News. I also edited my LND config to change the send-out HTLC on my channels to 200 millisats.

Now this reply should work with zero sats on SN and all from my node.

10 sats \ 0 replies \ @ek 18 Nov

you now have the premium non-custodial experience

223 sats \ 3 replies \ @DarthCoin 18 Nov

It's odd that the 2sat zap went through fine

Is not odd. As I warned so many times about this NOT necessary move to "p2p self-custody" madness, it will create more trouble than good.

SN is taking a fee from each zap or post or comment. That means at least 1 sat you must pay in fees even for 1 sat zap. On top of that you add the LN fees for routing that payment.

When is a 1 sat payment it became complicated because not all LN nodes are set to deal in msats for fees and MOST important is that each node will set his own policy of min HTLC and usually is 1 sat min.

All this p2p zaps of 1 sats is pure madness and will create a lot of trouble.

7 sats \ 2 replies \ @anon 18 Nov

Well, it may not be odd, but I basically cannot comment anymore, even on my own post, since I can't raise the comment fee & I cannot go and pay the "canceled" invoices with another method either (apparently they're expired, so cannot be paid).

So I'm having to comment as an anon and pay 100sats, lol.

Screenshot of the Stacker News notifications:

Screenshot of the Stacker News wallet history:

125 sats \ 1 reply \ @DarthCoin 18 Nov

How many times I have to explain this meme?

7 sats \ 0 replies \ @Arceris OP 18 Nov

Somehow just got 5 sats that didn't make it to my node, so using it to post this now.

But yeah, I am definitely feeling this.

0 sats \ 2 replies \ @OT 18 Nov

Yes. But I was having a different problem where 1 sat comments go through and the bigger zaps fail.

I turned it off for now. Will try again in a week or so, or switch to coinos.

0 sats \ 1 reply \ @Alby 19 Nov

It's hard to move 1 sat through the Lightning Network if there is no direct channel between sending & receiving node - most routing nodes charge.

Could you tell us more about bigger zap fails? Happy to troubleshoot!

0 sats \ 0 replies \ @OT 19 Nov

It was with ecash on the back end. It was working well but they changed something for security reasons. After it created a lot of failed payments.