@RialoHQ 's Latch flips the agent security model entirely. Possession of a key is no longer the proxy for authority. You bind the credential once into REX hardware-enforced, encrypted at rest, never exfiltrated. What the agent holds is a derived scoped token.
https://t.co/TOaYXHac0c Open, no waitlist. Bind a Secret once. Fan out multiple Latches from one credential each with its own upstream URL and filter pipeline. Stack method, endpoint, rate limit, payload, IP, response filters. First deny wins. Your policy logic runs inside REX.
Every Latch policy execution is a REX computation: encrypted inputs routed into attested hardware, logic runs blind to the raw data, signed attestation comes out. Subzero just shipped the first publicly accessible proof that REX works in production.
Happy new week,
Brief chat about @RialoHQ extended execution, they said privacy was a feature. Rialo made it a separate execution domain. Inputs route encrypted into a hardware-enforced compute boundary consensus only sees a signed attestation, never the raw computation.
Forget oracles. Rialo's identity, privacy and compliance is protocol-native. A compliant transfer flows: transaction triggers โREX encrypts and computesโ sanctions list checked on-chain in real timeโ settles only if clean. Policy enforcement fused into finality itself.
While everyone watches the devnet, Rialo quietly shipped Gauss a reconfiguration engine that upgrades live fault-tolerant systems with near-zero downtime and minimal coordination overhead. Most chains skip this until a hard fork burns them.
@RialoHQ claims no oracles needed since contracts call HTTPS directly inside the protocol. But consensus requires determinism, and HTTP GET is not determi nistic two validators can get different responses to the same call. The validator set just became the oracle committee.