> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useslip.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Record the bounty demo

> A five-minute recording sequence that demonstrates Slip without overstating deployment status.

# How to record the bounty demo

The TxODDS track requires a video of at most five minutes. Record only behavior that is working in the
environment shown. If the public devnet upgrade is incomplete, label the program segment Surfpool and
do not describe it as devnet.

## Required evidence before recording

* public repository URL;
* hosted application URL or functional public API/devnet endpoint;
* deployed unified program and at least one recorded lifecycle, or a clearly labelled Surfpool build;
* wallet with test SOL and settlement USDT;
* fixture and market whose proof path can be demonstrated;
* transaction signatures and TxLINE proof identifiers ready to paste.

If the application-access requirement is still missing, resolve it before recording the final
submission video.

## Five-minute sequence

### 0:00–0:35 — Problem and product

State the problem in one sentence: sports prediction products require users to trust prices and
settlement operators. Show Slip's market list and explain that one primitive handles two to five
outcomes with variable stakes.

### 0:35–1:25 — Natural-language Rulebook

Choose a live TxLINE fixture. Enter both:

```text theme={null}
match result: home, draw, away
```

and the five-outcome example:

```text theme={null}
total corners: 0-7, 8-9, 10-11, 12-13, 14+
```

Show the compiled stat keys, labels, and complete bands before signing. Explain that unsupported
player language is rejected rather than guessed.

### 1:25–2:10 — Variable stakes and odds

Create the market, then stake different amounts from two wallets on different outcomes. Refresh the
market and show the pool totals, implied percentages, ticket records, and vault-backed USDT amount.

### 2:10–3:20 — TxLINE settlement

Show the exact TxLINE surfaces used: score snapshot for terminal status, stat-validation proof, and
the `daily_scores_roots` PDA. Submit resolution through the keeper or resolver. Explain the three proof
segments and terminal phase requirement without reading code line by line.

### 3:20–4:10 — Claim and refund

Show the recorded winner and proportional payout. Claim a winning ticket. Then show a one-sided or
timed-out market being voided and refunded. Point out that losers and double claims fail on-chain.

### 4:10–4:45 — Verification and architecture

Show the passing Surfpool summary and the narrow architecture diagram. State that the keeper is
permissionless and does not choose the outcome.

### 4:45–5:00 — Submission access

Display the public repository, hosted URL/API, program address, and documentation index. End before
five minutes.

## Recording checks

* Keep wallet secrets, API tokens, RPC credentials, and local paths off screen.
* Use readable zoom and show transaction confirmation, not only button clicks.
* Do not use old H2H, scorecast, binary-pari, or outcome-market vocabulary.
* Do not claim CPI settlement; Slip ships an independent proof walk against TxLINE's roots PDA.
* Do not claim the unified program is deployed until the recorded address runs the checked-in binary.