-
Notifications
You must be signed in to change notification settings - Fork 25
PetNames
Zooko's triangle says we can have at most two of three properties we want for names of participants in a network protocol:
- Human-meaningful: Meaningful and memorable (low-entropy) names are provided to the users.
- Secure: The amount of damage a malicious entity can inflict on the system should be as low as possible.
- Decentralized: Names correctly resolve to their respective entities without the use of a central authority or service.
Though it may not be possible for any single namespace to have all three properties, petname systems do embody all three properties.
Keys lie at the heart of the security properties of the petname system. A key is a globally unique, unforgeable designator of some specific entity.
Nicknames can be used to assist in discovery of keys, and for help in selecting a petname. Nicknames are chosen by the owners of keys in hopes of creating a distinctive, if not unique, mapping from the memorable nickname to the key.
Petnames are our private bidirectional references to keys. There are many dogs named Rover, but for the owner of a dog with the petname Rover, there is one specific Rover to whom the name refers.
- [contact] is on [platform] - anti-pattern? · Issue #89 · dckc/madmode-blog
- does directory.rho implement the PetNames ocap pattern? · Issue #4 · rchain-community/rho-bot
- 2005: Petname Tool: Enabling web site recognition using the existing SSL infrastructure by Tyler Close
- 2005: Petname Systems by Marc Stiegler
- PetName Markup Language
- 2000: Petnames and Forgery among partially trusted participants in E in a Walnut