Using IBC for verfiable snapshoting

[Vishwas1]

Hi All,

We have been working on building public and permission-less network for managing digital identity and access rights. This network will acts as Verifiable Data registry - decentralized storage for DIDs and Schemas.

One of the concern we came across during a discussion with few govt. bodies was, govts or orgs may not be comfortable putting DIDs of their users on the public network with the fear of leaking any data even though it an identifier containing public keys. They might want to keep DIDs on zones within their jurisdictions.
For example,

• Govt. of India may want to keep citizens DIDs in Mumbai's zone only and do not want the world to know about that.
• Company A might want to keep their employee data with Company A's network and would only share with Company B if or when required, say for example, if Company A's employee goes to work for Company B in federated setting.

The public permission-less blockchain does not fits on this scenario however, the public chains are expected to be better secured than private chains since, public chains will have more number of nodes as compared to private ones (theoretically).

With this context, I was wondering what if these orgs can fork our node's code base and run their own network (something like zones in cosmos) and keep their data private of their network. But, these zones also send periodic snapshots to our network via IBC - obtaining security from bigger network. These snapshots can be cryptographically verified any point of time and does not contain actual data.

Similar concept can be found in Polygon's whitepaper (https://github.com/maticnetwork/whitepaper#consensus-con) where they talked about "Checkpointing" for obtaining security from Ethereum main network.

Does this make sense?