VOW · OPERATOR CONTROL ROOM

Reserve one approved purchase

Choose from permissions the owner already committed. Every available action is derived from the encrypted set and checked against the deployed VowVault before it can reach the wallet.

Deployment Reading the deployment manifest… Inspect the controlled 0.1 STRK reservation →

1. Load the committed permission set

This is the encrypted file the owner created. Every permission object below is checked against the mandate root already on chain before it can be selected.

Scanning for wallets… No permission set loaded. No mandate read.

Mandate totals

Five separate numbers, in the token’s smallest unit. A reservation can only draw on Available.

  • Fundedunread
  • Availableunread
  • Reservedunread
  • Paidunread
  • Reclaimedunread
No mandate state read.

2. Choose one permission object

Committed permission objects

Only unused permission objects from the loaded set can be selected. Padding slots are never shown because they hold no permission.

3. Review the exact reservation

Bounded by this permission’s committed cap and by the mandate’s Available total. The request deadline is derived from the permission and cannot be extended here.

No reservation reviewed.
No reservation reviewed.

4. Operator signature

Sign the exact authorization above with the operator key in a separate tool. Enter only the resulting public signature; this page never asks for a private key.

No operator signature checked.

5. Send the reservation

The wallet prices and confirms this call. This page cannot cap a network fee: reject the wallet confirmation if its fee is higher than you accept.

State: READY

Nothing has been signed or sent.

Exact call

No call built.

Transaction hash

No transaction hash for this attempt.

Only needed when the outcome is UNKNOWN and no hash was returned. An unknown outcome is never permission to send the call again.

No public receipt read.