Add ability for owner to specify a Kepler orbit containing additional claims
wyc opened this issue · 0 comments
When adding additional claims, especially private claims, users do not necessarily want to pay gas costs or reveal a public tx. How could we specify an additional orbit to list query for a claims listing, perhaps protected using Kepler authn? This way, the user can add another claim without any public tx. However, this has the disadvantage of reducing the chain-anchored data integrity (content URL and Hash), and creates a dependency on the data storage as opposed to URL scheme agnosticism (right now, it can be https:// or kepler:// or anything the user wants that tzprofiles-sdk can interpret.
Perhaps this is a new field in the smart contract storage. Top level or metadata? Maybe a different type of claim in the list?
("kepler://<orbit-id>", "<orbit-id>", "KeplerOrbit")