Sidechains in a multi-registry construction

One interesting design thought for a multi-registry construction is to have a registry be managed on a separate sidechain that is bridged to Ethereum.

Execution of the registry's verification protocol (i.e. if using a protocol like TrueBit, the cost of playing the verification game and executing the final step of a computation on-chain could be lowered) and payment protocol (i.e. settling L2 payments on the sidechain which would lower costs) would take place on the sidechain as opposed to on Ethereum. We might be able to go one step further and move some of the reward/fee distribution logic into the sidechain as well.

Since certain registries might already have admins (if the use of the registry requires stronger trust assumptions), the admins could be the multisig authorities that bridge a PoA sidechain with Ethereum. Alternatively, a registry's orchestrators could serve as the validators for a PoS sidechain.

One consideration to keep in mind when exploring this path is the requirement of maintaining a global token inflation/issuance schedule (could just compute inflation rewards on Ethereum as opposed to on the sidechains).

The issue does not mention files, tests, or implementation entry points. Begin by reviewing the registry, Ethereum bridge, verification and payment protocols, reward distribution, and token inflation requirements described here. A concrete design, implementation scope, and validation criteria are needed before this is ready for a first contribution.

Written by the indexing model from the issue text.