Quickstarts
Who Answered?
NEXT WALKTHROUGH: Two Gotchas Before You Build →
STEP 1 OF 3
ALL QUICKSTARTS →
L1 · YOUR CONTRACT
CounterAndProxy
L1 · TARGET'S PROXY
Counter proxy
L1 · MANAGER
EEZ
THE PROXY REPRESENTS · L2 TARGET
Counter · increment()
CALLER
CounterAndProxy on L1
TARGET
Counter on L2
CALL DATA
increment()
VALUE
0
Call inputs → proxyEntryHash
The entry stores this call's hash. success and returnData are separate fields.
DAPP DEVELOPERS

Who Answered?

CounterAndProxy calls Counter's proxy on L1. How does EEZ find the stored answer that belongs to this call?

Follow the call hash: compute it, compare it with an entry, then read success and returnData. The composer prepares the entry before your call; locally, the scenario script does that work.

WHAT YOU'LL LEARN
  • 01 · COMPUTE THE CALL HASHproxyEntryHash identifies the cross-chain request, using its call inputs.
  • 02 · FIND THE MATCHING ENTRYEEZ compares the current call's hash with the stored proxyEntryHash.
  • 03 · READ THE RESULTThe matched entry holds success and returnData: true and an encoded 1 in this example.

Verified against eez-core-protocol Git commit 9a1f815; interfaces may move.

UP NEXTTwo Gotchas Before You Build