@wizardsardine CEO πͺπ. β¬π¨ Working on @lianabitcoin, self custody done right. Organized Breaking Bitcoin, BoB and @btcazores technical bitcoin confs.
Azores, Portugal
Joined March 2013
- Tweets18.3K
- Following815
- Followers11.9K
- Likes26.8K
I rarely get rid of my old signing devices unless they die.
Just found this oldie. Ledger HW-1 with Chainsmiths branding.
Kevin Loaec π§ββοΈπ retweeted
Text messages with a machine, in and of themselves, are not criminal, immoral, or dangerous, for there is no victim, whatever the content. It is the very same thing as with thoughtsβregardless of the content, no thought can be said to create a victim.
β’ If someone steals info and feeds it into an LLM, it was the theft itself which created the victim, not the subsequent text message.
β’ If someone uses the output of an LLM to hack a system, it is that subsequent hack which creates the victim, not the text message preceding it.
β’ If someone threatens harm to themselves or others through messages into a machine, here still the messages themselves cannot be said to have created any victim.
Imagining otherwise inappropriately reorients blame from its rightful place: the action of harm actually done by a perpetrator. Thinking harm =/= harm.
As humans integrate AI as an extension of their mind, policing at the message layer means to increasingly police thought itself.
Which company, which committee, do you trust to police your thoughts? Or do you simply want the thoughts of others policed, and not your own?
Weβve trained Claude to flag potential misuse in conversations, a technique we call self-assessment. Right after it responds, Claude gives a preliminary safety assessment of the conversation.
Since we began using self-assessment in June, it has surfaced misuse that our other safeguards werenβt designed to catch.
Because Claude has already read the conversation, self-assessment is very efficient. And unlike classifiers, which target a discrete set of harms, it draws on Claudeβs own judgment, so it gets more accurate as our models improve.
Read more on our new Safeguards blog:
safeguards.anthropic.com/202β¦
Kevin Loaec π§ββοΈπ retweeted
All Liana scripts should be recoverable in Nunchuk in the latest app versions.
Kevin Loaec π§ββοΈπ retweeted
So, the French socialists, and Parliament members just voted a tax, that they donβt understand, which would cost VideoLAN more than 1 million euro per year.
They are probably the most clueless politician on Earth? And they claim they want technological sovereigntyβ¦
@LaurentLhardit
#PJL2027 AdoptΓ© par l'AssemblΓ©e nationale : la "taxe assise sur les flux de donnΓ©es numΓ©riques Γ©mises par les fournisseurs de contenu et acquittΓ©e par ces derniers"
Selon les députés PS, "au taux de 0,055 ⬠par giga, un rendement de 10Md⬠est attendu".
assemblee-nationale.fr/dyn/1β¦
Kevin Loaec π§ββοΈπ retweeted
We are getting more audit requests than usual in the past few months, and we also don't have a CSO in the team.
If you are the kind of profile who'd love to be CSO in a tiny startup like ours, ping me. Role would require very deep understanding of Bitcoin, and preferably past CSO or strong infra experience.
If your exchange isn't using a Liana or Revault type setup for your bitcoin, maybe it's time to look into it.
Kevin Loaec π§ββοΈπ retweeted
Frog put the keys in the HSM. "There" he said "now we cannot leak the private key". "But our servers can ask the box to sign with the key" said Toad.
"that is true" said Frog
Use @lianabitcoin . v16 coming next week!
Kevin Loaec π§ββοΈπ retweeted
If you run lnd (or any services in Go) and accept connections from the internet, shut down your node *now* until you can patch your kernel or disable MPTCP.
Same goes for any internet-connected service but Go is one of the very few that turns on MPTCP by default.
Wizardsardine: here is a blog post about how we don't even trust the compiler on each dev machine.
Binance: lol one compromised laptop = 5Bn gone from the hot key
Kevin Loaec π§ββοΈπ retweeted
@revaultdev fixes this. When the new CSO is appointed, he should book an onboarding call with @KLoaec
Kevin Loaec π§ββοΈπ retweeted
Tu primera multifirma miniscript, con una sola hardware wallet de #Bitcoin.
Usando @BitBoxSwiss y @lianabitcoin
We are getting more audit requests than usual in the past few months, and we also don't have a CSO in the team.
If you are the kind of profile who'd love to be CSO in a tiny startup like ours, ping me. Role would require very deep understanding of Bitcoin, and preferably past CSO or strong infra experience.
I want self hosted AI hardware π π π
I don't want to pay the current memory prices π
wen cheap ram
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
