@eez:target
The remote contract a cross-chain proxy stands in for: the reverse of @eez:proxy. Fails if the address is not a registered proxy on that chain.
On-chain (@eez:target!): Reads the registry of the chain the assertion runs on only, and an address that is not a proxy resolves to the zero address instead of failing.
⚗️ Experimental — available at next.evmcrispr.com.
Returns: address
Syntax
Section titled “Syntax”@eez:target(chain proxy)Arguments
Section titled “Arguments”| Name | Type | Description |
|---|---|---|
chain | chain | Chain the proxy lives on (gnosisChiado, chiadoX) |
proxy | address | Cross-chain proxy address on that chain |
Examples
Section titled “Examples”# Which rollup contract does this L1 proxy stand in for?switch gnosisChiadoprint @eez:target(gnosisChiado 0xD79015E2d143a8770dD5eF15A70F2F24232259c0)On-chain face (@eez:target!)
Section titled “On-chain face (@eez:target!)”authorizedProxies(proxy) on the registry, keeping the original address (word 1 of the triple). Two differences from the off-chain face:
- An assertion runs on one chain, so only that chain's registry can be read:
@eez:target!(chiadoX …)from L1 refuses at composition time. - The registry answers a non-proxy with zeroes, so an address that is not a proxy resolves to the zero address instead of failing.
assert @eez:target!(gnosisChiado $x) == $expectedstill fails for it; forcing a revert would take a contrivedcondonto a failing param.