Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Secondary read failures when doing lookups against eigenda-proxy #65

Open
ethenotethan opened this issue Feb 13, 2025 · 0 comments
Open

Comments

@ethenotethan
Copy link
Collaborator

ethenotethan commented 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 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.

@ethenotethan ethenotethan changed the title Secondary storage incompatibility with EigenDA Proxy Secondary read failures when doing lookups against eigenda-proxy Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant