# EEZ Protocol Documents

Specifications for the EEZ core protocol contracts.

- [EEZ walkthrough](/eez-walkthrough): Follow one call through preparation, proof verification and local execution, then tables, hashes, rollback, ETH accounting and system authority.
- [Build with AI](/build-with-ai): Give your coding agent the EEZ protocol docs: install the EEZ Docs skill, or read any page as Markdown.
- [Core Protocol Specification](/core-protocol-spec): How the EEZ contracts post, verify and execute cross-chain entries: data model, core functions, call and rolling hashes, entry lifecycle, invariants.
- [Execution Entry Specification](/execution-entry-spec): How to build execution entries for L1 (postAndVerifyBatch) and L2 (loadExecutionTable / executeIncomingCrossChainCall).
- [Static Entry Specification](/static-entry): Read-only cross-chain calls (STATICCALLs) and the resolution of reverting mutable reentrant calls: routing, position keys, resolution and root pins.
- [Multi-Prover Specification](/multi-prover-spec): EEZ verifies batches with multiple proof systems. Each rollup's manager defines its accepted verifiers, verification keys and threshold.
- [Events and execution reconstruction](/events): Event signatures, ordering, rollback behavior and reconstruction from committed receipts and execution inputs, for the current contracts.
- [Call-pattern support and current limits](/call-pattern-limits): Which call patterns the current tables support, and where CALL, STATICCALL and revert traces lack a faithful table encoding or exceed retry budgets.
- [Caveats](/caveats): Caveats of the current contracts: calling through cross-chain proxies, delivery and execution semantics, deployment and trust assumptions, edge cases.
- [Integration boundaries](/integration-boundaries): Support limits and external obligations outside the contracts: builder and prover, L2 funding, deployment and proof domains, event consumers.
- [Standardized Message Format](/blobs/blob-format-spec): A binary format for publishing rollup activity as one stream of messages: operations, cross-rollup calls, results, reverts and transaction boundaries.
- [A Compact Byte Encoding for 256-bit Integers](/blobs/u256-compressed-codec): A self-describing, byte-oriented variable-length codec for any 256-bit EVM word, with a literal form and a scientific (mantissa × base^exp) form.
- [Future Optimizations](/blobs/future-optimizations): Deferred size optimizations for the blob message format: compressed rollup ids, compressed u256 values and dense blob packing.