pull down to refresh

I’ll adjust our default values for the ctlv delta which should make this less likely. We have it set pretty low, which still should give us ~6 hops worth of block time or so, but that appears to be not enough for many stackers
I don’t know what that means technically but now I’m getting sats instead of cowboy credits. Woo!
Shoutout to @koob for the quick turnaround. Everything is green so we’re good to go! 🤠⚡️
50 sats \ 5 replies \ @k00b 6 Jan
I don’t know what that means technically
Part of how lightning works is that nodes negotiate how long, in the worst case with time measured in blocks, they're willing to lock up liquidity to help you route a payment. We set this much lower than is usual so that in the worst case our peers would have their liquidity freed fast.
We adjusted this so that it is still lower than is usual but not by as much. The effect is that nodes that are in the remote edges of the lightning network should be reachable if they weren't before.
reply
Hey @k00b, I’m still getting cowboy credits. Anything else I can do on my end?
Here are the errors (first time seeing the “Estimated fees are too high” one).
reply
21 sats \ 3 replies \ @k00b 13 Jan
Those errors are from Jan 5. Do you have more recent errors? If not, you might be good to go now.
reply
Just got one from your zap.
reply
21 sats \ 1 reply \ @k00b 13 Jan
Currently, we will only pay 3% of the zap in network fees to reach your wallet. So if the zap is small, you'll get CCs. If the zap is big enough, you'll likely get sats unless your node is on only really expensive routes from our node.
In the future we'll allow you to pay this fee yourself if you want, but for now we have to cap the fee as we're paying it ourselves.
reply
That makes sense. Thanks for explaining!
(That 100 sats went through as you probably expected) 🤠
reply