Skip to content

op-batcher: use one BatchAuthenticator reader, bound and code-checked once at startup #503

Description

@philippecamacho

One BatchAuthenticator reader, bound once. registerBatcher, resolveTEEVerifierAddress, and isBatcherActive each construct their own binding from the same address, and isBatcherActive re-does a CodeAt probe per publish tick plus fetches the SystemConfig address via BatchAuthenticator.SystemConfig() even though the batcher already has l.RollupConfig.L1SystemConfigAddress. One reader object, code-checked once at startup, cuts the gate to at most 2 L1 calls per tick and makes it unit-testable with the mock-backend pattern already used in espresso_fallback_gate_test.go.

Original discussion: #459 (comment)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions