Gigi

I wrote it to never, ever, under any circumstances, have Swan do address reuse. (Because address reuse is really really really really bad 😭)
Time is a flat circle. I go cry now.

2026-05-18 16:21:28 CEST

- reply

Locked into something, you say? #nevent1q…52r5

2026-05-18 16:19:29 CEST

- reply

this is all so retarded I'm legit losing my mind

2026-05-18 16:19:16 CEST

Lightning doesn't "lock" you to a provider.
Neither does Cashu. Unilateral exit is a thing.
On-chain zaps, however, will "lock" your nsec to a bitcoin address. Forever.

2026-05-18 16:16:49 CEST

- reply

Godspeed 🫡

2026-05-18 16:14:26 CEST

- reply

😩

2026-05-18 16:12:23 CEST

- reply

😭 😭 😭 https://haven.dergigi.com/27fd01621ea238a7fdb57cb98b7ccdb74ac4b3771e1253fa94f4952f55b6257d.png

2026-05-18 12:27:52 CEST

- reply

only the best

2026-05-18 12:27:39 CEST

Onchain data is built to stay around forever. All other data is subject to bitrot and eventual loss. Few understand this.

2026-05-18 12:24:19 CEST

- reply

There's other solutions that are way better. Npub cash and NIP-60, for example. Silent Payments is an option, that's why insisting to blast ahead with a naive and destructive approach is so flabbergasting.

2026-05-18 12:19:52 CEST

- reply

It's quite something

2026-05-18 12:18:55 CEST

- reply

https://haven.dergigi.com/eecc38ad77ab98605c8f4a24b1dbe2d2d99539f9d58e2609b62f3c122cdae8b5.gif

2026-05-18 12:07:45 CEST

- reply

🎯 #nevent1q…6h4j

2026-05-18 12:07:06 CEST

This.
#nevent1q…75sq

2026-05-18 12:02:46 CEST

- reply

https://haven.dergigi.com/b2c372b667b453be04d2003091af4798608f1f3b08865b1334621977be1d8e0d.gif

2026-05-18 11:58:57 CEST

- reply

we've even got retards and shitcoiners chiming in from the sidelines, it's almost perfect

2026-05-18 11:58:23 CEST

i hate everything about this "debate" but at least nostr feels a little bit like old twitter right now lol

2026-05-18 11:56:37 CEST

- reply

Wrong. It needs to be shouted from the rooftops louder. It's way more problematic than you think it is. https://en.bitcoin.it/wiki/Address_reuse

2026-05-18 11:53:31 CEST

- reply

It's a proof-of-concept, not a proper implementation. But it's pushing things in the right direction, as opposed to on-chain zaps.

2026-05-18 11:51:01 CEST

- reply

👀

2026-05-18 11:50:52 CEST

- reply

👀

2026-05-18 11:42:33 CEST

- reply

The fact that "normie user dgaf" is exactly the reason why non-normie users should give a fuck and why devs shouldn't push harmful implementations, practices, or defaults.

2026-05-18 11:21:55 CEST

- reply

Yes. I encourage you to read through the gists posted here: #nevent1q…awfk

2026-05-18 11:06:45 CEST

- reply

2026-05-18 10:39:15 CEST

- reply

2026-05-18 10:38:04 CEST

- reply

GM, and yes

2026-05-18 09:33:34 CEST

- reply

Vitor, you're a smart man. How you continue to not get the difference is beyond me.
Onchain is transparent. You can not deny that you have received funds. You can not deny that you have moved them after you received them. If you still use your nsec after receival you can't even deny that you have the capability to move them.
Am I taking crazy pills?

2026-05-18 08:34:17 CEST

GM https://haven.dergigi.com/f60d50222510785f9a7d2207879e9b790856d438f5774c40852a515fb3203cc6.jpg

2026-05-17 22:18:38 CEST

"the fact that you're familiar with something doesn't mean that you understand it deeply"

2026-05-17 21:09:29 CEST

- reply

Solid writeup: #nevent1q…lmsr

2026-05-17 21:07:02 CEST

- reply

Why should he, it's sloppypasta by definition. https://stopsloppypasta.ai/en/

2026-05-17 21:04:51 CEST

- reply

Your nsec can roleplay as the privatekey of a bitcoin wallet. Some devs want to use this so that you can send and receive money ("on-chain zaps") without having to jump through any wallet setup hoops. There's issues with this for privacy, security, and a multitude of other reasons. The idea is okay in principle and similar to nutzaps, but the forever footprint of this "solution" and the 2nd and 3rd order implications of forcing users to deal with onchain shenanigans is problematic, to put it mildly.

2026-05-17 20:56:56 CEST

petition to call on-chain zaps "shrimps" https://haven.dergigi.com/1b9ccec14d7cd0ea1bca5f504db3b4b8bc7a5adb411e83f778d12bc97e5ae22d.jpg

2026-05-17 20:53:01 CEST

- reply

In addition, address reuse is bad for everyone else on the network (because it decreases the anonymity set). #nevent1q…5a7y

2026-05-17 18:51:35 CEST

- reply

Users don't read.

2026-05-17 18:31:56 CEST

- reply

Zaps don't promote on-chain address reuse. Are you even trying to understand what I'm saying?

2026-05-17 18:31:14 CEST

- reply

Anyway, I know that you're gonna ship it anyway but this is too important for me to just shut up about. I hope that a more sane approach will win in the end. Silent Payments, for example. I'll go touch grass now.

2026-05-17 18:29:59 CEST

- reply

It matters. It matters a lot. Providing and normalizing the use of long-term footguns is not the way. Building stuff that actively harms the privacy of all on-chain users (that's what address reuse does, remember?) is not the way.

2026-05-17 18:26:53 CEST

- reply

Sure, it's an obvious thing to build.

2026-05-17 18:26:36 CEST

- reply

Yes, that's one of my concerns. It's almost impossible to educate users on the dangers of on-chain privacy implications. #nevent1q…ssrd

2026-05-17 18:25:41 CEST

- reply

You can't opt out.

2026-05-17 18:24:40 CEST

- reply

Plenty of people have a lightning address that isn't theirs as their zap target.

2026-05-17 18:19:13 CEST

- reply

Let me try to make my point once more:
1) Address reuse is actively harmful for the whole Bitcoin network.
2) On-chain privacy is very, very hard.
3) Lightning privacy is NOT hard
What (3) means is that I can spend the zaps that I have received WITHOUT getting into trouble further. I can spend them at a merchant or whatever, and nobody will know. On-chain makes that way, way, way harder. On-chain is traceable.
Further, nobody knows the current balance of my wallet. I might have spent everything. Or maybe I haven’t touched it. Switching to on-chain makes every user naked, and thus plausible deniability flies out the window.

2026-05-17 18:12:11 CEST

mood https://haven.dergigi.com/6337b65f15218a87756cc42c7eacf07e5bc79d342d5e7cedcce495f463e3f9d6.gif

2026-05-17 18:10:40 CEST

- reply

> Saying that lightning zaps is a "sane" privacy implementation
That's not what I said.
When it comes to zaps, Lightning is the sane choice, because of its properties. Using on-chain for those public payments is NOT the sane option, since on-chain leaves a trail that is forever auditable. “Forward secrecy” (if you want to call it that) does not exist. Plausible deniability does not exist. The option to say “I never touched that money” doesn’t exist. The option to say “I lost access to this wallet” does not exist either, unless you nuke your nsec.

2026-05-17 18:04:55 CEST

- reply

All the zaps that I have received so far, what did I spend them on? Can you tell? Did I even move those sats at all? Where did the sats go after I’ve received them?
Less importantly: Is it possible that some of the zap receipts were faked, and thus there’s “zap events” out there that didn’t even move sats at all?
Even less importantly: I had many lightning addresses attached to my profile up to now. Is it possible that one of those lightning addresses was controlled by someone else, and not me?

2026-05-17 17:48:29 CEST

- reply

Nobody is gonna kidnap my kids or $5 wrench attack me because there is “child porn attached ot my pub key on chain” (whatever the fuck that means, please explain).
I guess my main point is this one: on-chain privacy is hard. Lightning privacy isn’t hard.
It is my humble opinion that we should have sane defaults and encourage privacy best practices. Lightning is a sane default for zaps. Lightning has privacy best practices built in. On-chain privacy is very (very) hard, and any mistake you make might haunt you forever.
And once more for good measure: address reuse is really, really bad. For everyone.

2026-05-17 17:38:43 CEST

- reply

It absolutely matters whether it's a new address every time or the same one. On-chain data is forever, most other data is not.
Lightning zaps have plausible deniability. On-chain zaps don’t have that property. On top of that, Lightning has certain privacy guarantees after receival that on-chain does not and will never have. If you move the money on-chain after receival, everyone will be able to see it and prove it without a doubt. Once more, plausible deniability goes out the window.
“Don’t transact with them.” Ok, here’s a thought experiment: If I want to make someone a target and I have money, I can just on-chain zap them 100 BTC. The fact that they don’t move the money won’t help them, they are still a target.

2026-05-17 17:14:39 CEST

- reply

I won't challenge you on the first part, but saying that address reuse onchain zaps are "a million times better than Lightning" is a wild thing to say. It's also wrong.

2026-05-17 17:10:13 CEST

- reply

Ok. Once more for the people in the back: Address reuse is really really really really (really) bad. Don't encourage it. It destroys the privacy of everyone.

2026-05-17 17:06:09 CEST

- reply

Time is a flat circle. https://github.com/jlopp/physical-bitcoin-attacks

2026-05-17 17:01:59 CEST

- reply

I guess I am?

2026-05-17 16:59:19 CEST

- reply

Plausible deniability is important. This removes it. You didn't address the address reuse issue. It's a massive issue. Keep in mind that I'm an advocate for both nutzaps and the marriage of silent payments and nostr.

2026-05-17 16:55:30 CEST

mood https://haven.dergigi.com/7c93e931904a0e75155ee12683a18530549c34bd233b578b8c2cf401506c601d.mp4

2026-05-17 16:53:03 CEST

- reply

Users should have the option to decouple money and identity. Address reuse is actively harmful for the entire network. Users can't opt out. Users have no way of denying that they received money. I could go on...

2026-05-17 16:50:12 CEST

- reply

Separate discussion entirely. Current proposal is to turn any npub into a single publicly known onchain address, which encourages address reuse and makes it impossible to decouple identity from money. You can't opt out of it either.

2026-05-17 16:45:21 CEST

Terrible idea. Harmful concept. Users will get rekt, attacked, or worse. Do better.
#nevent1q…clpr

2026-05-17 16:40:10 CEST

- reply

That won't help those who'll get rekt by this "feature"

2026-05-17 16:38:08 CEST

What users?
#nevent1q…e5nh

2026-05-17 16:37:15 CEST

- reply

Onchain is forever, and forever is a long time.

2026-05-17 16:34:27 CEST

- reply

nothing wrong with a little self-love from time to time

2026-05-17 16:02:01 CEST

- reply

Ok. Be well.

2026-05-17 16:00:28 CEST

- reply

... #nevent1q…sw7x

2026-05-17 15:59:51 CEST

- reply

To make an educated decision you need to be educated in the first place. Most users are uneducated when it comes to the nuances of on-chain privacy. It's a difficult topic, and the software we build shouldn't make it easier for users to damage themselves, but harder.

2026-05-17 15:56:31 CEST

- reply

not this one lol

2026-05-17 15:56:12 CEST

- reply

Address reuse is bad. The fact that open-source developers are currently behind bars is atrocious. Both can be true.

2026-05-17 15:44:03 CEST

Address reuse is a big problem as it is already. Let's not make it worse.
#nevent1q…5a7y

2026-05-17 15:41:40 CEST

- reply

there is a way to do this "properly" but just deriving an address from an nsec is not it. Some prior work:
https://gist.github.com/BoltTouring/dde944661df330ec5119af8ef94159e1
https://gist.github.com/BoltTouring/5376f9cf02b6949252cd17c2f41b453f

2026-05-17 15:35:32 CEST

"on-chain zaps" are a bad idea and have the potential to be actively harmful when implemented naively

2026-05-17 15:32:40 CEST

- reply

You can put a silent payment address into your profile info using the "sp" field. Jumble supports it, some other clients too. https://gist.github.com/BoltTouring/5376f9cf02b6949252cd17c2f41b453f

2026-05-17 15:29:57 CEST

- reply

> all women converging to Kim Kardashian
https://haven.dergigi.com/079f7547b91ca0c439e73e4071363720ebd1eab9fdfd38fbc53a882315e5c63a.gif

2026-05-17 15:28:42 CEST

- reply

Grug brain is best brain. https://sovereignengineering.io/images/nosolutions-cover.jpg

2026-05-17 15:27:01 CEST

"Your scientists were so preoccupied with whether they could, they didn’t stop to think if they should"
#nevent1q…x8rn

2026-05-17 15:25:56 CEST

- reply

Especially if the thing is on-chain zaps. Don't tell anyone. Don't even think. Don't entertain whether it's a good idea or not. Just ship it.

2026-05-17 15:19:20 CEST

"Address reuse harms the privacy of not only yourself, but also others"
https://en.bitcoin.it/wiki/Address_reuse

2026-05-17 15:06:20 CEST

- reply

We forgot about serious play. https://www.youtube.com/watch?v=CrxvB1_t03I

2026-05-17 15:01:43 CEST

- reply

It is. Also: https://haven.sovereignengineering.io/5c534684d544b519bbb09cc126ac0095f093949498091ca818a55baee26e0e44.png

2026-05-17 14:55:14 CEST

- reply

https://dergigi.com/2026/03/20/the-internet-left-me/

2026-05-16 22:52:13 CEST

- reply

😂👌 #nevent1q…5mzk

2026-05-16 22:51:21 CEST

say what you will but "mini shai-hulud" is a great name for a worm

2026-05-16 22:47:20 CEST

mood https://haven.dergigi.com/aed06cebb0530dcc2d766826af0b39f853df1c3390ee44da53c786e8bfc9e9e4.jpg

2026-05-16 22:31:50 CEST

- reply

Careful, Icarus.

2026-05-16 17:52:02 CEST

latest Amethyst update is insane lol

2026-05-16 17:03:14 CEST

- reply

What hardware do you have an eye on?

2026-05-16 16:08:50 CEST

- reply

https://haven.dergigi.com/6e39880a54d3822a2f865f151ea2b8da20381f986598c55ded6f85b27014d23f.gif

2026-05-16 16:08:21 CEST

- reply

😋

2026-05-16 14:00:59 CEST

- reply

2026-05-16 13:05:13 CEST

- reply

RIP Carl Sagan https://haven.dergigi.com/8d9be423cf28fc7dd376f13c3753982795bb0c3429e01659fd06b4f1c54f51a5.jpg

2026-05-16 12:56:19 CEST

@nprofile…406e that pfp is diabolical lol

2026-05-16 08:50:21 CEST

GM https://haven.dergigi.com/f9cd4819bfabf7ddc03fe9d22e82d2bc9808ce4c5c0f962cd96435d51e97e3b4.jpg

2026-05-16 08:47:23 CEST

- reply

Ostrich under the table, who cut his head off?

2026-05-16 08:44:50 CEST

- reply

I can read! 😜

2026-05-15 18:34:33 CEST

- reply

NewPipe is the hack. It's on Zapstore too. https://zapstore.dev/apps/org.schabi.newpipe