RawBTC / RawBTC is on Nostr

Unchained QA Engineer. Honolulu BitDevs host.

Last Notes

2025-01-02 23:55:03 UTC

I appreciate that @RabbitHoleRecap + No Agenda cover all the news I need to care about.

2024-05-10 22:59:16 UTC

- reply

😁

2024-02-13 17:20:13 UTC

- reply

the next step is to just put a pool of canola oil in the middle

2024-02-12 18:07:43 UTC

- reply

*with medium-to-high signal

2024-02-10 21:44:45 UTC

- reply

Liquid is federated, but it's an interesting way to consolidate UTXOs cheaply before you settle on-chain. Aqua itself is a good tradeoff balance for some people - interoperable with Lightning without requiring liquidity management. I consider it a decent onboarding tool for people that aren't yet ready for self-custodial LN like Phoenix, @npub1mut…23vg , @npub1xnf…lpr5 , etc. Avoids the upfront liquidity cost to establish a new channel.

2024-02-04 07:31:11 UTC

- reply

@npub1w69…zltw has some great content on this
https://graduallythensuddenly.xyz/pay-me-in-bitcoin-theory/

2023-06-27 18:33:45 UTC

- reply

Fat, lazy, rule-following tax cattle

2023-06-16 22:06:25 UTC

- reply

How is it?

2023-06-09 02:09:58 UTC

- reply

npub1m72pdynrlmrpstrxu49k828r5xjlqc9hgtz9zfmy4m30u40uqxgsgkjxux
primal.net/robby
🙏🤙

2023-05-17 19:32:53 UTC

- reply

I thought Jack had reposted their article from yesterday about seed phrases (https://bitkey.build/seed-phrases-are-sharp-edges/) and responded before I saw it was a new article about hardware device screens.
I don’t agree with all the reasoning in that seed phrase article. Ultimately, someone has to control the seed. If the user doesn’t keep a copy themselves, then they’re deferring trust somewhere else.
“Seedless” custody generally puts a lot of trust in the device securing that seed. Without a seed backup, hardware failures are catastrophic for singlesig setups. I would never do seedless unless it were multisig. But even with seedless multisig, losing a device means you have to deal with a more complicated key rotation process, rather than just recovering the same seed into a new device.
In Block’s Bitkey setup, it sounds like it’s seedless multisig “until you need to export the seed”. It’s yet to be seen how sovereign that recovery can be or if you’ll have to ultimately get permission to access a seed or move to a different multisig coordinator. It sounds prone to lock-in, but I’d need to read more about the technical details to know.
There are trade offs to various approaches, and I don’t think their seed phrase article properly highlights those trade offs.
—
But like I said, the article Jack linked in the OP is a different topic - hardware device screens. It seems pretty well reasoned, but I only skimmed it. I don’t know if I agree with all the listed attack vectors and risks associated with over-reliance on device screens. I prefer a screen on the device, but screenless might work well enough in their setup, since it’ll have a server-side component to help verify data.
Regardless, it’s a unique approach, and I’m interested to see how it develops. Will probably be a good onboarding option for less technical people.