wen miniscript

32.0rc2 testing binaries are now available bitcoincore.org/bin/bitcoin-… Includes the new getopenrpcinfo RPC (shoutout @willcl_ark). It returns a machine-readable OpenRPC spec of the entire RPC API, useful for generating client code and docs or diffing between releases.

With fast enough image processing, where no frame skipped, UX is much better with BBQr for larger payloads too.

We're adding multi-language support to@lianabitcoin , expected in the next release. Which language would you like us to prioritize?

I, along with @btcqna and many others, want QRs in Liana! But @pythcoiner is right, we need better UX, simplicity, and reliability, and first impressions matter. Air-gapped miniscript has everything to be the perfect setup for many use cases, but we must think strategically together about how to make the UX simple while keeping the setup secure and sovereign. BIP138 was a firm step in this direction and was quickly and well implemented. @pythcoiner has many other good ideas for a protocol, such as fetching batches of xpubs for key reuse. Let's make this happen!

Herencia en Bitcoin Creé un esquema de herencia en @lianabitcoin que pude restaur en Nunchuk, conservando las mismas condiciones de uso + tiempo para el acceder a los mismos UTXOs. Un mismo esquema de herencia, dos implementaciones diferentes. En esta prueba diseñe un esquema de herencia con dos caminos difernetes: ➜ Llave principal: acceso inmediato. ➜ Llave heredera: acceso habilitado después de 150 bloques.

You guys really should use Liana 😭 I won't always be there when shit hits the fan

We might be interested to build our own firmware, if funding were to follow.

- BIP138 based descriptor registration, import and export (C implementation of the great of @pythcoiner, @salvatoshi, Sjors and others) - k_quirc QR decoder is 2x faster and with better success/rate, using vector processing among other optimizations. github.com/odudex/Kern/relea…

Voting is the adult version of writing a letter to Santa Claus

Segwit miniscript was a mistake

ah, that's why Opus was being retarded this morning. Every single time they make the "old one" dumber instead of the new one better.

If your tomato sauce is too acidic, start from the basics and learn how to make tomato sauce!

This was never about protecting the user's ability to run Bitcoin on low compute hardware. It was about control. Protecting decentralization was their argument, now the mask came off: they were always trying to become the center.

There is no coldcard white hat. People who got their money stolen won't get it back. Even if it's in a trust now.

can we not?

I no longer tell people to buy Bitcoin. There's no point in trying to convince anyone. Not my problem if they want to keep losing.

Big win for multisig and Miniscript UX. Great work!

BIP138: Compact Encryption Scheme for Non-seed Wallet Data was merged to the BIPs repository. github.com/bitcoin/bips/pull…

The only thing that materially differs from my analysis is that you're using Core to set up a multisig wallet. But all my other points stand. It's still two general-purpose laptops. All 7 keys are generated by the same binary on the same machine, and signing happens on that same machine, so the multisig doesn't remove the single point of trust you warned about. Such a model still has many weaknesses, and is still a poor fit as an end-user product. The bottom line is Bitcoin Core as a software project was NOT started or designed as a Bitcoin wallet. To the extent that a wallet was included, it was a dumb accident. Using something for a task it wasn't primarily built for, and that doesn't get the same amount of care or attention, is just insane to me.