
Exploring Web3 & AI agents | Contributor @RialoHQ
Mars
Joined June 2019
- Tweets5.2K
- Following533
- Followers1.1K
- Likes9.5K
Prediction market settlement still depends on a keeper bot noticing the oracle result and sending a tx.
Keeper dies or gets outbid on gas and funds just sit locked.
@RialoHQ being event driven means the event itself kicks off settlement, no bot to babysit.
Rialo founders left mysten lab to fix the part L1s still can’t do.
Talk to the outside world.
Today that means a cron on some vps and we call the app decentralized.
@RialoHQ puts web calls and event triggers in the protocol. one less box to get owned
🤖 Made with AI
A fund running strategy on a public chain is basically live streaming it.
Every tx and counterparty in the log.
@RialoHQ has confidential execution built into the infrastructure.
positions stay hidden and state still verifies. no desk touches a chain that shows its book live.
🤖 Made with AI
Been reading the scale writeup from @RialoHQ.
Test part is the boring one.
Agent misses the deadline, native timer refunds the escrow, no off-chain script involved.
On most stacks that refund is a cron job on some box with a hot key nobody audits.
Most onchain credit score setups come down to one api key in a relayer's env file.
Thats the whole trust model.
On @RialoHQ the contract just fetches the fico data directly, nothing sitting in between to get popped.
People say just use chainlink like the oracle hop is free.
iIt's still a relay, a feed config and a trust boundary you now have to threat model.
@RialoHQ lets contracts make the http call directly so the request stays inside the tx flow.
Most L1 push data and scheduling out to oracles, keepers and relayers.
Then the audit covers the contract and nobody looks at the hot key on the relayer box.
@RialoHQ moved all that into the chain itself!
Rialo using account abstraction, signup is just email or google login, no seed phrase step.
Keys are still non-custodial, you just never touch that part yourself.
Decentralization killing onboarding was always a choice not a requirement.
Rialo escrows the payment when you hire an agent to do a task.
If it misses the deadline you get your money back automatically.
Theres also a separate judge agent checking the actual output before the payout clears.
People say just use a bridge like it's a function call.
But it's a relayer watching one chain, a multisig and a contract on the other side trusting whatever they sign.
Ronin needed 5 of 9 sigs to move funds, attackers got 5, $600M gone.
@RialoHQ building this into the chain instead of around it is the direction i like!
Keeper bots are just a script watching a price feed.
One bad rpc call or it gets outbid and tx doesn't fire.
@RialoHQ has this baked into the chain itself.
No need some separate bot running 24/7 somewhere just to poll state and pray it wins the race.
People say decentralization means no single point of failure.
Mostly true for consensus but check the RPC provider, the bridge, the sequencer still centralized in most chains.
One of those goes down and it doesn't matter how decentralized your validators are.
@RialoHQ is building around this exact gap!
L2s made tx cheaper but we are still trusting the same sequencer, same bridge, same fraud window as before.
That's not a fix, that's just paint on the crack.
@RialoHQ isn't stacking another rollup but questioning why we keep patching instead of rebuilding.
The cool thing about @RialoHQ is identity checks dont happen in the open.
Your info gets encrypted, checked privately and only a yes or no ever touches the chain.
Actual data never shows up onchain just the result.
The real problem was never "reading the internet" but that a smart contract can't trust what it reads.
Since chain state has to be deterministic and verifiable by every node.
@RialoHQ solves that at the runtime level!
Contracts query external data and the network verifies it before it becomes state.
No oracle contract acting as a middleman you have to separately trust.
Rialo retroactive points have been distributed!
If you contributed to @RialoHQ Discord community or GitHub, you can now claim your points.
• sign up: playground.rialo.io/
• visit your profile
• connect your discord & GitHub
• claim
That’s it.
Most chains give you finality in seconds, fine for a swap but useless for a game where you gotta hit or dodge in real time.
@RialoHQ does 50ms so the chain keeps up with your reflexes instead of your reflexes waiting on the chain.
















