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
Some EigenDA certificate fields are ignored when posting to the sequencer inbox. This results in having to embed custom translation to go from the ABI encoded cert type known to the inbox to the certificate type known to eigenda-proxy (cert' --> cert).
Currently, there's a bug where this translation fails to include the fee field - resulting in a cert with one missing field or cert''. This affects secondary storage lookups since they entry key is computed as H(cert).
So in essence:
Proxy --cert--> batch poster --cert' --> inbox
And the nodes deriving:
inbox --cert`--> preprocess --> cert'' --> proxy
Where derivation should be:
inbox --cert`--> preprocess --> cert --> proxy
The fix is pretty trivial, but we should establish some tests to ensure this never happens again.
The text was updated successfully, but these errors were encountered:
ethenotethan
changed the title
Secondary storage incompatibility with EigenDA Proxy
Secondary read failures when doing lookups against eigenda-proxy
Feb 13, 2025
Some EigenDA certificate fields are ignored when posting to the sequencer inbox. This results in having to embed custom translation to go from the ABI encoded cert type known to the inbox to the certificate type known to eigenda-proxy
(cert' --> cert)
.Currently, there's a bug where this translation fails to include the
fee
field - resulting in a cert with one missing field orcert''
. This affects secondary storage lookups since they entry key is computed asH(cert)
.So in essence:
And the nodes deriving:
Where derivation should be:
The fix is pretty trivial, but we should establish some tests to ensure this never happens again.
The text was updated successfully, but these errors were encountered: