Profile: bc552e99...
I am new to nostr. I guess I have to set something up?
Anyway, the cryptography is solid, it’s from the zcash foundation https://zfnd.org/ , and the crates make a good impression in my opinion.
When #frost becomes a viable multisig-style tool for nostr private keys, does the cryptography in some way allow for “converting” an existing nsec into a FROST structure?
In other words, could I retain my primary keypair and somehow make it into a an offline key? (Currently it was generated in nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 and has only been exposed to Damus and a pen-and-paper backup).
I’d love to gain the additional security but not have to rebuild the content and social graph that I’ve spent nearly 2 years building. But how?
Or as another route, could I use a new FROST multi/nsec along with an nsec-bunker type authorization tool, such that the new key is the master key behind my bostonwine nsec?
Not sure who to ask… nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 nostr:npub1mxrssnzg8y9zjr6a9g6xqwhxfa23xlvmftluakxqatsrp6ez9gjssu0htc and nostr:npub1u8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhs46turz, y’all were discussing on today’s nostr:npub1qdcakl75gd7wv0nqmmwrz09ddm5tzl7xj8lq2gclng2qzd8up5yqjpzclt or maybe nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s, or nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft - nsecbunker is your creation, right?
Hell, might as well #asknostr
I wrote a blog post about frost https://www.iroh.computer/blog/frost-threshold-signatures
For iroh, we use curve ed25519, while nostr is using secp265k1. So the linked code only works with ed25519 keys.
But other than that this transfers 1:1. You can take an existing key and split it into as many key shares as you want. So you can move to a multisig style approach while preserving your nostr identity.
You could take the existing code, replace https://crates.io/crates/frost-ed25519 with https://crates.io/crates/frost-secp256k1, and you would have a working co-signing setup for nostr keys.
Iroh dev here.
The core of iroh is p2p QUIC with dial by node id and very good NAT hole punching, so you almost always get direct connections.
We need a global mechanism to publish some information (a relay URL and optional direct addresses) for an ed25519 public key.
We have multiple mechanisms, one of them pkarr.
So far it works really, really well. Both speed and reliability is comparable to DNS, but we don’t have to run infrastructure. It is just nice in terms of operations even if you don’t care about p2p for ideological reasons.
See https://docs.rs/iroh-net/latest/iroh_net/discovery/index.html