@wizardsardine CEO πͺπ. β¬π¨ Working on @lianabitcoin, self custody done right. Organized Breaking Bitcoin, BoB and @btcazores technical bitcoin confs.
Azores, Portugal
Joined March 2013
- Tweets18.2K
- Following811
- Followers11.9K
- Likes26.7K
Liana v16, baguette edition
(yes, we began localization. Just a few languages supported for this release, help us for the next ones!)
We just published a new post to learn about Reproducible and Bootstrappable builds: wizardsardine.com/blog/guix-β¦
Kevin Loaec π§ββοΈπ retweeted
it's always cool to see real money secured by miniscript in the wild!
this ~61.8 BTC input could be spent by either two signatures from a set of three keys, plus 3 from a another set of six keys,
or a separate 2-of-3 quorum after ~36 days worth of blocks have elapsed.
Some thoughts about hardware, especially wallet-specific UX.
Until very recently, I was strongly against "non-standard" products, like Bitkey for example.
I'm now realizing that trying to support everything that comes out in Bitcoin is impossible, the amount of work to just follow all the new stuff (Silent Payments, Ark, Bip89 CCD, etc etc) and the work needed in UX to show that clearly to the user (so they don't fuck up) is just near impossible.
We took some design decisions in Liana, for example not having Absolute Timelocks available in the community software, because we don't have a good UX for it (and again, we believe users will fuck up). Or we only accept descriptors with one non-timelocked path. Again, just for UI/UX perspective.
Now that Liana has a really good UX (check out v16rc1), the main complaint of not-yet-users is the shitty signing device UX. I now understand why Bitkey went the route they did.
I still wish they had support for other software coordinators, including with Miniscript, and I hope they will. But I get that having control over the hardware UX is a huge selling point for end users.
TLDR: I think it's time for Wizardsardine to really start exploring hardware, either through custom firmware of existing devices, and/or making our own devices.
Obviously with a MVMS (multivendor-multisig) approach first, so we would still support all the Miniscript devices out there.
If you guys have any thoughts on this, shout.
Kevin Loaec π§ββοΈπ retweeted
An important discussion.
I hate the term βpaymentsβ for this but itβs true that if people arenβt transferring value using bitcoin then what weβve built is pretty uninteresting (even if financially valuable).
.@jack thinks bitcoin payment adoption isnβt where it should be. We want your ideas on how @Blocks, Spiral, and you can increase adoption within 5 years. Our trajectory needs changing. Hereβs more on our thinking. Now we want yours: github.com/spiralxyz/bitcoinβ¦ View article
Back to the office after 3 weeks of events, it's a bit intense :D
Liana 16rc1 is out for whoever wants to test it!
Kevin Loaec π§ββοΈπ retweeted
An update to Bitcoin Core's security policy
via @darosior on the Bitcoin-Dev mailing list
Kevin Loaec π§ββοΈπ retweeted
π¨ CRITICAL: GitLab flaw (CVSS 10.0) affects 12 years of releases.
CVE-2026-110264 could allow unauthenticated remote code execution on self-managed servers.
Read - thehackernews.com/2026/10/crβ¦
Kevin Loaec π§ββοΈπ retweeted
CEO of @wizardsardine, @KLoaec is back and has a solution for the attacks affecting one single device not affecting you/
The year has not been great for Bitcoin security and the year is not done yet.
In case you missed it, @Vladcostea went live again on day 2 of his livestream from the final installment of @tabconf.
This Podcast is not known for brevity, so it cannot be expected to do short summaries.
Ekrem Bal, @ekrembal, talks about @citrea_xyz pivoting to privacy with Crest, making Citrea post-quantum, why he would pick OP_CAT, and how Crest differs from Tornado Cash.
Kevin Loaec, @KLoaec chats about why so many people still use single sig in 2026, why vaults don't really have demand, Coldcard's RNG bug and funding open source without begging users.
Stu, @stutxo drops in with memes and script emulation on Bark.
Andrew and Buffer, @_buffrr of @spacesprotocol on names on Bitcoin at 32 bytes per batch, retiring the @tabconf namespace forever and why you shouldn't reuse your name's address.
Kyle Shirkness, @KyleShirkness and Jesse Markowitz of The Bitcoin Pivot, credit unions as Bitcoin on-ramps and Lightning service providers!
Full episode in the reply π
Talking to a lot of long time bitcoiners in the past two weeks, it's obvious that:
- there is a bitcoin fatigue (tech is moving, but people don't care, single sig or custodian NGU mentality)
- there is AI psychosis/FOMO
Bitcoin is freedom money. We achieved that already. (1/n)
I'm happy with Bitcoin the way it currently is, of course I think there are many things we can improve (privacy, security, usability), but I also understand why people feel that the industry is boring in comparison to the global reach AI managed.
This is why you need keys. Custodians verifying stuff by Whatsapp, or phone calls for that matter, isn't secure.
Use Liana, maybe add cosigners if you want, but don't "authorize" transfers without actually signing the transaction.
If you send me obviously llm generated emails, I will ignore them. You aren't worth my time if i'm not worth yours.
