๐Ÿ”ซ Alwin ๐ŸฆŒ๐Ÿด's avatar
๐Ÿ”ซ Alwin ๐ŸฆŒ๐Ÿด
thebutterzone@iris.to
npub19ctm...zf83
On-chain zaps via Taproot are burned, please use bc1q8yl7p85fzf82u5yuf8pelt58n7xzu3wnnjujfs or 16Di3DUzhK7Qz1esUXp9pyPQK2i2ifFYWR 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
๐Ÿ”ซ Alwin ๐ŸฆŒ๐Ÿด's avatar
TheButterZone 5 hours ago
In the end, I want nostriches to be optionally able to receive zaps to safe(r)-at-rest public key hashed addresses that are derived user/client (NOT server) side from their nsecs + passphrases of their choice (with only the slightest extra step of putting in their passphrase), versus unsafe-at-rest Taproot addresses (which don't need a passphrase at all in the current form of "on-chain zaps"). This option deliberately breaks the UI flow to any unhashed key derivations from the npub/nsec; the hardened form will need to be indicated as a payment target or something that points would-be zappers to it, away from any unhardened derivations. It also presumes the receiver isn't in need of 24/7 guardianship/care & is therefore able to practice proper hygiene unassisted, never letting their public zap (fka tip) UTXOs move with/near their privately-transacted UTXOs & never revealing their pubkey until it's balance-zeroing-TX/no spending reuse of the key time (as well as not completely losing their nsec+passphrase & all those UTXOs in turn). Anyone with me/who can do this better/at all?
I don't get the "X algo feeds everyone ragebait" meme. I'm supposed to be mad at the posts of people I follow, and because I like & sometimes repost them, get mad at the subjects they cover that make it into my FYP when I switch to that tab?
Introducing #BTC2Free โ™ป๏ธโ‚ฟ People donate Bitcoin. Participants offer items on Freecycle in return. Turning magic internet money into generous real-world giveaways. Currently in beta. GitHub account required for directory submissions.
Love having to teach Gemini 3 how to code JS for a GitHub Page when I'm learning everything as I go... /s Seriously, how difficult is it for you to not go directly into a curly bracket variable without putting a / inbetween that & the TLD? I really had to tell you that by copy-pasting the + "/" that you already had further forward in the const, after .TLD?
โ†‘