Learn how EEZ
actually works
EEZ lets a contract call another rollup and use the answer in the same transaction — no callback, no timeout, no retry.
[ FIRST TIME HERE? THREE STEPS, IN THIS ORDER ]
01How to read another rollup's state from your contract
DAPP DEVSLearn how the answer is written down before your transaction runs, instead of being fetched while you wait.
02How to use another chain's answer in the same transaction
THE DIFFERENTIATORLearn how the value that comes back decides what the rest of your transaction does — and why that removes the callback, the timeout and the retry you would otherwise have to write.
03Why msg.sender isn't your contract on the other side
BEFORE YOU BUILDLearn why every onlyOwner, allowlist and approve on the far side keys to a proxy address instead of your contract — and why nothing reverts when it does.
Start here — the same three steps with the commands to run them locally, plus reading orders for rollup operators and protocol researchers.
[ DAPP DEVELOPERS — ALL WALKTHROUGHS, TRACK ORDER ]
01How to get your contract's address on another rollup
Learn how to read it, or deploy it.
02How to call a contract on another rollup
Learn how to encode it like any normal call and send it to the proxy.
03How to handle msg.sender across chains
Learn how to whitelist the proxy instead of the address you expected.
04How to check an address is a real proxy
Learn how to read the on-chain registry instead of guessing.
05How the guard makes sure only proxy calls reach execution
Learn how UnauthorizedProxy() stops any call that isn't proxy-routed.
06How to encode a call's content hash
Learn how to hash eight fields in the one order that works.
07How to read a remote contract's state
Learn why balance and code size answer about the proxy — a real number about the wrong contract, with no revert.
[ ROLLUP OPERATORS ]
01How to run the whole stack locally
Learn how to bring up the node, proof-signer and the L1 in a disposable network.
02How to deploy the protocol
Learn what lands on L1 and L2, and in what order, once the network is up.
03How to run against a real testnet
Learn what changes when the L1 underneath you is Chiado rather than a disposable devnet.
04How to send and test a cross-chain call
Learn how to drive traffic through the stack you just brought up, and how to tell that it worked.
[ PROTOCOL RESEARCHERS ]
01How the four components divide the work
Learn how sequencer, composer, proof-signer and deriver each fit.
02How L1 stays the source of truth
Learn why the L2 block is added immediately and rolled back if L1 never confirms it.
03How the composer attests a batch
Learn what is actually checked before a batch is accepted, and by whom.
04How the deriver rebuilds L2 from L1
Learn how the whole chain is reconstructed from L1 data alone.
05How the address is derived
Learn how two values become a salt and a CREATE2 address.
06The rolling hash
Learn how one bytes32 commits to a whole execution tree — and why no call index is folded in.