REX — Rialo Extended Execution
The part of Rialo that reaches outside the chain: WASM components running in a trusted execution environment, allowed to make HTTP and WebSocket calls, with their results settled on chain.
How it works
A normal blockchain program cannot call the outside world: every validator must reach the same result from the same inputs, and a web request is not deterministic. Rialo's answer is to move the non-deterministic part into an attested enclave. A component compiled to WASM runs inside a TEE, performs the network call, and the enclave's attestation is what the chain verifies — not the response itself.
A REX request is the standing subscription: a component, an interval, and a number of validators that must each independently perform the run. Every scheduled run is a duty, assigned to specific validators ahead of time. A validator that fails to produce its attestation on time records a missed duty, which is queryable — so the reliability of an off-chain feed is public rather than a matter of trust.
Inputs can be encrypted to the enclave with HPKE using the network's secret-sharing public key, so a request can carry an API credential without publishing it on chain.
On-chain components
- REX processor
- Qrac1eProcessor1111111111111111111111111111Account data decodes to
rex_processor· 13 B · owned by the native loader, so it is built into the runtime rather than deployed. - Secret-sharing key
- a41762c37902d5af2c711e8ae180d8df925a5b0e0bc4286874661191cd12e328Epoch 0, version 0. Hex-encoded, unlike the base58 keys used for accounts. This is the key inputs are encrypted to.
- Validators
- 4 in the set · view validators →