From d45afab1688ccbab53487d2e12af5d954a09151f Mon Sep 17 00:00:00 2001 From: nolash Date: Fri, 21 Aug 2020 17:05:38 +0200 Subject: [PATCH] Restructure the registration mapping description --- spec/016_cic_token_platform_registration.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/spec/016_cic_token_platform_registration.md b/spec/016_cic_token_platform_registration.md index eb88d0f..be4c98a 100644 --- a/spec/016_cic_token_platform_registration.md +++ b/spec/016_cic_token_platform_registration.md @@ -19,10 +19,19 @@ A separate, more formal document will be written as a request for comment for de The `DecentralizedStorageResolver` contract facilitates multiplexing of data resource locations across web2 and web3 networks. It is a separately maintained project with its own documentation. Its utility here is to let an entity specify one or more locations where the metadata for the registration can be retrieved. -The `CICRegistration` contract announces the availability of metadata for a given token. In essence it is a simple chain of mappings: +The `CICRegistration` contract announces the availability of metadata for a given token. In essence it is a simple chain of mappings (names do not match contract properties): ``` -token_address -> token_announcer_address -> resolver_address -> resolver_type -> resolver_chain +{ + 'token_address': { + 'token_announcer_address': { + 'resolver_address':
, + 'resolver_type': , + 'resolver_chain': , + } + } +} + ``` The `resolver_type` is a sha256 hash of a custom resolver id. The only three recognized values at current time are: