← Quickstarts
Why the Manager Only Accepts Proxy Calls
PRE-MAINNET
STEP 1 OF 3
NEXT: How to encode a call's content hash →
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 · NO WAY PAST ITBoth proxy entry points open with this check, so no proxy-routed call reaches execution without it.

RUN IT YOURSELF · forge test --match-test test_directCallFromEoaReverts -vv — from eez-demos/snippets, Foundry only.

Verified against eez-core-protocol @ 9735f53 — pre-mainnet; interfaces may move.