Registry support for chain and watcher IPLD codecs #26

New Issue

i-norden · 2022-08-31T16:45:40Z

i-norden commented

2022-08-31 16:45:40 +00:00

From Ashwin:

Create a "chain registry".

Register chain record, it is mapped to a bunch of metadata (name, IPLD type schemas/codecs, etc)

Chain attributes:

Name
List of IPLD types and their codec or schemas
Fill in the rest....

This is a good example of where we need dynamic indexes, chain record is single type of record with unique attributes.

Types of records:

Service provider
Watcher
Chain

Two concerns:

Need level of expressibility to be able to index the different types of records (https://github.com/cerc-io/laconicd/issues/27)
Need to support different codecs at the base layer of the chain (not all watcher records will be stored as dag-json) (not as much a priority)

From Ashwin: Create a "chain registry". Register chain record, it is mapped to a bunch of metadata (name, IPLD type schemas/codecs, etc) Chain attributes: * Name * List of IPLD types and their codec or schemas * Fill in the rest.... This is a good example of where we need dynamic indexes, chain record is single type of record with unique attributes. Types of records: * Service provider * Watcher * Chain Two concerns: * Need level of expressibility to be able to index the different types of records (https://github.com/cerc-io/laconicd/issues/27) * Need to support different codecs at the base layer of the chain (not all watcher records will be stored as dag-json) (not as much a priority)

i-norden commented

2022-09-16 17:43:13 +00:00

New type of records related to #27:

Schema record (types content record's attributes)
Content record (e.g. Service provider registration, watcher registration, chain registration records mentioned above)

New type of records related to #27: * Schema record (types content record's attributes) * Content record (e.g. Service provider registration, watcher registration, chain registration records mentioned above)

i-norden commented

2022-09-16 17:52:37 +00:00

Next step:

Determine service provider registration record fields and attributes (attributes should stay the same for all service provider registrations as all registrations should use the same form as set by the laconicd chain).
Determine watcher registration record fields and attributes (attributes may vary/watcher registrations may have different types; until #27 we can work on supporting a single well defined record type).
Determine chain registration record fields and attributes (may also need to be a dynamic type- further thought required).

Next step: - Determine service provider registration record fields and attributes (attributes should stay the same for all service provider registrations as all registrations should use the same form as set by the laconicd chain). - Determine watcher registration record fields and attributes (attributes may vary/watcher registrations may have different types; until #27 we can work on supporting a single well defined record type). - Determine chain registration record fields and attributes (may also need to be a dynamic type- further thought required).

i-norden commented

2023-02-28 14:49:44 +00:00

Types are supported in https://github.com/cerc-io/laconicd/issues/51

We will need to revisit this once we move to a system to support registrying arbitrary types.

Types are supported in https://github.com/cerc-io/laconicd/issues/51 We will need to revisit this once we move to a system to support registrying arbitrary types.

Sign in to join this conversation.