Quickstarts
Why Only Proxies Reach the Cross-Chain Entry Points
ANYONE ELSE
eez.executeCrossChainCall()
EEZ MANAGER
?
A REAL PROXY
fallback → executeCrossChainCall
EEZ MANAGER
executes it
DAPP DEVELOPERS
How the guard makes sure only proxy calls reach execution
Anyone can try calling the manager’s entry point directly.
It reverts — UnauthorizedProxy() — so a call reaches execution by routing through a registered proxy instead.
WHAT YOU'LL LEARN
- 01 · ONLY A REAL PROXYAnyone can try calling the manager’s entry point directly.
- 02 · THE GUARDIt reverts — UnauthorizedProxy(). Only a real proxy gets through.
- 03 · ON BOTH PROXY ENTRY POINTSexecuteCrossChainCall and staticCrossChainCall both open with this check, so neither runs for a caller that isn't a registered proxy.
RUN IT YOURSELF · forge test --match-test test_directCallFromEoaReverts -vv — from eez-demos/snippets, Foundry only.
Verified against eez-core-protocol Git commit 9a1f815; interfaces may move.