TheButterZone
🔫 Alwin 🦌🏴

On-chain zaps via Taproot are burned, please use bc1qn5kua7a4r7xasgnd6mt4k5huv45gcm3rs545u2
L1 only, no L2 or Taproot/dependents, for me! And there should only ever be one fee: <1 sat/byte. Back in the day, I sent/received bitcoin with ZERO TX fees.
PGP 750A6640C5E4961B

Public Key

npub19ctmsmtf9jtehddhctwmnacwqtnkh0p43tafttrgzdgy0wlppcpq50zf83

NIP-05 Address

thebutterzone@iris.to

Profile Code

nprofile1qqszu9acd45je9umkkmu9hde7u8q9emths6c4754435px5z8h0ssuqspz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsn30jln

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub19ctmsmtf9jtehddhctwmnacwqtnkh0p43tafttrgzdgy0wlppcpq50zf83

Show more details

Last Notes

2026-07-02 08:39:16 UTC

- reply

https://github.com/eddieoz/btcmesh

2026-06-29 09:17:23 UTC

- reply

Is it anti-Tor Browser? Signed in with my nsec seemingly okay but on https://nostrhub.io/create I get a toast of
Failed to publish
No Promise in Promise.any was resolved
whether I click save draft or publish NIP with all required fields filled with copypasta from https://github.com/nostr-protocol/nips/issues/2360

2026-06-28 18:31:21 UTC

- reply

You can just do things like that? Hmm, maybe I need to vibe-code BIP173Nostr, a client for Nostr where people salt their nsecs & on-chain zaps go to the p2wpkh derivations https://github.com/nostr-protocol/nips/issues/2360

2026-06-18 18:11:07 UTC

- reply

Considering what Mossad did with the pagers, what are the odds they'll rig Iran's nukes to detonate on Iranian soil/ships?

2026-06-14 13:10:52 UTC

Odd, a bunch of sparrows are pecking at concrete pavement, did someone spill seeds?

2026-06-07 15:50:38 UTC

- reply

Seemed like a game of reverse karma for both sides, make mistakes=get rewarded later. At least it didn't go to shootout, I find those super boring outside hockey movies LOL

2026-06-07 15:41:48 UTC

- reply

What
You
Doin'
Hurricanes
?

2026-06-07 10:54:56 UTC

- reply

WYDH LOL
https://youtu.be/wYBsNDGOMhg?t=188
(would've posted screenshot but "Upload failed Could not upload file." thanks, Blossom servers, really helpful)

2026-06-05 17:29:35 UTC

- reply

Would've helped if I watched my own repo for all activity... I thought I'd get an email of any new issues other than my own by default, now I will.

2026-06-04 09:42:32 UTC

https://infosec.exchange/@tomgag/116690952101130544

2026-06-04 03:48:15 UTC

- reply

https://www.casascius.com/fulllist.txt

2026-06-02 04:41:44 UTC

- reply

https://news.northeastern.edu/2024/02/09/anti-aging-pill-senior-dogs/

2026-06-01 00:22:54 UTC

- reply

https://chat.iris.to/

2026-05-31 05:06:40 UTC

- reply

Are you watching the series in reverse order? LOL

2026-05-28 16:21:28 UTC

- reply

25 for me

2026-05-26 16:28:06 UTC

- reply

@nprofile…xvjn

2026-05-26 10:29:10 UTC

- reply

Added concomitant protection against the GitHub user having their BTC address updated by another GitHub user if the maintainer accidentally approves.
Another thing I can't pentest against my own entry with only one GH account.

2026-05-26 07:53:12 UTC

- reply

Added code that should prevent the maintainer successfully approving a removal request by one GitHub user for another GitHub user's entry.
Without a second account, I can't pentest against my own entry, only verify it'll still remove me via script if I request it LOL

2026-05-26 03:23:44 UTC

- reply

Maybe the worst cancer was the state anyone lived in, along the way.

2026-05-26 02:48:45 UTC

- reply

tl;dr L1 allows me to be effectively self-sovereign for free
One of the biggest value propositions for me has always been that I can put 1 of my bitcoin addresses out in public & not need any technology or a third-party provider (nightmare nightmare nightmare!) for fund management between the time it's generated & the time it's spent from. So, I use L1 exclusively.
P.S. I feel like I'm probably doing more than my part for society already & any recyclables I cash in don't really even the karmic balance. In addition to my litter collection I described above, I'm also hunting/killing cockroaches in the street around midnight (first spotted this month), reporting vandalism, bulky illegal dumping, discharge of pollutants into storm water drains, stolen shopping carts, dead animals that may need testing for zoonoses, trespassers encamping on private property, moving reusable illegally-dumped items to better locations & putting them on Craigslist free... overwhelming trying to remember everything from on patrol.
My city has a public reports website where everyone can see things everyone else reported (except 911 calls & some other exceptions), and it's rare that I see anyone else had reported something in my immediate neighborhood. I also have email alerts set on Craigslist & I almost never see neighbors posting their stuff as curb alerts, they just curb it & skip the alert.

2026-05-25 19:21:39 UTC

Introducing #BTC2Free ♻️₿
People donate Bitcoin.
Participants offer items on Freecycle in return.
Turning magic internet money into generous real-world giveaways.
https://thebutterzone.github.io/
Currently in beta. GitHub account required for directory submissions.

2026-05-25 01:15:50 UTC

- reply

Fees either 0 or negligible. When they were 0, I'd often get to first confirmation in next block or the block after that. https://primal.net/e/nevent1qqsfuu2wwd7tu9u87zydrmur9s75rtsf6wnejv0wy835zzh5l844essk5ux7g

2026-05-24 16:05:44 UTC

- reply

When I started in bitcoin, I routinely transacted with 0 sat fees & in Q3 2025 my 0.1 sat/vbyte confirmed. 🔪 high time preference 🩸

2026-05-24 08:42:44 UTC

- reply

P.S. In case this was why you're asking them, this isn't intended to allay their privacy concerns whatsoever; as indicated in my opening para,
this is only about adding BTC QC theft prevention (with a good enough passphrase).
Took me too long to realize/properly interrogate Gemini that QC compromise of an nsec merely from the npub will also compromise even-y p2pkh & p2wpkh deterministic addresses from that npub & all coins sent to them.
I suppose if you wanted to (or even could) add a p2tr payment target that overrides your on-chain Zap address, code can also be written to salt your nsec & output that instead of p2pkh & p2wpkh addresses & WIF only. But someone not me, should try that.

2026-05-24 06:16:34 UTC

- reply

Did you receive any payments (or could you have) while it was unattended those two months?

2026-05-24 05:48:55 UTC

- reply

obligatory gm

2026-05-23 20:04:23 UTC

- reply

Found in this bag next to the sidewalk 5-23-2016
https://blossom.primal.net/a23570e2afba10c9897d78ae7494d596c54d3d338b7220f9ffec5328462ae32d.jpg

2026-05-23 17:21:30 UTC

- reply

The only real risk to everyone (who doesn't need 24/7 guardianship/caregivers & can easily keep on-chain zap coins from being spent with any others) is that it's not public key hashed addresses, it's Taproot:
https://primal.net/e/naddr1qvzqqqr4gupzqtshhpkkjtyhnw6m0skah8msuqh8dw7rtzh6jkkxsy6sg7a7zrszqqk8gctswfhk7arn943xjem8v4ez6ct5w3skx6edwejkxar0wgkhg6rpdckkvat5w4ex2tt3vvhqvqgk

2026-05-23 17:03:35 UTC

- reply

Perhaps the first on-chain zap was discovered to have been received 3 years ago...
https://primal.net/e/nevent1qqspkeev0047sw9tc28lf4vrqr7feaxr0q6688ck3aa09lc6j3h7apgpve4eq
And then came this thread the next month in 2023... https://bitcointalk.org/index.php?topic=5473719.0
Can't put the genie back in the bottle, or undo the laws of cryptography; in Python, anyone can derive a bitcoin address from virtually any data.
The only way to "win", is to not play against all human/machine-kind - don't even generate a npub/use Nostr, in the first place.

2026-05-23 16:52:42 UTC

- reply

Since I'll only use L1, gotta resist the urge to mentally check out whenever I see Lightning/L2/zaps/sats, but...
I thought of a similar program but inverted? People can get paid BTC in advance to drop their recycling in public & post a location photo, so whoever picks the recycling up can cash in at the minimum fixed per-pound rates set by the state. https://bitcointalk.org/index.php?topic=5582600.0
P.S. While I pick up neighborhood litter, on average every week it's not big bags' worth. I just separate the organics/recycling/textiles/trash & stuff that could be recycled but is excluded as such from municipal bin collection. I almost always fit the week's littered trash into my partly-filled kitchen trash bag & that's all the municipal collectors get in that bin (which has way too large a capacity for almost everyone, who got it by default/opt-out).

2026-05-21 10:03:18 UTC

- reply

They say; not my website, and I don't really want to run Sparrow because that would be a lot of time/money getting something compatible.

2026-05-21 04:34:24 UTC

- reply

🖤 🤣 Hell yeah! https://primal.net/e/nevent1qqs8cva22y2nnnuqahgyufx3xn4umgvu5ccrf9wtk6qnng4f9fqnfls4g8j6y

2026-05-20 16:35:52 UTC

- reply

npub>P2TR
(Taproot)
https://nostrfinance.com/wallets/overview/

2026-05-20 13:42:16 UTC

- reply

Is NIP-26 a no from you?

2026-05-20 04:45:02 UTC

- reply

The open-sourcing of Google Authenticator might have been the only good security thing they provided to the public. Although the devs of RFC 6238 (TOTP) & RFC 4226 (HOTP) should deserve most of the credit.

2026-05-20 04:31:47 UTC

- reply

Doesn't have to be, if the sender could just send from their non-Nostr-linked wallet to the receiver's Nostr-derived zap address.

2026-05-20 04:29:22 UTC

- reply

Pretty sure it was one of them who posted "anyone want on-chain zaps?" or something to that effect, so at least everyone saying yes in the replies should have gotten them.

2026-05-20 03:32:38 UTC

- reply

Me personally, as I was shocked to discover they made on-chain Zaps go via p2tr instead of p2pkh or p2wpkh, I don't plan to spend/save them at all, they're burned.
Academically (for people who think Taproot is fine), I would say if people transfer Zap sats to cold storage, they should dedicate one cold storage address for receiving all their coins they ever received at a public address that was associated with their identity (whether actual or same-pseudonym). That means all the Zap sats go there, all the p2pkh & p2wpkh tipping/donation address coins also go there, and then that cold storage address either already was separate from every other address by keeping it as a paper wallet or 1-private-key-only wallet file or at a minimum, frozen & labeled as cold storage within their main wallet. Any of those would be simpler than coin controlling the cold storage UTXOs out of every TX.
Deleted/reposted to answer your second question in context with that last option, freezing it that way makes it that much easier to unfreeze & immediately add only the cold storage address to coin control if you ever want to spend the cold storage. Just make sure if you have a change output (I personally try to avoid spending a key until 100% of it goes to receiver with no change), it goes to a new change address that you label & then freeze (and burn/label as burned, the previous cold storage), because that's your new cold storage.

2026-05-19 16:38:40 UTC

- reply

But it goes through somebody's services (have not been able to get it to work with the mobile server app Mandacaru), left Google Play review:
Install on adopted SD (~19GB free) <-> internal storage
Set Electrum server to 127.0.0.1:50001 non-secure (Floresta/Mandacaru)
Flip the offline switch back & forth, server connects (no restart)
Scan a xpub & a zpub from Electrum desktop "Cannot read property 'length' of undefined" when I try to look at my transactions list...
Refreshing transactions of those imported watch wallets appears to host a game of "will it be no change, implausibly high balance, or lower balance vs what Electrum says?"
---
Mandacaru & Electrum Android work together ok, at least when Mandacaru finally finishes getting all the filter transactions via user rescanning over and over and over again. And its coin control is limited to freezing addresses & UTXOs vs picking them in the send transaction flow.

2026-05-19 15:51:47 UTC

- reply

Everything may be "risk" but almost all risk assessments, are actually FUD.

2026-05-19 15:47:18 UTC

- reply

Flipping through my memory of dozens-hundreds of notes I read about this, I think some of the devs' intent seemed to be around letting people break out of the circular zapping back & forth to infinity, but there was also amenability to adding some friction, eg. mixing out.
That's fine if it's an option, but there should also be a unilateral exit without friction or extra fees.
What does $10 even buy you these days?

2026-05-19 15:36:58 UTC

- reply

https://blossom.primal.net/d513ab695777b1684edd32faa9584fe11f6738283877dd14ca7f13e1937a4070.png

2026-05-19 12:04:50 UTC

- reply

Which, if fully-honored, would mean every single one no longer existing.

2026-05-19 06:23:14 UTC

To whoever sent me that on-chain zap that I found with https://openetr.org/bitcoin/check-balance - consider it burned.
Please, nobody on-chain zap me; I won't do Taproot, so all you're doing is burning BTC.

2026-05-19 06:05:06 UTC

- reply

Hey hey hey, no stolen valor!
https://en.wikipedia.org/wiki/Purple_Heart

2026-05-19 06:02:52 UTC

- reply

Everything is always at everyone's own risk; no amount of warnings to this effect will ever be enough for paternalists, who act like it's possible for people who need 24/7 guardianship/caregivers to use bitcoin, let alone the internet, safely alone.

2026-05-19 05:52:22 UTC

- reply

Maintaining proper public tip/donation address hygiene isn't difficult enough to, in good faith, consider receive-more-than-once reuse with burn/spend-all-to-0-only-once non-reuse, an antipattern.

2026-05-19 05:43:37 UTC

- reply

How would having the p2pkh or p2wpkh address derived (without vendor lock-in) from the nsec hurt peoples' privacy, if all they're doing is clicking a zap button with a bitcoin:[derived-address] hyperlink & no Nostr interaction is coupled with that?
That, at least, would be historically precedented, vs whatever Taproot/Craproot? stuff is cooking.

2026-05-19 05:34:39 UTC

- reply

No way for me to opt out of people paying to a brainwallet address derived from my handle, either. Cryptography doesn't give a F.

2026-05-19 05:22:57 UTC

- reply

Say that in your bio?

2026-05-19 05:01:47 UTC

Show me the message then, A-HOLE!
https://blossom.primal.net/2dd805b424b283797c12e2af147c5619d66ae3ed76bc1791073e455723dcea04.png

2026-05-19 04:59:11 UTC

- reply

https://primal.net/e/nevent1qqsyc4uwm37k6l85ljmf2g9rm28d79xn462n8kzkk8t4yggrag89hac50uxwy

2026-05-19 04:57:41 UTC

- reply

Don't forget the sauce, boss! https://openetr.org/bitcoin/check-balance

2026-05-19 04:50:51 UTC

- reply

Have you come across NIP-26 root/child key delgation for posting that keeps the root key safe for payments only? I think I just did yesterday after wondering why there were extra 2 pubkeys in https://iris.to/settings/devices (now deleted, may make some new ones safely).

2026-05-19 04:44:57 UTC

- reply

Nah, forever undefeated will be people who publish their P2PKH/P2WPKH/P2SH tip/donation addresses from accounts required to be more tied to their actual identities than Nostr. Except we're not incompetent to the point of needing 24/7 guardianship/caregivers, we know how to coin control.
Too bad for totalitarians, that the fundamental rules of cryptography can't be broken to make it impossible for anyone to know how to pay anyone else.

2026-05-19 04:35:28 UTC

- reply

https://primal.net/e/nevent1qqsv2g6acwngx3hh2jyznnnthgkevvtvl9r3shvdqh4xpxrse5jqzrc5ng5qx

2026-05-19 04:35:04 UTC

- reply

JFC, cringe! Stop using Kill Your Customer exchanges, EVERYONE!

2026-05-19 04:33:00 UTC

- reply

What's the issue on the sender side? Do you even ̶l̶i̶f̶t̶ coin control, bro?
"your entire onchain tx history"
You're not tipping people with transactions that spend every single UTXO from every single address in every single wallet you have, are you?

2026-05-19 04:24:44 UTC

- reply

Resorting to accusation of mental illness & egotism isn't debating. Each individual has the right to decide qualitative tradeoffs.
No matter how "easy" it is, I don't want an integrated or standalone LN wallet & I see Nostr as pathologically bound to L2 with no truly meaningful way to receive frictionless L1 payments (putting tip/donation address in bio is barely meaningful).

2026-05-19 03:39:01 UTC

- reply

bITcOiN Devs sTilL haven'T MaDe it ImPosSIBle tO derive FROm pRActICAlLY anytHING & SHAre ADDrESses pUBLicLy fOr Tips/DoNAtIoNs?
dO YOu Even KnOW how TO BREAK THE FuNDaMENtaL LAwS OF cryptOgraphy?
aRe YoU COMPletELy REtarDed?

2026-05-19 02:26:30 UTC

- reply

https://www.freecycle.org/member/tbz1
#nevent1q…5nag

2026-05-19 02:16:59 UTC

- reply

1) AYFKM, moving the goalposts right now? You didn't have any qualifications with "Link me where that was said".
X, Twitter back then, is where I learned of Nostr for the first time because it was being censored by totalitarians.
2) Oh no, they didn't take into account every possible thing you could come up with in THEIR character-limited post! How dare they!
Goodbye.

2026-05-19 00:43:15 UTC

- reply

If your thesis is that the masses aren't that careful, what you just described would not fit, because that's closer to "being careful" - sending or sweeping a bitcoin balance out of the Nostr combo client+wallet purpose-built to accept & manage on-chain zaps, or exporting/importing the private key from it as backup, into a separate btc wallet.
What does this btc wallet look like, anyway? Is it a crapware wallet that people installed despite negative reviews from Gigi & company, that it only has one receiving address & forces spending reuse?

2026-05-18 18:31:40 UTC

- reply

HFSP

2026-05-18 18:16:09 UTC

- reply

If "on chain zaps"=craproot instead of P2PKH or P2WPKH derived from nsecs, then even 3 might be too many.

2026-05-18 18:11:18 UTC

- reply

0.1 sat/byte, low time preference, frack fee estimation

2026-05-18 18:08:29 UTC

- reply

ooga booga UTXO management problem permanent, coin control hard

2026-05-18 18:05:58 UTC

- reply

Indeed.

2026-05-18 16:32:27 UTC

- reply

Watch out for suuper professional K&R crews, they might think the "131100" address balance means you just received $10,000,000,000 USD equivalent of BTC!

2026-05-18 15:59:58 UTC

- reply

Might we see a payment target box on https://primal.net/settings/profile that allows P2PKH/P2WPKH/P2SH addresses & not just "Bitcoin Lightning Address"?

2026-05-18 15:48:29 UTC

- reply

https://x.com/TaoistBitcoiner/status/1676276971821572109
"The problem with using immutable identifiers based on our biometrics is that they can never be changed, so if/when leaked, the security breach of our ID is permanent.
Our #nostr identities have similar key management issues, but at least those are disposable & psuedo-anonymous."
https://x.com/mdhardcastle/status/1893736080437916065
"npubs (nsecs) are disposable, they are not an account or an identity.
This is not really understood by many people even on NOSTR"

2026-05-18 14:25:20 UTC

- reply

No less FUD-ery with memes.
https://primal.net/e/nevent1qqsfqppl9afhhj7kzl78gkyfr0m8xgwvj6d0p5xf8lx3jpazc8twl6qknvfmt

2026-05-18 14:23:06 UTC

- reply

Kidnappers somehow simultaneously sophisticated enough to capture targets, but too unsophisticated to know that the "5000" balance on an on-chain zap address means all they get is the equivalent of $3.83 USD (as of Preev right now).

2026-05-18 14:17:15 UTC

- reply

Those who are at that level of incompetence, in need of at least one person to act as their legal guardian & caregiver until death, don't need improvements, they need to be told, point blank: don't use bitcoin & it's not even safe for you to be alone using the internet, period.
I've never been a bitcoin evangelist & I don't believe anyone in this dev space can work the miracles needed.

2026-05-18 14:04:39 UTC

- reply

AYFKM? They absolutely have, starting years ago; I've had multiple nsecs since then.

2026-05-18 14:01:33 UTC

- reply

Meh, anyone who's put their P2PKH/P2WPKH/P2SH or whatever address on Nostr has already made the OPSEC tradeoff. The deterministic derivation just makes it a lot more dangerous for no-wrench funds loss (but only if anyone actually zaps more than 0 to it), since everyone's shuttling their private key around clipboards & possibly screens in the clear/no asterisks, for RATs to eat.

2026-05-18 13:52:03 UTC

- reply

What's "retardarion"/retardaTion about pointing out that an npub & its associated on-chain zap address, both derived from the same nsec, can't be changed?
Why not just request "put in your own BTC address" fields that make each user's zap button turn into "bitcoin:useraddresshere"? I think everyone would prefer that at a minimum, with other options TBD added later.

2026-05-18 13:41:48 UTC

- reply

A bunch of clients/interfaces I don't recognize (& don't particularly want to install now that I've seen Taproot enter the chat) have come across the feed, but if Nostr on-chain zaps were to get to the point where at least one client would just compute then let me copy my non-Taproot WIF under the nsec I logged in with (https://primal.net/settings/account is where it appears here), I would want to import that to my discrete Electrum wallet just to keep an eye out for any zaps. As it stands, the discrete wallet has the result of my own nsec-WIF computation, both the uncompressed & compressed ones. I wonder if either WIF private key would match or they'd do non-Taproot derivation differently than what I thought standard.
At a minimum, would like "put in your own BTC address" fields that enable my on-chain zap button turning into "bitcoin:myaddresshere" or whatever, sorta like X's app. Could have sworn I saw a note about that coming back to one Nostr client's UI that was broken & fixed, but I struggle to find that post again.

2026-05-18 13:37:09 UTC

- reply

Do you have any links to instances of this actually happening? Pretty sure everyone who was tipped more than 1 ₿ in what could be codenamed Operation Santaoshi back in 2012, have still not been targeted to this day & their meatspace addresses were definitely known to some.

2026-05-18 12:53:03 UTC

- reply

Nobody with a brain who actually uses it properly will allow the on-chain zap address to touch their significant hodlings, whether by sending BTC they already had to the on-chain zap address, or spending from the on-chain zap address more than once (exposing the public key in spite of the normalized warnings about exposing public keys by spending from the same private key more than once), nor with other coins not frozen/controlled/fully-wallet-separated-away. Proper hygiene has been the norm for over a decade.
If you don't believe it or don't understand it, I don't have time to try to convince you, sorry.

2026-05-18 12:37:50 UTC

- reply

Payjoin = #JustChangeOutputPrivatization?
All I want to do is (when it's time to burn the nsec) consolidate all the on-chain zap UTXOs that were ever received into 1 output (where the hygiene starts anew)... no bloody change, ever!

2026-05-18 12:26:15 UTC

- reply

https://en.bitcoin.it/wiki/Address_reuse
Example 1: Not applicable. Nobody is going to commit armed robbery to obtain anyone's minuscule on-chain zap amounts. And nobody with a brain who actually uses it properly will allow that address to touch their significant hodlings, whether by sending BTC they already had to the on-chain zap address, or spending from the on-chain zap address more than once (exposing the public key in spite of the normalized warnings about exposing public keys by spending from the same private key more than once), nor with other coins not frozen/controlled/fully-wallet-separated-away. Hygiene not difficult at all; the norm for over a decade.
Example 2: Exchange address is the one being spied on, N/A
Example 3: See #1
Example 4: So what if an exchange blocks transactions to your address? The exchange account-holder can ask you for a unique address.
Still not evident how Ditto "destroys privacy for the ENTIRE bitcoin network... fucking everyone, not just themselves". Do I need to look at Ditto's code myself & then learn to code after I realize I have no idea what I'm looking at? 🤣

2026-05-18 11:51:52 UTC

- reply

I'd heard Taproot was bad, but does it show your on-chain balance of every address in every wallet you have, or just of a single address derived from your nsec? 🤣

2026-05-18 11:47:03 UTC

- reply

Clown World News at 11: person beaten with a wrench & robbed of the equivalent of $5 USD in bitcoin

2026-05-18 11:44:19 UTC

- reply

Did the entire crypto industry normalise address reuse? When industry wasn't around in the earliest days after Satoshi paid Hal P2PK for the first time, then P2PKH for public tipping/donation addresses became the first norm & warnings about exposing public keys by spending from the same private key more than once, were the norm everywhere I went for years, then a few P2SHs would pop up every so often?
Like OMG, I'm going to get wrench attacked because the only publicized address in my wallet with most minuscule amount of BTC of all, is associated with my identity! Satan forbid I use my brain & only spend out my public address's UTXOs in consolidation to a single fresh address, without linking any of the larger ones via coin control/freezing all other addresses/exporting the private key to a 1-key-only wallet!

2026-05-18 11:23:12 UTC

- reply

If Nostr is hitching its wagon to Taproot for this instead of P2PKH or P2WPKH & no range of options that include pasting in my own of those P2s (whether they're derived from my nsec or just a typical seeded Electrum address), I'll try indicating as best as I can that anyone who zaps me is burning their BTC on the altar of Taproot.
Prequel reply?
https://primal.net/e/nevent1qqs8h9whjs7uqz4mtmm2l2zujva2uv4ys7c6ue40a77dgtmgj4j8mvc738ccl

2026-05-18 11:13:55 UTC

- reply

Default or not (haven't seen any indication either way), it seems like "you can't stop the signal" because at this point, aren't what we're seeing is debate about whether there should be a GUI for seeing the signal that may have been possible for years? https://bitcointalk.org/index.php?topic=5473719.0
From what I gather, you can derive a P2PKH address from your nsec thusly:
In terminal: echo -n "nsec..." | shasum -a 256 (this gives you the 64-character bitcoin private key hex)
Then convert that to wallet import format, with BitAddress (offline) or...
Python
import hashlib
import base58
# 1. Your 64-character hex private key
hex_key = "YOUR_64_CHARACTER_HEX_KEY_HERE"
# 2. Add '80' for Mainnet (use 'ef' for Testnet) and append '01' (compressed)
# Note: Remove '01' if you want an uncompressed WIF
extended_key = "80" + hex_key + "01"
# 3. Double SHA-256 hash
first_hash = hashlib.sha256(bytes.fromhex(extended_key)).digest()
double_hash = hashlib.sha256(first_hash).digest()
# 4. Grab the first 4 bytes for the checksum
checksum = double_hash[:4]
# 5. Append checksum and encode to Base58
binary_data = bytes.fromhex(extended_key) + checksum
wif = base58.b58encode(binary_data).decode('utf-8')
print("WIF:", wif)
---
Then you import the WIF into your wallet, copypaste the corresponding address that appears to Nostr, and obviously freeze the public address in your wallet, or coin control the public away from the private transactions, or go nuclear & have a 1-private-key-only wallet for on-chain zaps.
Could a Nostr client not compute all that itself & along with the nsec, let you copy out the WIF for the derived bitcoin address?
Although... I saw mention of Taproot in a more recent noti (https://primal.net/e/nevent1qqs8tc9aspgcc72nj6u546a72kmj3vcxh8l2y9lx5rw0ap7unlnkd8s9rxz08) which would be a dealbreaker for me, if they're going that route instead of P2PKH/P2WPKH (more complicated) as on-chain zap addresses.

2026-05-18 10:51:27 UTC

- reply

I said "as-is" & then you added nuance that was lacking but said I was wrong. Ok thanks bye.

2026-05-18 10:48:30 UTC

- reply

🤣
It's been a long time since I've seen 100 BTC tips...

2026-05-18 10:46:25 UTC

- reply

https://primal.net/e/nevent1qqsfr4j9c3dxwxgd9tl7u6tt9lxa3wqlmnf70jgquvw5rw0y9rcc98cjd4huk

2026-05-18 10:39:48 UTC

- reply

Simplest form of coin control without silent payments would just be to have a one-private-key-only wallet for the on-chain zap address, and when you properly consolidate all its UTXOs into 1 output elsewhere (and burn the key/nsec), the hygiene starts anew for you (or the recipient, if it was an actual payment).

2026-05-18 10:27:43 UTC

- reply

At least this ^. The only signal I need is L1 BTC directly to my address, with as little friction as possible (bitcoin:bc1/1... or an even better way). Whether others see this in a Zap GUI element, or on a blockchain explorer or watch-only wallet stalking my public tip/donation address... /shrug

2026-05-18 10:14:42 UTC

- reply

Ah. https://primal.net/e/nevent1qqsppf085aw2849pc993fngkjeatjavh2rjetch0kcqtep64psgvjkgvasrj8

2026-05-18 10:12:59 UTC

- reply

Linkable, but only actually linked if you either don't possess a fully functional brain or if you do, you don't use it properly. It isn't difficult at all.

2026-05-18 10:09:29 UTC

- reply

Hyperbolic & profane, but would you like to explain how?

2026-05-18 10:08:06 UTC

- reply

What is your actual objection (to what is bringing the option for public tipping/donation addresses, longstanding all the way back to the first P2PKH & P2PK before that) other than profanity?

2026-05-18 10:04:56 UTC

- reply

https://primal.net/e/nevent1qqsfxqpnjhhuk080emkvx4s7x9nmaz2yl8arkp32klk2tnc3lv3ppssjw6zjg

2026-05-18 09:58:52 UTC

- reply

... as long as they trust Liquid whatever/whoever.

2026-05-18 09:54:19 UTC

- reply

Why so serious? The option to publish tipping/donation addresses has been around since P2PKH (and P2PK before that), and shouldn't be treated profanely as if a novel security vulnerability. It's just one address that's public. That you can easily keep separate from all your other addresses/UTXOs.
This concept around Nostr has been congealing since at least 2023: https://bitcointalk.org/index.php?topic=5473719.0

2026-05-18 09:46:15 UTC

- reply

Why? It's just one address that's public. That you can easily keep separate from all your other addresses/UTXOs. Tipping/donation addresses shouldn't be treated profanely as if a novel security vulnerability.