tari-manifest

Tari Ootle Transaction Manifests

Tari Ootle manifests are a Rust-like DSL for defining transaction instructions. They are parsed by tari_transaction_manifest::parse_manifest() and compiled into Vec<Instruction> for execution on the Tari engine.

CRITICAL: User Confirmation Required Before Submission

NEVER submit a transaction without explicit user confirmation. Before calling transactions.submit_manifest (with dry_run: false), ALWAYS:

1. Present a clear summary of what the transaction will do, including:
   • The action in plain language (e.g. "Transfer 100 tTARI from account A to account B")
   • The manifest source code
   • All variables and their resolved values (component addresses, amounts, etc.)
   • The max fee
   • Which account will sign/pay fees
2. Ask the user to confirm before proceeding. Wait for explicit approval.
3. Do not batch or auto-submit multiple transactions without per-transaction confirmation.

Dry-run submissions (dry_run: true) may be performed without confirmation as they do not modify state.

Manifest Structure

Every manifest has a fn main() block for transaction instructions and an optional fn fee_main() block for fee payment. Helper functions may be defined and are inlined at call sites.

// Optional: import templates by hash
use template_<64-char-hex-hash> as TemplateName;

// Optional: fee instructions (executed first)
fn fee_main() {
    let account = arg!["account"];
    account.pay_fee(1000);
}

// Required: main transaction instructions
fn main() {
    let account = var!["account"];
    let component = var!["component"];

    let result = component.some_method(arg1, arg2);
    account.deposit(result);
}

Core Concepts

Variables and Arguments

Access runtime variables passed to the manifest via globals:

let my_var = var!["variable_name"];   // workspace variable
let my_var = arg!["argument_name"];   // alias for var!
let my_var = global!["global_name"];  // alias for var!