REACTORTürkçe

34 facts

Reactive transactions

34 facts about reactive transactions from 5 Rialo sources. Each one is the explanation Reactor shows after a question, followed by the exact line it rests on.

Test yourself on this topic in Atlas

Reactive Transactions: A Model for Native Automation on Rialo

A predicate is the onchain condition; when it becomes true, the transaction tied to it is eligible to run without anyone submitting it.

“A predicate is a logical expression that determines the conditions under which a transaction is eligible for execution.”

Rialo checks affected predicates at the end of each block's execution, deterministically, so every validator reaches the same result.

“At the end of a block's execution, Rialo evaluates all predicates whose dependencies may have changed. The evaluation is deterministic, meaning every validator arrives at the same conclusions.”

Dependency ordering decides whether the triggered transaction lands in the same block or a subsequent one, and consensus guarantees it executes.

“The triggered transaction runs either within the same block or in the subsequent blocks, depending on dependency ordering. The consensus protocol guarantees its execution.”

No external watcher is involved: the validators themselves hold the predicate and wait for it to become true.

“The key distinction is that all waiting happens inside the validator process itself. A reactive workflow on Rialo does not rely on an external system watching for a condition to change.”

A conditional transaction can spawn more conditional transactions, which is how workflows chain across many blocks and react to intermediate results.

“A conditional transaction can also create additional conditional transactions, enabling workflows that span many blocks, react to intermediate results”

Because workflows suspend and resume on conditions, the post says they can run for hours or even days without an external system progressing them.

“continue operating for hours or even days if necessary.”

The post treats reactive and conditional transactions as the same thing: execution based on predefined conditions, or predicates.

“Reactive transactions, also known as conditional transactions, execute based on predefined conditions or predicates.”

Predicates can read validator attested oracle data that reflects real-time external signals, so outside prices and events can drive reactive logic.

“Validator-attested oracle data that reflects real-time external signals”

Validator attested API calls bring external signals straight into reactive onchain logic, the basis of what the post calls hybrid onchain and offchain compute.

“Rialo supports validator-attested API calls, allowing workflows to incorporate external signals directly into reactive onchain logic.”

The post calls fully autonomous perpetual exchanges an example of autonomous finance.

“With reactive execution, perpetual exchanges become fully autonomous. Market logic updates itself, reacts to new conditions, and maintains stability without offchain intervention. This is an example of what we call "autonomous finance" at Rialo.”

Perp markets today lean on centralized or semi-centralized keepers; reactive execution lets them run without those keeper protocols.

“Traditionally, these functions depend on centralized or semi-centralized keepers.”

RWA systems need constant upkeep like coupons, NAV updates, redemptions and default checks; reactive execution models these onchain.

“Coupon payments, NAV (Net Asset Value) updates, redemption flows, and default checks all depend on processes that historically run offchain.”

DCA orders, periodic funding updates and vesting unlocks run at predictable intervals, so the post files them under time-based workflows.

“Time-based workflows: Scheduled DCA (Dollar Cost Averaging) orders, periodic funding updates, vesting unlocks, and other operations that must run at predictable intervals”

The post's pipeline example chains a sale, a purchase and a vault deposit into a single reactive workflow instead of offchain coordinated steps.

“Sequences such as selling asset A, buying asset B, and depositing the result into a vault, all encoded as a single reactive workflow rather than as separate offchain-coordinated steps.”

Each middleware layer extracts value and distorts incentives; reactive transactions fold them into the chain's own execution environment.

“Automation systems, indexers, schedulers, and keepers each extract value and create misalignment. Reactive transactions collapse these layers into the execution environment itself.”

The post says the opposite: the native pipeline guarantees consistent execution even under heavy network congestion.

“It prevents race conditions, reduces reliance on bots, and guarantees consistent execution even under heavy network congestion.”

The pipeline is run by all validators as part of native execution, with no external infrastructure or automation services.

“This pipeline is executed by all validators and happens as part of the chain's native execution logic; it does not depend on external infrastructure or separate automation services.”

Predicates can read not only stored state but transitions other programs produce in the same block, plus events, oracle data and time checks.

“State transitions produced by other programs during the same block”

A workflow stores a predicate that wakes it on an oracle update and can schedule a delayed conditional step itself, with no external scheduler.

“A workflow can suspend after its first step, store a predicate that will awaken it when an oracle updates, and schedule another conditional step that will run after a delay.”

Making reactive execution a native primitive is how Rialo replaces bots, keepers, cron systems and other external automation.

“By making reactive execution a native protocol primitive, Rialo removes the need for bots, keepers, cron systems, and other forms of external automation.”

It is the reverse: the example fees rise during volatility spikes and fall during calm periods.

“Fees that rise during volatility spikes and fall during calm periods”

Supermodularity means components are worth more combined; reactive transactions unify coordination, state and execution so applications compose natively.

“Reactive transactions enhance supermodularity by unifying coordination, state management, and execution in a single environment.”

Evaluate, mark triggered, enqueue, execute: all of it happens inside the validators' native execution, with no external service.

“At the end of a block's execution, Rialo evaluates all predicates whose dependencies may have changed. The evaluation is deterministic, meaning every validator arrives at the same conclusions. 5. Any predicate that becomes true is marked as triggered. Rialo automatically enqueues the associated transaction for execution. 6. The triggered transaction runs either within the same block or in the subsequent blocks, depending on dependency ordering.”

This line is from the post Reactive Transactions: A Model for Native Automation on Rialo.

“Reactive execution allows these adjustments to be performed natively onchain, without relying on external automation.”

Rialo Learn: Reactive Transactions

The demo lets you fire on intervals, on an account balance crossing a threshold, or on an external data feed.

“Choose from three trigger types: Time-based (execute at intervals), Value-based (trigger when account balance crosses threshold), or Data-based (react to external data feeds).”

The Recurring option makes the reactive transaction repeat each time its condition is met again instead of executing a single time.

“Recurring (repeat when condition is met again)”

The Learn page's three sample predicates are every 10 blocks, balance > $1000, and BTC < $95K.

“Create a logical condition: time-based ("every 10 blocks"), value-based ("when balance > $1000"), or data-driven ("when BTC < $95K").”

Conditional and time-based execution is built into the chain, so the usual offchain automation disappears.

“Conditional and time-based execution built directly into the blockchain. No bots. No keepers. No cron jobs.”

Composable is one of the three properties the Learn page lists, next to Deterministic and Trustless: protocols chain reactions without middleware.

“Composable Chain reactions across protocols without middleware.”

Value-based triggers watch an account balance; time-based ones run at intervals and data-based ones react to external feeds.

“Value-based (trigger when account balance crosses threshold)”

Upgrading the Consumer Lending Stack

Conditional transactions, also called reactive transactions, run automatically once user-defined conditions are met and power native automation.

“a conditional transaction (also called a reactive transaction) is automatically executed by the network once certain user-defined conditions are satisfied.”

The required actions execute automatically with no admin, bot, keeper or relayer orchestrating them.

“In each case, the required onchain actions execute automatically without an admin or external actor (e.g., bot, keeper, or relayer) having to orchestrate it.”

Rialo Foundations II: Supermodularity and Blockchain Integration

Reactive transactions plus the native bridge and native oracles let a price condition on SOL:BTC trigger a cross-chain mint.

“This combination allows users to execute complex workflows like "Send 1000 USDC from my Rialo address to my Ethereum account" or "Send a request to mint WBTC to my Solana address whenever the SOL:BTC pair falls below $X".”

Supermodularity and System Welfare: The Economics of Integration

Native automation watches positions, the protocol emits an event when one falls below the threshold, and a reactive transaction liquidates it.

“Loan positions continuously monitored by native automation (set a transaction that recalculates LTV ratios for open borrowing positions at intervals or whenever oracle prices change) Undercollateralized loans automatically liquidated by the chain when collateral value is negative (set up the protocol to emit an event when the loan position falls below a threshold and create a reactive transaction that responds to the emitted event and automatically liquidates the loan)”

Other topics