STEP 1 OF 3
NEXT: How to read a remote contract's state →
8 FIELDS · THIS ORDER · LOAD-BEARING
1. isStatic
2. sourceAddress
3. sourceRollupId
4. targetAddress
5. targetRollupId
6. value
7. callGas
8. data
DAPP DEVELOPERS
How to encode a call's content hash
Eight fields describe a cross-chain call, in this exact order.
Hash them together and one bytes32 identifies the call.
WHAT YOU'LL LEARN
- 01 · 8 FIELDS, FIXED ORDEREight fields describe a cross-chain call, in this exact order.
- 02 · ONE HASH OUTHash them together — one bytes32 identifies the call.
- 03 · ORDER IS LOAD-BEARINGReorder them and you get a different hash.
RUN IT YOURSELF · forge test --match-test test_matchesIndependentlyDerivedDigest -vv — from eez-demos/snippets, Foundry only.
Verified against eez-core-protocol @ 9735f53 — pre-mainnet; interfaces may move.