pull down to refresh

@ek
4,466,914 sats stacked
stacking since: #57444longest cowboy streak: 233 verified stacker.news contributornpub16x07c...2j2s96s89dekzyis
bio
10,236 items
2 territories
by
for
20 sats \ 1 reply \ @ek 1h \ parent \ on: No route for for territory payment lightning
Mhh, not sure why it would count the channel reserve to outbound liquidity but 1% of a channel is usually not available to spend, so this might still be the issue you're running into:
What is a channel reserve?
A channel reserve is an amount that is set aside by each channel participant which ensures neither have ‘nothing at stake’ if a cheating attempt occurs. This reserve can not be spent, and is held aside for the entirety of the channels lifetime.
Channel reserves make cheating attempts less economical. When one channel party attempts to cheat the other and they are caught, a penalty transaction can be used to steal all the cheating parties bitcoin as punishment. Channel reserves makes it so cheating attempts always have something at stake making this less likely to occur.
1 sat \ 0 replies \ @ek 2h \ parent \ on: No route for for territory payment lightning
Sorry for these lightning details, but how much you can spend over a channel depends on outbound liquidity (how much is on your side of the channel). Maybe that wasn't enough?
edit: Oh, I see your other comment. Will respond there.
33 sats \ 1 reply \ @ek 2h \ parent \ on: Stacker Saloon
We broke lightning addresses during the release but I think you had an issue before we released and it was simply a request timeout. Maybe we should increase the timeout to 30s but we cannot control how fast whatever is behind the lightning address responds. It might still not respond within 30s if it hasn't already in 10s.
0 sats \ 1 reply \ @ek 15h \ parent \ on: Stacker Saloon
Which wallet? Can you show us your wallet logs?
edit: we found an issue with withdrawing to lightning addresses, that should hopefully fix what you're seeing
13 sats \ 0 replies \ @ek 17h \ on: Nostr Relays: What Gives? nostr
I guess "freedom of speech but not freedom of reach" applies to nostr, too.
67 sats \ 1 reply \ @ek 18h \ parent \ on: Microsoft is building wooden data centers in its latest push to cut emissions Construction_and_Engineering
you mean even if it's fire-resistant?
Microsoft is testing fire-resistant cross-laminated timber (CLT)
22 sats \ 2 replies \ @ek 19h \ parent \ on: SN release: proxied lightning address, pull to refresh, wallet status, bug fixes meta
This only means that when you're editing and your timer runs out, you can still cancel to get out of edit mode. Before you would be stuck in edit mode since even the option to cancel would disappear.
20 sats \ 1 reply \ @ek 19h \ on: Nuclear targets in America charts_and_numbers
What about Alaska and Hawaii?
35 sats \ 1 reply \ @ek 19h \ parent \ on: Nuclear targets in America charts_and_numbers
and be the first city to get hit
1 sat \ 7 replies \ @ek 19h \ parent \ on: Early Retirement by Bitcoin bitcoin
but maybe his balls are on the bitcoin standard if he only dates bitcoiners
50 sats \ 0 replies \ @ek 19h \ parent \ on: Stacker Saloon
oh, but we should use WARN and not ERROR for Estimated fees are too high
48 sats \ 0 replies \ @ek 20h \ parent \ on: Stacker Saloon
Oh, you have a direct channel with SN? Then that's weird, we will also look into that. No network fees from SN to you should apply in that case.
edit: do you have enough inbound liquidity on that channel?
242 sats \ 3 replies \ @ek 20h \ parent \ on: Stacker Saloon
That is intended and should only show up in your logs but not break zaps.
It means reaching your node is too expensive for that zap so we fall back to credits.
Btw, we found the issue for no wallet to receive available. We'll deploy the fix soon.
37 sats \ 5 replies \ @ek 20h \ parent \ on: Stacker Saloon
you should be able to zap anyone, this error is not intended
21 sats \ 0 replies \ @ek 20h \ parent \ on: Stacker Saloon
Ohh, that’s not good. We‘re looking into it, thanks for the report!
zapped you with custodial sats