Roy

Building Breez

Public Key

npub1ey6qdmvzcgcsr883m9nspzz0mm037l26xtardzcskfsvc6gc7jssm9szvp

NIP-05 Address

Profile Code

nprofile1qqsvjdqxakpvyvgpnncajecq3p8aahcl04dr973k3vgtycxvdyv0fggpz4mhxue69uhk2er9dchxummnw3ezumrpdejqzxrhwden5te0dehhxarj9e4k7mrvd9jx2u3w0puh5qgcwaehxw309ac8yetdd96k6tnswf5k6ctv9ehx2aqprdmhxue69uhkummnw3ez6ur4vgh8xetdd9ek7mpwv3jhvqghwaehxw309ahx7um5wghxvmt59emkj73wvf5h5qgawaehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2aq8znd7v

Publishing to

eden.nostr.land

nostr.kollider.xyz

premium.primal.net

nostr-pub.semisol.dev

nostr.fmt.wiz.biz

nostr-pub.wellorder.net

Author Public Key

npub1ey6qdmvzcgcsr883m9nspzz0mm037l26xtardzcskfsvc6gc7jssm9szvp

Show more details

Last Notes

2026-01-23 09:13:08 UTC

- reply

🙏❤️

2026-01-15 18:57:51 UTC

- reply

What this has to do with our challenge?

2026-01-15 18:56:33 UTC

- reply

Yessir

2026-01-14 23:08:56 UTC

- reply

There are always trade-offs... There are a lot of different designs you can do with PRFs. We decided to prioritizie simplicity in our protocol, inline with *our* use cases. We don't need to support imported wallets or deal with UTXOs in our SDK. We've also vetted the approach with design partners.

2026-01-12 00:17:48 UTC

- reply

That's not how it works. The primary nostr salt is fixed. Then it can store additional salts.

2026-01-09 20:53:07 UTC

- reply

It's crazy right now with the SDK, once things settle down...

2026-01-09 18:31:16 UTC

- reply

We're adding this to Misty Breez very soon

2026-01-09 18:30:36 UTC

- reply

Try Misty Breez

2026-01-02 14:29:47 UTC

- reply

We're also using private mode by default: https://sdk-doc-spark.breez.technology/guide/config.html#private-mode-enabled-by-default

2025-11-16 09:59:56 UTC

- reply

Notice zaps require public mode till we'll have client side receipts: https://github.com/breez/spark-sdk/pull/389

2025-11-10 19:15:25 UTC

- reply

🙏❤️

2025-11-06 18:24:27 UTC

- reply

Btw, by your definition, all the companies you listed above have "proprietary API", some of them don't even open source their code, but claim to be open source... So allow to lolz

2025-11-06 18:22:18 UTC

- reply

I second that! Do your research. Do your due diligence.

2025-11-06 18:21:18 UTC

- reply

That's your blind spot, not mine. I think they are committed to an open network. They already executed on their commitment. They open sourced the SE/SO. They communicated a public roadmap wrt to privacy. I think you're completely misjudging because? You're not doing that with Arkade, you're not doing that with Phoenix, for some reason you're targeting David Marcus. I judge them based on their actions.

2025-11-06 18:03:11 UTC

- reply

Not anyone can run an LSP. You need a lot of liquidity to run an LSP. I don't know what you mean by "proprietary API", the Spark SSP interface is public. The Spark SO is open source. You can run a Spark, an Ark or a Liquid federation. Yes, it's not easy to do, but the public interface isn't the showstopper here. It's the server management. Let's be honest, since we're operating an LSP, and interfaced with other large LSPs - running a LSP is super challenging as well. Perhaps the barrier of entry is lower now, because WE pushed for a spec and WE open sourced our LSP code - but it's still super challenging. They same dynamics apply to Spark, Ark etc.

2025-11-06 17:57:26 UTC

- reply

I just think you're on the wrong track. I know we're a good actor and we help Spark be more private. We already do so. We're also pushing other sub-networks and the native Lightning tech itself.

2025-11-06 17:53:46 UTC

- reply

They can send it to you as well and to any Lightning node as a matter of fact. There's a reason Phoenix and WoS pulled out of the US. Now they are back - but nothing has changed from a tech standpoint.

2025-11-06 17:52:11 UTC

- reply

But that's exactly what it is. An LSP can track balances, IPs, transaction details as well. We should be honest about it.

2025-11-06 16:10:21 UTC

- reply

Not extreme at all. LSPs are inherently centralizing. The more liquidity you have, the more users you will attract.

2025-11-06 16:09:07 UTC

- reply

1. It's not theoretical. Lightning is already being surveilled, don't be naive.
2. It's our job to allow users to switch LSPs and sub-networks at their will.
I don't subscribe to the FUD around Spark. I think it's a cool tech that will only get better and more private. And if not, the market will reject it and use something better.

2025-11-06 16:03:20 UTC

- reply

So we agree. Effectively the biggest LSP, Phoenix, does know the destination and dies trampoline payments and implementations like LDK use an external graph sync mechanism because regular graph sync doesn't work with mobile clients. There are always trade-offs.

2025-11-06 11:00:43 UTC

- reply

I recommended you a few times in the past not to overhype the privacy state of Lightning. I suggest you align your documentation with this: https://lightningprivacy.com/en/introduction

2025-11-06 10:55:09 UTC

- reply

And if you are referring to in-Spark transactions, the same issue exists in an in-LSP transaction... I.e. the sender and receiver are connected to the same LSP.

2025-11-06 10:33:15 UTC

- reply

Get your facts straight. You can blame me all you want, but this is a complete misunderstanding of how Lightning works.
If the LSP knows the destination node, it knows the destination. period. And you don't understand how Phoenix works - they don't do source routing. They use they LSP as a trampoline nodes. They construct the path and they know the destination.
Moreover, even in cases of source routing - if the user is connected to a single LSP - the LSP effectively controls the path because the graph information is fed by the LSP...

2025-10-11 22:37:41 UTC

- reply

The default behavior in the Breez SDK is not to expose the spark address in the bolt11, so you can't do what Evan showed above. However, since spark reuses addresses (currently), you can still apply stuff like timing attacks to discover the underlying address. This should be addressed soon by the spark team (they are switching to a dynamic address model).

2025-10-08 11:08:50 UTC

- reply

We also have a Spark-based implementation

2025-10-02 18:45:40 UTC

- reply

🙏❤️

2025-10-02 10:58:13 UTC

- reply

Ah?

2025-09-16 22:32:29 UTC

- reply

You should come to the Bitcoin Embassy in Tel Aviv

2025-09-16 22:31:11 UTC

- reply

There's a relatively small but dedicated Bitcoin community, practically no one accept Bitcoin unfortunately...

2025-09-14 14:31:43 UTC

- reply

Very soon: https://github.com/breez/breez-sdk-liquid/pull/920

2025-09-12 06:23:33 UTC

- reply

Yes

2025-08-28 14:12:23 UTC

- reply

Ofc you can

2025-08-27 07:02:48 UTC

- reply

Again with the FUDing. Self-custodial is a regulatory term. If you hold your keys to the asset, the wallet is self-custodial, no matter ls what the asset is BTC, USDT or L-BTC. Now, the question is how protected the asset itself. With BTC, if you have a way to unilaterally exit to mainnet (which Liquid doesn't, but Spark for example does), you have control over your funds.

2025-08-26 18:16:30 UTC

- reply

Misty Breez is self-custodial. You're referring to L-BTC, which is held in a Liquid federation. There are 15 functionaries (all from different entities) in Liquid, so no need to FUD in order to get ppl using your service.

2025-08-10 05:34:18 UTC

- reply

💯⚡

2025-08-08 08:32:41 UTC

- reply

Can you please block your bot for breez.fun addresses until we'll lower the minimum? These addresses work, but you need to zap at least 100 sats.

2025-07-28 19:58:11 UTC

- reply

So check again

2025-07-24 08:50:31 UTC

- reply

Try Misty Breez

2025-07-11 17:38:14 UTC

- reply

Not what I meant. Boltz|CNL is used for in our Nodeless SDK, you're classifying all as Aqua. I don't really care about attribution, but in our native SDK, multiple nodes are being used, but that's besides the point.

2025-07-10 07:56:30 UTC

- reply

Misty Breez and all Breez SDK wallets as well...

2025-07-03 18:01:12 UTC

- reply

Yes, we plan to

2025-06-19 21:03:24 UTC

- reply

#nevent1q…7wyj

2025-06-13 09:19:10 UTC

- reply

Better that ocean would implement pay note. The alternative would be to create another bolt12 offer (which you can via the Breez SDK), but tbh it's not something we want to do in Misty (we want to keep bolt12 static in Misty till a much wider adoption).

2025-06-13 09:16:04 UTC

- reply

Soon: https://github.com/breez/misty-breez/pull/560

2025-06-04 19:12:10 UTC

- reply

👀

2025-05-27 06:49:53 UTC

- reply

1. The QR code works with Phoenix (just tested)
2. Yep, the cost of doing swaps, but on the other hand you don't pay for liquidity. Also, for larger amounts Phoenix is 0.4% and Misty is 0.1% (+ the fixed liquid tx fee).

2025-05-24 20:36:53 UTC

- reply

Nope

2025-05-24 20:36:40 UTC

- reply

Nice!

2025-05-24 09:08:41 UTC

- reply

It does

2025-05-24 09:07:50 UTC

- reply

You can do it via mobile notifications "magic" on both iOS and Android

2025-05-23 19:10:14 UTC

- reply

It takes time to get wallet adoption. We just added full bolt12 in our nodeless SDK this week, we still don't have it on Greenlight. But I agree with Matt, it's here, and we need to push for wider adoption.

2025-05-23 19:07:35 UTC

- reply

We worked with Phoenix and Boltz to improve it, let us know if something isn't working as expected after the latest updates (both Phoenix and Misty).

2025-05-23 06:49:29 UTC

- reply

👀

2025-05-20 18:47:51 UTC

- reply

We have a couple, but this is the largest so far - many more to come 🚀🚀🚀

2025-05-17 20:26:21 UTC

- reply

Fixed