What are the frost shards that promenade uses? Are they relays or dvm-like agents?
Discussion
Ah found in the promenade description, never mind
One thing missing in the promenade description is that signers connect directly to the coordinator. In theory one could use a different relay as a proxy, but connecting directly is more private and more efficient and allows coordinators to know which signers are online.
Currently events shared between coordinator and signers are not encrypted in any way.
So currently signers aren't really "multi-party", right? And the plan is that eventually independent parties will run publicly known signers and promenade will somehow choose among them?
What do you mean? They are multi-party.
Promenade is two things: a coordinator and the signers. There are currently 5 signers I think, ran by different people. The client (nstart) will select 3 of these at random to do a 2of3 scheme (I think ideally it would be a 3of4 or maybe 3of3 if we get very reliable signers). The client can in theory select any signers they want and any coordinator they want, but currently it's all hardcoded because we don't have anyone else interested (do you want to run a signer and be added to list, by the way?) and I don't know what would be the UX of giving people options.
nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk is working on a "manager" client companion to nstart that I think will give the user ways to configure these things. In the future (always in the future) we may have a more decentralized market of coordinators and signers and friend recommendations and stuff like that.
Oh, unrelated but also if you compromise your bunker currently you can delete it from the coordinator so the coordinator will just stop answering to requests for that specific bunker URL. Or you can redo the bunker setup process with the same signers and coordinator and your previous stuff will be deleted and overwritten. For this you need your main nsec.
Well I meant "hey are you running signers yourself for now?", but it's great to know those are different people - found the list on nstart source. Happy to run it too: nostr:npub1qaekjyulztkfmc3lu08pr57jvx0cdcrg9qx5gm55kltklaz233qs4c0kuu
The UX of giving people options could probably look like "Choose 3 of these 10 signers passing wot score threshold" with some defaults set. Signer owners should put their signature somewhere (nip89 event?) to enable that.
How do I ask coordinator to delete the bunker url?
How do you have a WoT threshold if you're just creating a Nostr account?
App either has hard-coded pubkeys of trusted owners, or trusted "wot root" pubkeys, or may infer some context from the place where user is signing up. I.e. if user signs up on npub.pro site then we'll use site admin as wot root (we already reuse their relays for new profile, and suggest new user to follow them).
Even if wot roots or owners are hard-coded I guess it's better then hardcoded signer pubkeys bcs new good signers can be discovered/suggested without recompiling the app.
Let me know your signer pubkey once you have one running, make sure to pass the --accept-relay flag to the signer.
I sent it, the signer pubkey is nostr:npub1qaekjyulztkfmc3lu08pr57jvx0cdcrg9qx5gm55kltklaz233qs4c0kuu