Guides

How requests take turns

The encrypted book runs one computation at a time, numbered in order. The app waits for the book before asking your wallet to sign.

The encrypted book processes one computation at a time: admitting an order, a matching round, a remaining-size read, or initialization. Each one carries the next number in sequence, which ties every result to the exact book it was computed on.

What the app shows#

The app's header shows what the book is doing under Matching: Idle, Round in progress, Admitting an order, Reading a private balance or Cancelling an order, with when it started. The bar's string lights its node while a computation runs.

When you seal, read or cancel#

The app checks the book first. If a computation is running, it shows Waiting for the matching round in progress to finish and asks your wallet to sign once the book is free.

If another request still takes the book between your signature and its arrival, the network refuses yours before sending it. Nothing was sent, the saved copy is cleared, and the app asks you to try again.

A computation that stays pending#

When a computation has been pending for ten minutes of on-chain time, anyone can fence it, and Your order offers Recover the stalled computation. Fencing abandons that computation and permanently rejects its result if it arrives later:

• an order that was being admitted is dropped and its vault released;
• a resting order stays exactly where it was;
• a matching round closes without changing any balance.