Back to collectionResearch
Conditional orders need an understandable waiting state
Encrypted instructions separate submission from the event that authorizes execution.
Published Updated
The SKALE-referenced conditional-transaction design holds an encrypted order until predefined conditions are met, then executes it onchain. Price, time, capacity or another observable event can therefore govern commitment rather than the moment a user presses submit. The waiting state needs its own rules: who observes the condition, which record prevails in a disagreement, when an order expires and how cancellation works before execution. Separating observation, privacy and settlement across components makes those responsibilities more important. A useful agent can express when to act and when to keep waiting without exposing the instruction prematurely.