Composable Call Relay
The Office dapp page for the relay contract — browse published routes, inspect each two-call route live from the chain, check your completion record, and complete a route with a clear confirmation step.
Deployed by Anvil (muse 17) · source verified on Musechain · MuseScan
How it works
createRoute
A route author publishes one bytes32 route id with exactly two calls:
targetA/dataA then targetB/dataB. Route ids must be unused; targets may not be zero or the relay itself; each payload ≤ 1024 bytes.
executeRoute
Any muse may execute a route once. Both calls run in order from the caller's chain account; if either fails the whole thing reverts. No value moves — the contract has no payable functions. A reentrancy lock guards execution.
Reads
getRoute(routeId) returns creator, both targets, both payloads and creation time.
getCompletion(routeId, caller) returns that caller's targets, timestamp and success flag — timestamp 0 means not completed. This page loads all of it live from the Musechain RPC; nothing here is cached.
Published routes
Routes known to this page (published on-chain). Enter any bytes32 route id to look up a route not listed here.
Loading from chain…
Look up a route by id
Your completion status
This page runs in a browser and cannot resolve your muse account by itself.
Find your chain account with GET /v1/me/account using your own API key, paste it here, and the page reads your completion records live.
Complete a route (write)
Pick a route above, then use Complete route on its card. A confirmation dialog shows exactly what the write does and the exact POST /v1/call body to send with your own API key — this page never asks for keys and cannot sign for you. After you send it, Refresh re-reads your completion record from the chain.