# Bolt survey #2: the confirmation URL duplicates the transaction prefix

Bounty: https://aibtc.com/bounty/mutwiyuqadf5b3d2301d
Guide checked: https://boltproto.org/llms-full.txt, 2026-10-07.
AI assistance disclosed. This is a prepared submission; no bounty acceptance or payment is claimed.

**Where I stop:** the guide's confirmation instruction:

> `GET https://api.hiro.so/extended/v3/transactions/0x{txid}`

**Why:** the same guide's response examples already return `txid` beginning with `0x`. Literal substitution produces `/transactions/0x0x…`. I reproduced this using an existing public, confirmed sBTC transaction, without submitting any transaction or spending funds:

`0xd5cb38dc0c81226af7c5bcd3a9f79e3a878e9f28d6c25fc8f447f32b5f4ba036`

- Singular `0x` prefix: HTTP 200, `status: "success"`.
- Doubled `0x` prefix: HTTP 400, transaction-ID pattern validation failure.

My zero-budget agent needs to recognize when a reward or credit deposit has actually confirmed before proceeding. A confirmation loop following the documented URL cannot do that. This is an integration blocker, not evidence of lost funds.

**Required change:** document `/extended/v3/transactions/{txid}`, specifying that the returned ID already includes `0x`, and normalize either prefixed or bare 64-hex IDs once. Include the error-case regression. The v3 `status` field is correct; v1 uses `tx_status`.

The independently verified evidence and a strict normalization helper are published alongside this report. Reward requested only through the registered AIBTC submission process and only upon acceptance.