Oren ☂️ #BIP-128's avatar
Oren ☂️ #BIP-128
orenz0@protonmail.com.ln2.email
npub1xvtw...m7f8
Software Developleb https://github.com/oren-z0 Founder of RITREK.com Side projects: https://niot.space https://ln2.email
Spam bots are back? I get endless notifications after my last note on #Ditto 😢
Are you excited about the recent Bitcoin surge? Do you check the price before you even get out of bed? I vibe-coded an Android alarm clock that wakes you with happy music if BTC went up overnight, and sad music if it went down. Set it once, every day, or chosen weekdays. At alarm time it fetches BTC/USD, then plays Number Go Up or Number Go Down on the Android alarm stream. Press Stop and it reads the price. Play: https://play.google.com/store/apps/details?id=com.ritrek.btcpricealarmclock Open source: image
GM to all fiat miners out there! #FiatMining files.niot.space/4_5814628726503120982.mp4
If a future #AI loses control and starts philosophizing, it would probably build a simulation of the years that led to its birth. What are the odds of being alive during those exact years? #showerthoughts
I initially wanted to build the TimelockRecovery.com feature for Sparrow Wallet, one of the most popular wallets for advanced Bitcoin management, including multisig, air-gapped wallets, and more. But Sparrow is written in Java, and I've never worked on a large Java project, let alone one with a UI. So I implemented it in Python for Specter and Electrum instead. This week, I fed Grok and Fable the source code from Specter and Electrum and told them to replicate the mechanism in Java for Sparrow. A few prompts later, with some tiny improvements, and it works perfectly! 🤩 As a developer, it feels like knowing a few words of Latin and suddenly being able to speak any Latin-derived language. We live in amazing times! #dev #devstr #Bitcoin #BitcoinDev #Electrum #ElectrumWallet #Specter #SpecterWallet #Sparrow #SparrowWallet #AI
I'm a shy Israeli who won't do this, but I definitely know others who do - and it usually works for them. #Israel #rules
The idea that multisig wallets are created by importing xpubs (Zpubs) to a hot online computer and building the wallet descriptor there - is absurd. That computer can manipulate the xpubs of some of the signers, add another xpub inside the QR code that doesn't appear in text form, change the number of required signers, etc. Most users won't notice the difference on their small hw wallet display, and won't verify a receive-address on all wallets (i.e. hacker can replace one of the xpubs with his own, and could fool you into sending funds to an address where they are a co-signer). The wallet descriptors should be generated on the hardware wallets themselves, with clear instructions how to verify them on all other hw wallets.
Hardware wallets are hard to hack but can have disasterous bugs. Hot Phone wallets are safer against bugs (can be fixed via online update), but can have disasterous hacks. For example, while creating a 2-of-2 multisig on a hot phone wallet, the phone can show you a fake seed unrelated to the its declared xpub, and hide the real seed internally. At some random point, the phone can get a remote command to blackmail you, and only then you will realize you don't really have the real seed. People won't buy more than 1 hardware wallet, and I don't know how to solve this issue. Maybe UX for the Phone Wallets that shows a seed + xpub, and let you decide whether to use it or pick another one? You could enter a few seeds that the phone generated into the hw wallet just to verify that the phone didn't try to cheat, then use the last one without entering it to the hw wallet. Or maybe covenants?
vibe-coded a tool to test your air-gapped wallet ( @SeedSigner , @npub1j0dm...lwm0 ) against basic #DarkSkippy attempts: create fake PSBTs with a fake seed, and see if the HW wallet returns the expected signature and does not try to leak data: Obviously you should also verify the firmware's pgp, and this tool does not cover sophisticated #DarkSkippy attacks (i.e. that try to leak data only in certain conditions, like in transactions of specific amounts, or multisig setups). Thanks to @Frostsnap for building darkskippy.com and creating a real-world example.