I can’t wait to test out an MVP of this. Sounds so cool
I think data-intensive stuff like video and decentralized apps will move to Holepunch, and punch links will get shared around via nostr.
Why even ask? Did he expect anyone to prefer closed source?
There's seems to quite nice articles and content on https://www.athena-alpha.com . First time seeing it.
(I'm not affiliated in any way, I just found the website)
Surprised I’ve never seen that one
🏝️ Honolulu BitDevs is next Monday (5/29) for any #nostrplebs that happen to be on island
https://www.hnlbtc.group/bit-devs/events/socratic-seminar-22/
Who needs a Pomodoro timer when you’ve got a pet that cries for attention every 20 minutes anyway?
Thanks for the feedback! When we share details of the key portability feature I’d love to hear what you think. You’re right that in multisig there are ways to recover from losing a device without needing the seed, and we’re trying to make that easy for the owner to do using the other device in the multisig setup. You can read more about this in another one of our posts: https://bitkey.build/losing-your-keys-without-losing-your-coins/
Everything’s about trade offs, and it sounds like your team is working hard to balance them. I’m sure it’ll check the boxes for quite a few people, and I’m excited to try it out myself!
Setup multi-vendor multisig, and then you don’t have to worry as much about each hardware wallet. One could be compromised without you losing everything.
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.
Not a fan of the seedless approach myself.
Flush niacin is the best preworkout
Yeah I expected to hear more about Holepunch since the docs were released, but I’m only aware of Keet. Holepunch definitely seems more complicated than nostr to develop on, but both have overlapping use cases.
From what I understand, it’s basically a way to create direct data streams between peers. So it seems like a great way to efficiently move around large amounts of data. Almost like BitTorrent but for dynamic data instead of static files.
I’d like to see something like this but with Holepunch instead of BitTorrent.
The interoperability is what blows my mind. Totally different micro apps can all tap into a shared data stream of all your Nostr interactions to create really personalized user experiences that all build off of each other 🤯
Sparrow is the best software wallet available. Deserves way more adoption
I keep waiting for projects other than Keet to pop up, but I haven’t really heard anything. I’d like more concrete examples of how to use Holepunch for different use cases.
You store the markdown files locally on your machine, so you can manually version control/backup however you want. I use periodic git backups for mine, but I also use their Sync service, which I think lets you restore old file versions too. 🤔