search

LNP-BP / LNPBPs

LNP/BP standards for bitcoin layer 2 & 3 protocols
https://standards.lnp-bp.org
202 stars 39 forks source link

Support for asset name registries #75

Closed fedsten closed 3 years ago

fedsten commented 3 years ago

In the current schema structure there is a field Name for the asset, which however is not supposed to be unique. For a smoother user experience, it would be nice to have asset names that are unique and standardised across wallets, and for this purpose it would be useful to add support for asset name registries, similar to the one used by Blockstream for Liquid.

To implement this I see two possible ways: (i) add in the schema a field for a URL pointer to an asset registry, where a trusted registry maintainer maps asset IDs with unique names, or (ii) add in the schema a field where it can be inserted a signature of a registry maintainer that certifies the unique name of the asset.

Obviously, then it will be up to wallet providers to decide which registry services to support and how to show different assets that may have the same name in different registries. This new field does not necessarily need to substitute the already existing Name field, as that could still be used as a name to show in a wallet user interface in the case the issuer did not subscribed to any registry service.

dr-orlovsky commented 3 years ago

Summary: after the discussing during dev call we have reviewed the difference between adding asset-related information to the genesis vs adding them to the registry. Registries will be based on Bifrost servers and there might be multiple registries; registry data are not global and different registries may provide a different view on the same asset. Genesis-based data are global: the issuer commits to them and can't display two different genesis for different users/clients