You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Analogous to https://github.com/ChainSafe/Banshee/issues/47, but instead of the entire beacon state, we only need light client sync committee data and block roots. There, the blocker was in the lack of specific SSZ methods in ssz-rs; we don't need those methods, so the option of writing data retrieval and pre-processing in Rust is relevant again.
for the link that you posted, it still looks like it's using "mock data" where the script is generating data (primarily for private keys and validators). the script would also require calling to an exposed endpoint and retrieving the beacon state for a light client?
Analogous to https://github.com/ChainSafe/Banshee/issues/47, but instead of the entire beacon state, we only need light client sync committee data and block roots. There, the blocker was in the lack of specific SSZ methods in
ssz-rs
; we don't need those methods, so the option of writing data retrieval and pre-processing in Rust is relevant again.The potential shortcut could be by using https://github.com/polytope-labs/sync-committee-rs.
Scope:
The text was updated successfully, but these errors were encountered: