This is our Self Order Point in action. Scan a QR code, pay it with your #LightningNetwork enabled wallet and get a random generated order name that you can mention to pick up your order at the coffee bar inside. @EnergyKitchen@puzzleitc@lightning
I'm back this week on the Optech live show to cover Newsletter #406 with co-hosts @bitschmidty and @murchandamus
We receive @guggero to talk about BIP322 updates and @0xB10C to talk about TCP hole punching for Bitcoin nodes behind NATs (and an update on peer-observer)
Other topics we cover:
- Ibis Wallet launch
- LDK Server launch
- @mempool v3.3.0
- new RPC `addhdkey` on Bitcoin Core
- BLIP42: a specification for BOLT12 contacts
- Other updates to Bitcoin Core, Eclair, LDK, LND and rust-bitcoin
Good news everyone, BIP-0322 is finally in status "Complete"! Hopefully now we can get broader support in wallets. There were a couple of minor but breaking changes in 1.0.0, so check out the changelog.
https://t.co/j2AsObYfwW
Ladies and gentlemen that have been waiting for BIP322: “Generic Signed Message Format”, there has been an update in the making to flesh BIP322 out and advance it to Complete. If you want to add review, you can find it at
https://t.co/Giffx2w5FZ
📢 LND v0.21.0 rc1 is ready for testing.
Basic Onion Messaging support lands in this release, along with the Payments store migrating to native SQL. Production Simple Taproot channels are also finalized.
Details here:
https://t.co/YTipKPiIRI
BIP: Oli Guggero (@guggero), recently retired Lightning infra engineer, is looking to take responsibility for BIP322.
Originally proposed by Karl-Johan Alm (@kallewoof) in 2018, BIP322 allows keys that control a bitcoin UTXO to sign any generic message. This permits UTXO holders of any script type to prove ownership without spending the coins 🪙
In his newly opened pull request, Oli catalogs and addresses open issues with the proposal and identifies work still to complete.
Read the full list of work still to do on the PR 👇
https://t.co/qSavN4CULh
Whenever I work in a JavaScript/TypeScript environment, I find myself missing the excellent library functions btcd offers (btcutil, psbt, btcec, txscript...).
Well, thanks to the power of WebAssembly (and Claude 😂), I no longer have to live without them: https://t.co/pjqBZBj9H7
@TomZarebczan Wasn‘t familiar with that library. But mostly performance, feature set, familiarity with the code base and it being battle tested (btcutil powers the btcd full node and lnd‘s on-chain wallet).
Whenever I work in a JavaScript/TypeScript environment, I find myself missing the excellent library functions btcd offers (btcutil, psbt, btcec, txscript...).
Well, thanks to the power of WebAssembly (and Claude 😂), I no longer have to live without them: https://t.co/pjqBZBj9H7
@roasbeef Definitely feels like that 😝 Though it's addicting too. How can you relax and do nothing if you could be feeding Claude with new tasks instead 😂
I'm hooked on Claude Code... In just one day I wrote a BIP-322 verifier library in Golang, with test vectors for almost all script types (p2pkh, p2sh-p2wkh, p2wkh, p2wsh, p2tr, including multisig and time locks), created a BIP PR and then published a NPM package for it...
There's a slight initial performance penalty of 210ms (on my machine with NodeJS) for loading the WASM blob. But after that, performance should be close to native, especially for things like ECDSA/Schnorr signing and verifying.
Our current release binaries are mostly-static; they still depend on some system libraries (libc & friends). Fully-static binaries would mean no runtime dependencies, and these binaries could support a wider range of operating systems, over a longer period of time.
We’ve just unified our SEPA and SEPA Instant infrastructure.
We’ve also migrated to local banking connections in Switzerland (CH) and Liechtenstein (LI).
Why it matters:
⚡ Faster processing
🛡️ Greater reliability
🏗️ A solid foundation for personal virtual IBANs
📍 Banking closer to where we operate
Infrastructure isn’t glamorous—but it’s what keeps everything else steady.