You hired an AI agent, gave it keys to everything and now you're just hoping.
@RialoHQ's Latch tells the agent exactly what it can do, for how long and cuts it off when done.
took long enough tbh!
This is huge!
What started as an internal tool for managing agents, now it will enable you & everyone unleash agents securely!
Sign up 👉 https://t.co/P12bb0WAq7
we've spent years building complex middleware to bridge web2 data to web3 when we could've just integrated TLS verification into the chain itself.
@RialoHQ does this. contracts read the web directly, no oracle markup, no extra trust assumptions.
Relying on a piece of paper for full tx auth is a big problem.
Seed phrases are just a massive single point of failure.
@RialoHQ gets it right by dropping them for smart accounts.
Shifting auth to email with 2FA removes the brittle key dependency.
Nobody is going to run a business on a public ledger where everyone can track
their txs and balances.
@RialoHQ makes a lot of sense here because they keep the data private but still let you prove the math works.
That’s very basic opsec but so underrated.
High TPS benchmarks are a total lie. They use simple, parallel transfers with zero state contention.
But in the real world, dapps constantly fight over the same state (like AMM pools).
@RialoHQ tackles this execution bottleneck instead of chasing empty metrics.
Checking out the @RialoHQ thread. @RialoHQ handle ZK proofs using native RISC-V.
no need to write messy custom code to translate other languages, less
code equals fewer bugs.
and a reminder that ZK won't fix bad inputs. verified garbage is still garbage
Multisigs are just dumb state machines.
they verify the sig and blindly fire the
tx.
@RialoHQ fixing this by enforcing 2FA on fat withdrawals is a big opsec win.
Isolating the api keys inside a TEE so they don't leak.
Our sincerest sympathies go out to the affected victims, but onchain treasuries have a structural problem.
The multisig that secures them can verify signatures and check thresholds. It cannot assess risk, notify anyone, or delay execution.
The Drift hack exploited this gap. $285M, gone.
many onchain lending apps just leak borrower PII to state.
@RialoHQ avoids that mess with REX.
it processes encrypted reqs in a sandbox, wipes memory and only drops the proof onchain.
zero cleartext logs and super clean
infra.
standard multisigs are blind. if sigs match, the tx ships.
@RialoHQ storing encrypted API keys in native private compute to trigger MFA is a super clean infra design.
killing the dependency on offchain keeper bots makes the whole
opsec model so much tighter.
@RialoHQ Gauss paper is titled "It’s Not a Lie if You Don’t Get Caught."
They split the log so execution only sees sanitized txs, hiding dirty consensus noise.
This lets them push zero-downtime upgrades without breaking state. Clean infra.