You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the only way a user can get an object is through their wallet ("pet names") and the wallet does support naming hubs ("edge names").
Given an object, we need to know the name for it in this user's wallet. E.g. "RUN issuer" and "BLD Issuer"
Design
The lookup strategy is going to be look at my local pet names and if it's not there look at the naming hub. There is a graph of naming hubs, where the root is your local pet names. The resolution of any name is a path through the graph so it's an array where the first element is your local pet namer.
Has to be more constrained than an arbitrary graph.
Open questions:
How to represent it in the wallet properly
How to use it in the wallet
Where is the paper for naming hubs?
The text was updated successfully, but these errors were encountered:
Tartuffo
changed the title
Naming hub: interface to look up an object and get a (set of) name(s)
Naming hub: interface to look up an Issuer object and get a (set of) name(s)
Apr 13, 2022
Problem to be solved
Currently the only way a user can get an object is through their wallet ("pet names") and the wallet does support naming hubs ("edge names").
Given an object, we need to know the name for it in this user's wallet. E.g. "RUN issuer" and "BLD Issuer"
Design
The lookup strategy is going to be look at my local pet names and if it's not there look at the naming hub. There is a graph of naming hubs, where the root is your local pet names. The resolution of any name is a path through the graph so it's an array where the first element is your local pet namer.
Has to be more constrained than an arbitrary graph.
Open questions:
The text was updated successfully, but these errors were encountered: