Oddbean new post about | logout
 Here goes… 

https://github.com/pubkeychain/pkc-protocol 
 I’ve read a few times, but still not sure if I’ve digested the purpose. Is it mostly to help existing PKI be published/shared somewhere?

the specific problem I’m interested in is around establishing a global namespace e.g. so you could own the handle “nusa” and we could use that to find this nostr-account or a website or whatever else you’d want to point it to. does your protocol touch on a solution to that problem? 
 First, thank you 😊

It touches on both, depending on the service you plug it into. I’ll try to describe what I mean. 

The handle or global namespace is the satoshi name, for instance the satoshi with ord number 1953186218210489 has a name of ‘aaaaaaaaaaa’.

For nostr, you could save the sat name to your profile and after anyone plugging that satoshi name into search could retrieve all history of all pubkeys contained in the inscriptions of that satoshi and it would all be your content.   There are also ways to make sure your pubkeys aren’t appropriated by others.

I can also imagine a service that would handle websites. Dns basically does cert and ip lookup. If you extend the inscription and provide the ip address beside the pubkey, which can be used to verify that the server holds the private key, I can imagine a legit request can be made to get the website data. 

Does that make sense? 
 Ah, I think I get it better now. So you’re relying on the satoshi names from Ordinals? There’s a bunch to like about that naming system, but I also have concerns with the fact that it’s going to be a long time before we can get short names which presumably would entice a lot of people to participate/promote such a system early-on. The proposal I’ve read that attempts to mitigate this problem reduces the self-sovereignty of ownership.

Do you agree that the sat names from Ordinals have not gotten substantial adoption? Are you assuming that will change soon for some reason? 
 My main focus has been on providing a self sovereign failsafe for lost nostr keys, and my reason for using the ord name instead or number was because it’s shorter. Readability of handles didn’t matter to me as much. I consider it more in the sense of a ‘telephone number’ made up with letters, for which you could maintain a personal ‘phonebook’ and just name things what you want for your reference, but you never need to look at the ‘phone number’ to get to the person or website you want. 

I see the value in naming though and in vanity names. I don’t expect the ord names to become suddenly popular and the availability of names people actually want is a real problem. But I absolutely don’t want to introduce a third party authority into it. That’s a hard pass. 
 agreed on 3rd party authorities being a hard pass. the only way such a thing could work would be if it was neutral 
 In the end it’s possible that the names don’t even matter. For the lookup to work you need a static identifier to which you can associate new ips and new certs. Maybe we can live without the global naming, since we use search engines, social media posts, adds, and qr codes to get where we want to go. 
 Wow, I was spectacularly unclear 🙈 I meant to say that the static identifier can as well be a satoshi name even if it’s a mostly random mix of letters and the websites and users can then name themselves whatever they want.