Jesse de Wit

Zero-JS Hypermedia Browser

avatar
Jesse de Wit
npub18hwp...v8du
Lightning developer | Breez

Notes (6)

Missing an out-of-the-box way to get a route for an invoice in core lightning. I see getroute and getroutes, but they require custom logic to handle route hints.
2025-01-17 10:56:09 from 1 relay(s) View Thread →
Over time got some reports of strange errors in the breez sdk. Sometimes there were DNS errors, sometimes payments not working, sometimes requests not arriving at the greenlight servers at all. Turns out it's app hibernation causing these issues. The rust code would still be running, but it wouldn't get any resources to execute. That causes grpc channels to fail functioning after coming back from hibernation. Adding a 'sleeper loop' to the Breez SDK. It sleeps in a loop for one second. If the sleep takes a long time, it means the app hibernated. Then reconnect any grpc clients. It's an interesting dynamic to guard against. Thr SDK should becone more robust for hibernation this way soon.
2024-10-29 13:45:12 from 1 relay(s) View Thread →
nostr:npub185h9z5yxn8uc7retm0n6gkm88358lejzparxms5kmy9epr236k2qcswrdp is there a rust implementation of a BIP-353 lookup out there?
2024-10-06 12:37:32 from 1 relay(s) View Thread →
Is there a way to sync the chain forwards from the bitcoind rpc? The only way I found now is to - get the tip - get previous headers one by one - then start syncing blocks from the start with the headers you've found What I'd like to do: - get the genesis block - get the 'next' block - etc. Is there way with the bitcoind rpc?
2024-10-06 12:10:34 from 1 relay(s) View Thread →
Tip about CLN: When CLN forwards a payment and it has multiple channels with the same peer, it selects the channel with the highest available balance out of channels with the same fee policy as the one the sender specified. Say you have 3 channels with the same peer. - A has fee 10ppm and is depleted - B has fee 10ppm and has 100sat sendable balance - C has fee 5ppm and has 1 BTC sendable balance Sender computes a route that contains channel A, sends a payment. Your node will pick the channel with the highest balance out of channel A and B, because they have the same fee rate. In this case it picks B because it has the highest balance. If the payment was more than 100sat, the forward will fail.
2024-03-21 17:42:37 from 1 relay(s) View Thread →