Jesse
Jesse de Wit

Working on a simple bitcoin powered point-of-sale app. It's powered by Spark, with Breez SDK. Onboarding is so easy. Just type in an amount and receive. No setup cost. No barriers.
Bitcoin UX is about to take a leap forward.
https://blossom.primal.net/2a1351d514c839d3898f871d0cd0f4bcbb43a982dc3024e323ef4e28446902fe.mov

2025-09-18 21:37:00 UTC

- reply

Right I should fix that.

2025-09-18 21:35:20 UTC

- reply

That's an interesting thought. It should be possible, because a spark address is simply a public key. It won't be possible out of the box with breez sdk in the current state, because of the way the keys are derived from a mnemonic. But it's possible theoretically for sure!
With the Breez SDK we just shipped lightning addresses out-of-the-box, without developers needing to host anything. It doesn't have nostr support yet though!

2025-09-10 16:08:19 UTC

- reply

git rebase --onto

2025-09-10 07:27:30 UTC

"Prevent utxo set bloat"
But don't libbitcoin, utreexo and SwiftSync prove that you don't need to store 'the utxo set' at all?
If you don't need to store it, or keep it in memory, it doesn't matter if it bloats. Seems like a resilient option to me.

2025-09-07 06:54:53 UTC

- reply

Primal

2025-09-05 06:38:13 UTC

- reply

Mentioned event not found! How do I fix this?
https://blossom.primal.net/c4a0397b0ef94846b2002bfefaec0814a11725d34d0ff3d62ffc453c39b94ec0.jpg

2025-06-11 16:08:55 UTC

- reply

This was a great speech

2025-05-20 20:19:04 UTC

- reply

So it went from 80M bitcoin users worldwide to 50M American-only users in 2 years? That seems like a huge increase, especially because the United States is 26th in terms of search interest in this period.

2025-05-09 19:06:36 UTC

- reply

I see, so lnproxy's node id (or the fake one they use) was missing in the screenshots above. It's in the signature there probably. That got me confused a bit.

2025-05-04 20:51:08 UTC

- reply

What kind of invoice was this that the destination node id is not in the invoice?

2025-04-28 20:43:00 UTC

- reply

This sentence is not finished:
36 bytes for the outpoint that identifies which UTXO is being spent (32 bytes for the txid, 4 bytes for the vout), 4 bytes for the nSequence, and

2025-04-28 09:50:58 UTC

- reply

Bars are almost always better btw. But if you really want to use a pie shape, use a donut.

2025-04-28 09:47:14 UTC

- reply

It's the area of the triangle that is hard to grasp for us. With the donut it's more like a bar. Focus shifts to the circumference of the circle instead of the area. Relative parts or the circumference of the circle do work good with our brains.

2025-04-28 08:21:03 UTC

Reminder that the human eye can't see the relative sizes of pieces on a pie chart.
Don't use pie charts.
Use a donut chart or bars instead.

2025-03-27 16:11:24 UTC

- reply

I'd say decisions are made by who we are. So our decisions are a result of who we are. Not to confuse the 'being' by the 'doing'. The decisions we make obviously nicely reflect who we are.
Otherwise agreed!

2025-03-08 09:34:39 UTC

- reply

Sounds great, if they'd open source it.

2025-02-20 21:00:25 UTC

- reply

exactly!

2025-02-15 00:25:44 UTC

- reply

great stuff

2025-01-26 16:25:24 UTC

- reply

Pretty crazy..

2025-01-24 23:59:56 UTC

- reply

I had to look up what 'red pill content' means.
"Online, red pill is especially used among anti-feminist and white supremacist groups to refer to “waking up” to the truth that women and liberal politics are oppressing men and white people."
I didn't know that was a thing. Let alone that you'd actively be followed around rooms for it.

2025-01-24 23:47:17 UTC

- reply

yeah it's more like a coinflip than pokemon

2025-01-24 23:01:34 UTC

- reply

That was clickbait!
Impressive nonetheless.

2025-01-18 15:18:49 UTC

- reply

The swap address you could see in the client where you senttohe onchain tx with.

2025-01-18 15:13:33 UTC

- reply

I can't see your DM. Invoice or payment hash would also help me. You could also reach out on telegram or twitter if this DM doesn't work.

2025-01-18 09:24:17 UTC

- reply

Can you DM me the swap address please? I would like to check why it took so long.

2025-01-17 11:04:43 UTC

- reply

The Swarm - Frank Schätzing

2025-01-17 11:00:55 UTC

- reply

Did you update to the latest version?

2025-01-17 10:56:09 UTC

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-16 16:08:33 UTC

- reply

You're clearly not autistic enough Calle. 6 of these fingers are pointing in the wrong direction. (pointing sideways but should be pointing up)
Fixed it for you:
👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿
👉🏿👇🏾👇🏾👇🏾👇🏾👇🏾👇🏾👇🏾👇🏾👇🏾👈🏿
👉🏿👉🏾👇🏽👇🏽👇🏽👇🏽👇🏽👇🏽👇🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👇🏼👇🏼👇🏼👇🏼👇🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👉🏼👇🏻👇🏻👇🏻👈🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👉🏼👉🏻🥜👈🏻👈🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👉🏼👆🏻👆🏻👆🏻👈🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👆🏼👆🏼👆🏼👆🏼👆🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👆🏽👆🏽👆🏽👆🏽👆🏽👆🏽👆🏽👈🏾👈🏿
👉🏿👆🏾👆🏾👆🏾👆🏾👆🏾👆🏾👆🏾👆🏾👆🏾👈🏿
👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿
Or even better, use this vortex:
👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👈🏿
👉🏿👇🏾👇🏾👇🏾👇🏾👇🏾👇🏾👇🏾👇🏾👈🏾👈🏿
👉🏿👉🏾👇🏽👇🏽👇🏽👇🏽👇🏽👇🏽👈🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👇🏼👇🏼👇🏼👇🏼👈🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👉🏼👇🏻👇🏻👈🏻👈🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👉🏼👉🏻🥜👈🏻👈🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👉🏼👉🏻👆🏻👆🏻👈🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👉🏼👆🏼👆🏼👆🏼👆🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👆🏽👆🏽👆🏽👆🏽👆🏽👆🏽👈🏾👈🏿
👉🏿👉🏾👆🏾👆🏾👆🏾👆🏾👆🏾👆🏾👆🏾👆🏾👈🏿
👉🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿

2025-01-16 13:45:38 UTC

- reply

It's still out there

2025-01-14 11:12:39 UTC

- reply

What do you mean with 'cycle through multiple routes'? Sounds like you should do retries after a route fails. Do queryroutes again and sendtoroutev2 with the new route. It should give a new route.
LND always returns a single route, so what does "get a list of all routes that LND suggests and try them one by one until one of them succeeds" mean?

2024-12-20 18:46:07 UTC

- reply

Actually the invoice contains the HASH to the payment preimage. Only if you've paud the invoice do you obtain the preimage over the lightning network. It is needed to settle the paynent and it is your proof of payment.

2024-12-20 18:43:48 UTC

- reply

sorry for the late reply. Alice should be able to see the preimage in the sender UI if the invoice was paid. That is your proof of payment. If you don't have it, the invoice wasn't paid.

2024-12-07 03:06:49 UTC

- reply

Does Alice have the payment preimage?

2024-11-06 11:02:19 UTC

- reply

This is an openvibe issue.

2024-11-02 08:50:12 UTC

- reply

Note this issue probably affects nostr apps as well! If you're a nostr app builder relying on a rust sdk, create a hibernation check!

2024-10-29 13:45:12 UTC

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-28 10:03:19 UTC

- reply

Great explanation, thanks!

2024-10-08 09:41:59 UTC

- reply

Yeah that's the way. But how to get each block in forward order?

2024-10-07 21:51:11 UTC

- reply

I have an application that needs to get certain data from the chain, so it syncs blocks off the bitcoind rpc. Parses the blocks, checks if there's relevant data and moves to the next block. I want that application to start at genesis (or some birthday block) and sync the chain from there.
Right now I'm getting the headers first, backwards, from tip to birthday. Then sync the blocks forwards, from birthday to tip. I was wondering whether I could skip the headers part and sync directly from birthday to the tip, forwards.

2024-10-06 12:37:32 UTC

@npub185h…wrdp is there a rust implementation of a BIP-353 lookup out there?

2024-10-06 12:10:34 UTC

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-09-22 07:12:14 UTC

- reply

Yep

2024-05-10 17:38:15 UTC

- reply

Hier nog een. Ben benieuwd naar de theorie?

2024-03-22 16:35:59 UTC

- reply

Yeah that's worth a PR I think.

2024-03-21 17:42:37 UTC

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-20 08:26:33 UTC

- reply

Yes! Just not for future calendar events or anything like that.

2024-03-08 18:35:12 UTC

- reply

Excellent work!

2023-07-15 07:03:45 UTC

- reply

Yeah. It's permanent. There's several names for this. Among others:
LND - lightning nervosity disorder
CLN - cerebral lightning nervosity

2023-07-02 17:44:58 UTC

Hello World

2023-07-02 11:42:18 UTC

- reply

Ability to remove relays from the settings menu would be nice.

2023-07-02 11:35:44 UTC

- reply

Also when you add a relay, it seems you have to restart the so in order to be able to find people on that relay.

2023-07-02 11:30:49 UTC

- reply

Yeah, I just installed.
It looks pretty slick, onboarding is easy.
I would like to be able to find people if I'm not connected to their relay. Either through npub, or through the email address notation.