Earnest question: If we adopt BIP177 (which I already have) and start expressing sats as integers with the ₿ symbol on the left, what’s the best way to handle millisats? Showing them like ₿0.001 feels too confusing right now. Any ideas?

I have upgraded Mario Kart: Double Sats to reflect the changes outlined in BIP 177. 🫡

i think we should rename sats to bitcoin and bitcoin to mega bitcoin (i am serious)

It’s rad/mystical to me how Zeus allows for circular payments but lncli does not. I love it @ZEUS 😍

My jaw dropped View quoted note →

Why I'm for loosening the OP_RETURN limits ⏎ - In practice, OP_RETURN is already unconstrained: see Carman's OP_RETURN bot or Portland's Slipstream. - Encoding arbitrary data via OP_RETURN is far more responsible than doing so in witness data, as it's 4x more costly. - OP_RETURNs are prunable and do not pollute the UTXO set, making them vastly preferable to faux outputs that burden every node indefinitely. - Mining non-standard transactions that bypass mempools undermines decentralized transaction propagation, disrupts fee estimation, and increases block propagation latency (especially when compact block construction fails due to missing transactions). - This latency disproportionately impacts smaller miners and encourages direct submission to large, well-connected players, widening the profitability gap and increasing centralization. - Layer 2 protocols are especially sensitive to fee miscalculations, making transparent and measurable fee behavior essential to their reliability. While I share the distaste many have expressed toward tokens, inscriptions, and BitVM (when used as a casino), I care deeply about minimizing harm to bitcoin’s base layer. Allowing larger, standardized OP_RETURNs is a pragmatic step in that direction.

Mario Kart: Double Sats was a success at the grand opening of the Tokyo Bitcoin Base 🍄

Update for those of you who are interested in Mario Kart: Double Sats: I have identified the correct memory locations of the players' lap count and position in the race. And I figured out how to access this memory outside of the emulator, using Python. This means I can plug it into my LND node and get the game streaming sats in real time. This is one of the coolest, funnest, and nerdiest things I've ever done. Will have a working demo this week.

What should I name my zap-hack of Mario Kart Double Dash? (Once I finish it, it’ll stream you sats for every second you’re in first place, the audience can place bets on who they think will win, and power-ups can be sent over Lightning to glitch the game.) View quoted note →

Cypherpunks write code. Heatpunks balance load.

Who’s building an opt-in, open-source, customizable “algorithm” for Nostr? We need a way to discover cool bitcoin sh*t.

Bring back key changes. 🎵

fuck off forever

it’s now officially 💚 bitcoin brat girl summer 💚

If you see me zapping myself, no you didn’t. Jk. I’m testing my zapplications.

Zapper is my Nostr zap receipts key. As you can see, Nostr doesn’t really have a way of verifying zap amounts. So I zapped this post… a lot. ☺️ View quoted note →

My nostr zap receipt app is finally ready for deployment! It took a little longer than expected. 😃⚡️ What is the best hosting environment for persistent applications? I LOVE writing code but try to keep DevOps and network administration to an absolute bare minimum. Render? DigitalOcean?

Best bitcoin podcast episodes to listen to on my 26 hour drive? 🚗

Hello World. Testing from my own Nostr app.

WoS’s departure from the US is fabulous motivation for me to FINALLY add zaps to my LNURL server! ⚡️ Now to figure out how…