We need a rough sketch of how we're doing beacon chain light protocol access. I suggest the following.
A new sub protocol for the portal network. I'll call this the "Beacon Chain Light Client" network. This network will provide storage and retrieval of LightClientUpdate objects back to some reasonable historical time horizon. The network will also provide gossip of the latest LightClientUpdate objects as they enter the network (provided by a bridge node).
This will need to be fleshed out into a full spec document. Would anyone like to volunteer?
I started working on draft specs for the Beacon Chain Light Client network. I will push a PR for review when I have something and then we can iterate on it.
We need a rough sketch of how we're doing beacon chain light protocol access. I suggest the following.
A new sub protocol for the portal network. I'll call this the "Beacon Chain Light Client" network. This network will provide storage and retrieval of
LightClientUpdate
objects back to some reasonable historical time horizon. The network will also provide gossip of the latestLightClientUpdate
objects as they enter the network (provided by a bridge node).This will need to be fleshed out into a full spec document. Would anyone like to volunteer?