Cross-VM writes share one journal

Cross-VM writes share one journal A sequence diagram generated by Archify. eto_buildWorkflow data + accounts signed workflow first instruction increment counter read 0; stage 1 next instruction increment same counter see 1; stage 2 outer commit: 2 separate attempt child increment read 3; stage 4 parent traps discard staged writes Successful workflow Separate failure case Client · signs workflow · Sequence participant Client signs workflow Builder · unsigned data · Sequence participant Builder unsigned data Outer router · caps + budget · Sequence participant Outer router caps + budget WASM · parent call · Sequence participant WASM parent call Move · registered native · Sequence participant Move registered native CuEVM · same counter · Sequence participant CuEVM same counter Journal · staged writes · Sequence participant Journal staged writes State · canonical commit · Sequence participant State canonical commit Legend request return security default message

One successful outer outcome

  • • From committed counter 0, WASM then Move call the same EVM counter.
  • • The second call observes staged value 1; outer commit publishes 2.
  • • The builder produces unsigned instruction data and accounts, not execution.

Shared authority and accounting

  • • Signed, attenuated capabilities constrain nested calls.
  • • The outer workflow carries a shared resource budget.
  • • The Move fixture explicitly registers its native table; this is not every VM pair.

Failure is a separate attempt

  • • Starting from committed 3, a child stages 4 and the WASM parent traps.
  • • The journal discards the attempt; committed counter remains 3.
  • • Compute is still charged.