Contract-aware envelopes
A cross-zone message identifies its target contract, function, and arguments. The destination is explicit and can be checked before execution.
Organize execution
A place for each part of the organization.
Zones organize contract execution and provide a deterministic path for messages between supported contract contexts.
Organization ZonesIllustrated study
A composition, not a black box.
Compose the primitives. Keep their boundaries explicit.
01 / Built for a purpose
Separate responsibilities. Connect the work.
An organization can have more than one contract and more than one responsibility. Zone-aware execution provides structure, while a deterministic delivery process lets supported contracts exchange messages without making network calls during block execution.
Ordered delivery
The delivery process snapshots pending messages and follows a deterministic order. Validators see the same inputs and can reproduce the same delivery decisions.
Bounded work per block
Per-zone delivery limits keep one queue from consuming unbounded execution. Messages remain part of an inspectable process.
Failures stay isolated
Malformed and failed deliveries receive failure outcomes without preventing later messages from being considered. Suspended zones can preserve their pending work.
The details matterGood questions.
Good questions.
Clear answers.
Is every zone transaction available?
No. The supported cross-zone path runs through the contract host and delivery envelope. Older direct zone transaction variants remain gated.
Is a cross-zone message the same as an instant remote call?
No. It is queued and processed under deterministic delivery rules. Applications should account for delivery outcomes and message ordering explicitly.
Keep exploringOne capability.