REACTORTürkçe

11 facts

Edge and webcalls

11 facts about edge and webcalls from 3 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

Rialo Dev Portal

Rialo Edge handles bidirectional Web2 interactivity without middleware, and the dev portal puts it at more than 100k concurrent web calls.

“Rialo Edge Bidirectional Web2 interactivity without middleware >100k concurrent web calls”

Introducing Rialo: A Blockchain Built for the Real World

Real World Data on Rialo means a single HTTPS call inside the smart contract pulls live data from anywhere.

“Real World Data : Pull live data anywhere with a one-liner HTTPS call in your smart contract.”

Rialo Learn: Async Transactions

AFTER wait until pauses execution, schedules the off-chain operation, and records that the transaction continues once the result arrives.

“The AFTER wait until keyword pauses execution and schedules an off-chain operation. The blockchain records that this transaction needs to continue after receiving the async result.”

On Rialo everything is paid in the one native token, while the traditional stack in the comparison needs 4+ different tokens.

“Rialo Real World Blockchain Infrastructure None required Tokens Required 1 native token Time to Build Minutes to hours Failure Points Single system”

The tutorial stresses a single fee token: no separate oracle or relay tokens to acquire and manage.

“All fees paid in the native token. No need to acquire or manage multiple token types.”

In block N+M the callback runs by itself with the async result, picking up exactly where the workflow paused.

“In a later block (Block N+M), the pay(success) callback executes automatically with the result of the async operation. The workflow continues exactly where it paused.”

The result is wrapped into a new transaction and comes back through the validator network, so no relay program is needed.

“The async result is wrapped in a new transaction and submitted back to the blockchain through the validator network.”

The tutorial's point is no relays and no bots: the result comes back as a new transaction through the validator network.

“No external infrastructure, no relays, no bots — just native async execution using the AFTER wait until pattern.”

Traditional stacks need relays, keepers and 4+ tokens, so the comparison puts build time at days to weeks versus minutes to hours on Rialo.

“Traditional Blockchains Complex Setup Infrastructure Relays + Keepers Tokens Required 4+ different tokens Time to Build Days to weeks Failure Points Multiple systems”

The example transaction runs request_fico_score(), the request travels encrypted to the off-chain FICO API, and handle_score(score) runs in a later block.

“BLOCK N request_fico_score() executes 🔒 request encrypted E2E ENCRYPTED Data never exposed in mempool OFF-CHAIN FICO API 🔒 encrypted BLOCK N+M handle_score(score) callback executes”

The chain records the pause, the external call runs, the result returns as a transaction through validators, and the callback resumes the workflow.

“The AFTER wait until keyword triggers. The blockchain records that this workflow needs an off-chain operation and will continue later. Payment request executes outside the blockchain. This could be calling a payment API, fetching data, or any external service. The async result is wrapped in a new transaction and submitted back to the blockchain through the validator network. The pay(success) callback executes automatically with the result.”

Other topics