mirror of
https://gitlab.com/pulsechaincom/erigon-pulse.git
synced 2025-01-10 13:01:21 +00:00
dab1ba44d0
https://github.com/ledgerwatch/erigon/issues/5884 has more context on this issue. we are trying to understand the encoding of the responses. from the Ethereum R&D discord, AgeManning said that the prefix is supposed to be a varint representing the length of the payload: https://developers.google.com/protocol-buffers/docs/encoding#varints. that works for the `&cltypes.MetadataV1{}` type, but not for `&cltypes.MetadataV2{}` or `&cltypes.LightClientFinalityUpdate{}`. |
||
---|---|---|
.. | ||
ssz_snappy | ||
packet.go |