Last Notes
This is forcing me to learn about things like side chains and pegs. So from talking with an LLM, it seems like the custodial problem with rootstock is "pegging out," i.e. releasing escrowed BTC when RBTC is getting redeemed. Bitcoin cannot know mechanically when RBTC gets redeemed, so there has to be a federation of entities that are trusted to correctly operate PowHSMs which co-sign the bitcoin transactions that release escrowed BTC. And these are held out to be "respected companies" but their "identities are not public," which raises the question what basis there is for the respect. And then there is still the other issue, i.e. that it's not clear what exactly would stop bitcoin miners from reorging rootstock. The miners get paid in BTC no matter what happens to rootstock, so beyond the small fee incentive they get for participating there doesn't seem to be anything they'd lose by attacking rootstock. At least at first glance, it doesn't necessarily seem more robust than Ethereum.
I haven't used anything FROST-based, but I think I would if I could do it in a way that seems more secure than regular NIP-46, and convenient to use.
For it to be more secure than regular NIP-46, I would want to require all shards for signing and keep exclusive control over at least one shard myself. If there isn't anything in the cryptography underlying FROST which makes it inherently less secure than using an unsharded key, it seems that this way of using it would be at least as secure as regular NIP-46.
And then on the convenience side, the actual signing would ideally be controlled through an app that sits on my phone and feels generally like Amber, and that app should probably hold one of the shards over which I have exclusive control.
I've only taken a cursory glance at FROST, but if there is something that provides this kind of experience or something equivalent, I think I'd try it.
Huh, so it's starting to sound like inkan would likely run on rootstock. One question then is whether that would be advantageous as compared to ethereum. I need to better understand what merge mining is. It seems like rootstock gets a lot of hashrate from it but it's not clear if the miners have anything really at stake there, i.e. it seems like a large pool could reorg rootstock without losing anything? I'm not sure if it protects against reorgs in the way in which Ethereum finality does. Also, rootstock seems like the more exotic product and it seems to have fewer endpoints, so it might be less suitable for broader adoption than something based on ethereum maybe. But I first need to do more reading to really understand how it works.
thanks, let me know any questions any time.
Actually you can simply keep using your current nostr keypair and make it the signer for a cold storage identity, this just came up in another conversation 👇
#nevent1q…hmyc
That seems right, I also just responded with the same reference to the NIP draft.
By the way, I'm still trying to get the word out on this key rotation system.
If you go to the "Explore" menu at https://www.inkan.cc, you can interact with cold storage identities that have never themselves signed a single Nostr event but that are nonetheless doing posts every day. If you like, you can also make your own toy identity on the homepage.
I realize there's a strong presumption among the Nostr community that this kind of thing doesn't work. But as a matter of fact it works quite well. I've been using it for many months now.
This also plugs into the recent discussion that we should adopt good practices while the Nostr community is still small. And in any event, it doesn't break anything in the current protocol, it just sits on top of it.
"Your nsec is still your identity"
FYI, here is a system where your nsec is no longer your identity. If you go to the Explore page at https://www.inkan.cc, you can interact with Nostr identities that have never signed a Nostr event themselves. You can also create your own toy identity on the homepage.👇
#nevent1q…qdtx
AI Search for Nostr has been live for a day now. 🧞♀
Here's the kind of thing it comes back with, more details below the screenshots 👇
https://image.nostr.build/c18f60cd4ba23a65401920bb361b784f38c41165f42503397d8403da29f88308.jpg
https://image.nostr.build/588d6eef47ac04ac01b93b8c2b6c2cb2602f77363250867b99550f49931d2198.jpg
https://image.nostr.build/9267f4938a9564508422b9d1867420cb8fae7af4e692fcc1257dbe77de990971.jpg
https://image.nostr.build/43455af0c02589ed30db66718ac178bec9b2b8e22eb270f171cb91232efc1cc5.jpg
#nevent1q…rlrz