pull down to refresh
0 sats \ 0 replies \ @tombennet OP 27 Jul \ parent \ on: Private, serverless Bitcoin payments for indie devs bitcoin
Agreed, I'd love that. Wide availability of BIP 352 in wallets would avoid the XPUB step.
I agree! It's a stupid buzzword and I don't like it either. Problem is, I tested a couple titles with friends and this is the one which they immediately understood. Maybe I should've gone with your idea - FaaS is a good description.
But yeah, you're right. It's just someone else's server, which for the purposes of my tutorial means you can host a simple, stateless function for free, i.e. no Linux box to provision, no SSH, no uptime monitoring, etc.
It's classic engagement farming. There's a lot of anti-Core sentiment floating around, and it's easy bait to frame challenging topics as "Core wants to…" even when the authors aren’t Core devs.
- "Now core devs want to freeze coins" - the villains strike again!
- "Pretext of quantum computing" - obviously a smokescreen for their real agenda: destroying Bitcoin, presumably.
- "Want to freeze Satoshi coins" - because that’s the endgame. Simple good vs evil, us vs them.
A more honest headline would be "Developers propose freezing unprotected coins as part of long-term quantum resilience strategy", but I doubt that would get as many clicks.
Thanks!
And no - you can use a dice to generate the first 128/192/256 bits of randomness, but the final 4 / 6 / 8 bits which are appended to the end are generated based on the hash of the dice-based randomness you generated. Note that those 4/6/8 bits (i.e. the checksum) take it to 132 / 198 / 264 bits in total - always a multiple of 11. That's because each 11 bits of data encodes a word. So the final word in any valid mnemonic will be determined in part by the hash of the previous words.
I've tried to visualise this in the 'Fingerprinting entropy' section. It's definitely a tricky one!
Thanks Alex! That's great to hear. Your site's awesome btw, just spent a while digging through your charts :D
I'm thinking of doing a tutorial showing how to accept on-chain payments while preserving privacy, i.e. without exposing the same receiving address to everyone. Reckon that would be useful to people?
Blink wallet supports LNURLp, so yes. This solution should work with pretty much all modern wallets inc Zeus, Breez, etc. Full list of wallets supporting LNURLp available from @DarthCoin: https://darth-coin.github.io/wallets/lightning-wallets-comparison-en.html
GENESIS