Built on the Rialo Reactive Transactions model

Triggers that execute themselves.

Today's chains are synchronous — nothing happens until a bot, cron job, or keeper pushes it. Rialo makes automation a native property of the chain. Move the slider. Cross the threshold. Watch the chain react — no bots, no keepers, no fragile glue code.

Interactive demo below
$3,180

Liquidation threshold: $3,000 · Target: restore CR ≥ 150%

Legacy Stack · Off-chain
Rialo · On-chain Native
Price Oracle
Off-chain data source
Keeper Bot
Waits · polls · can fail
Reactive Trigger
Registered on-chain
Reactive Engine
Native automation layer
Vault Contract
Deleverage executed
▲ Move the trigger slider or press “Fire Trigger” to begin
Execution Log
rialo-testnet
waiting for trigger…

Liquidations that execute themselves — before bad debt happens.

The old way is a tower of glue code

Every "automated" dApp today depends on off-chain bots that poll, sign, and push transactions. Rialo collapses that entire tower into one native layer.

Legacy Automation
Rialo Reactive
Trigger source
External cron / bot polling
On-chain reactive trigger
Who executes
Keeper bot (off-chain server)
The chain itself — natively
Failure modes
Bot down · API key leaked · RPC rate-limited
None new — inherits chain liveness
Trust assumption
You trust the operator’s infra
You trust the network
Latency to execution
Poll interval + bot + tx broadcast
Next block, deterministically
Cost model
Server + gas subsidies per action
One registration, then protocol-level

Zero keepers

Triggers live inside the chain. No third-party bot can sleep through your liquidation.

No extra trust

Automation inherits the network's own security — no operator key to leak or bribe.

Composable by default

Any contract can register triggers against any event — automation becomes a primitive.