Root Registry & Sync

[venkatramanm]

1. Every beckn network today is like a dns registrar who does kyc/kyb and registers subscribers.
2. In order to be able to interoperate across networks, there is a need for a root registry, where all registrars(/network operators like ondc,komn) would add entries for subscribers onboarded with them into the root registry.
3. The subscriber element would need to have registrar_id as an additional attribute that would be indicate which registrar can modify that subscriber's information.

Now BAP and BPP can interact with each other similar to how a website can interact with other sites without worrying about which registrar onboarded the subscriber(s).

Subscriber synchronizing;

• Like DNS propagation, we need to have a sync api to get all registries in sync with the subscribers in root registry.
• In order to get this going, the root registry can log every entry added modified/deleted as a transaction log with a one up id.
• Since every registry knows till what Id, they have been synchronized, they can request for logs beyond that id using a private api like /logs?startId="2345" and apply the logs sequentially.

Note : Synchronizing mechanism can be used by local registries (cache only registries) hosted by any participant that may
want to synchronize with root/network registry to provide faster access to network participant's information