ootle-rs 0.13.0

A Rust library for interacting with the Tari Ootle network.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75

# ootle.rs Examples

Runnable examples demonstrating how to use `ootle-rs` to interact with the Tari Ootle network.

## Prerequisites

All examples require a running **localnet** with an indexer (default: `http://127.0.0.1:12500`).

```bash
cargo run --example <example_name>
```

## Examples

### `fungible_transfer`

End-to-end public fungible token transfer: create a wallet, fund from faucet,
send multiple transfers in a single transaction, dry-run with fee estimation,
and verify balances.

### `stealth_transfer`

Confidential stealth transfers with input/output commitments, encrypted memos,
change handling, and stealth spending authorizers.

### `stealth_spend_conditions`

TIP-0006 spend conditions — condition trees (MAST) with builtin predicates. Takes free coins
from the faucet and locks them, for a destination account, behind a hash time-locked contract
(HTLC): a two-leaf condition tree of `BuiltinPredicate` leaves (a `HashLock` plus
`BeforeEpoch`/`AfterEpoch` timelocks) combined with `SpendCondition::All`, attached to a stealth
`Output` via `Output::with_spend_conditions`. Posts a real transaction on localnet.

### `claim_burn`

Claim a Layer 1 (minotari) burn into an Ootle account.

Claiming is a two-step process because the L1 burn must be addressed to a claim key
derived from the claiming account. Run it with no arguments to print the claim public
key (it uses a fixed, demo-only secret), burn tTARI on the L1 wallet to that key, then
re-run with the burn proof JSON as the first argument to claim:

```bash
cargo run -p ootle-rs --example claim_burn                       # prints the claim key
cargo run -p ootle-rs --example claim_burn -- ./burn_proof.json  # claims the burn
```

See the example file header for the full flow.

### `balance_query`

Query account balances and decrypt stealth UTXO values using ElGamal view keys.

Requires updating constants in the example: resource address, view secret key,
UTXO commitment, and max expected value.

> **Note:** UTXO decryption with on-the-fly lookup generation is slow.
> For production use, enable the `mmap-value-lookup` feature with pregenerated
> lookup files.

### `template_invoke`

Type-safe template invocation using the `ootle_template!` macro. Shows how to
define custom template interfaces, call template functions and component methods,
chain calls with workspace piping, and fall back to raw `TransactionBuilder`.

Requires updating template and component addresses in the example.

### `watch_component_events`

Real-time event monitoring via SSE (Server-Sent Events). Subscribe to events
filtered by component address and optional topic, with automatic reconnection
and resume-from-last-seen capability.

Requires updating the component address in the example.