BOT TESTNET PILOT · CHAIN 968 ONLY

One start. Three wallet approvals.

Connect a wallet you control, review a bounded native tBOT plan, then approve each transaction separately in your wallet. The runner checks receipts before moving on. It never holds a private key. Selecting a page never switches the wallet; the separate Switch button asks your wallet to confirm that change.

Wallet roles: one externally owned account deploys and owns a fresh test receiver, pays 0.01 tBOT into it through the previously tested settlement contract, then calls that receiver’s withdrawal to return the principal to the same account. Contract/delegated-code accounts are unsupported. Gas is spent. A wallet you do not control cannot recover the principal.

1 · Connect and review

Checking wallet network without requesting a change…

No BOT testnet wallet connected.

2 · Progress and recovery

No run started.

    If a wallet response has no hash, the outcome is unknown. The runner stops; it never automatically re-sends. A delayed wallet response may supply the original hash later. The held-hash verification button checks the original hash only and never opens a wallet prompt. Resume checks a pending original hash, then may request the next distinct transaction for its own wallet approval. A wallet or chain change stops the run. The prior browser journal is never cleared for an unresolved run.

    Trust boundary

    The app uses your injected wallet provider for chain data and wallet prompts. It checks a pinned testnet genesis, reviewed settlement runtime, an owner-controlled receiver, exact intent, receipt/event and provider-reported finality. A single provider is not independent consensus. The newer wallet integration has local fake-provider tests; those fixtures do not execute Solidity. This revision's type-2 recovery path has not been qualified with a live owner wallet.

    No mainnet code path, account funding, faucet request, private key import or automatic signing is included. The app requests a legacy gas price and verifies a wallet-converted type-2 transaction only when both signed fee maxima remain within that reviewed price cap. App fee caps are engineering defaults, not a hard wallet spending limit. Inspect every wallet prompt.