RFP-003 BTC test-case run on the v0.2.4 bundle (2026-09-23)

Cases run: the five BTC cases from the Logos review map (gist) that have an entry point in the v0.2.4 release, each in both directions.

Candidate: Gateway v0.2.4, 98f492adff67bf62c22e04609f0810c196d6a0dc.

Coverage review these results belong to: RFP-003 test-case coverage review of the Logos review map (2026-09-23).

Run date: 2026-09-23

1. Setup

The five BTC cases that have an entry point in the release were executed on this machine against the v0.2.4 bundle (lez-swap-stack-v0.2.4-arm64, images pulled by tag, escrow ImageID c22d61fc…), Bitcoin Regtest and a local LEZ devnet on the fast timing profile, driven by the release’s scripts/node-e2e.py. Both directions were run for every case. Logs, scenario JSON and the results table are in lez-swap-stack-v0.2.4-arm64/review-runs-20260923/.

2. Results

Case	Scenario	Direction	Result	Duration	Swap
BTC-HAPPY-001	`happy`	TakerSellsForeign	PASS	417 s	`1a274278…`
BTC-HAPPY-001	`happy`	TakerSellsLez	PASS	257 s	`2363628e…`
BTC-REFUND-001	`taker-refund`	TakerSellsForeign	PASS on retry	1368 s	`7735bd51…`
BTC-REFUND-001	`taker-refund`	TakerSellsLez	PASS	1955 s	`f90d0473…`
BTC-REFUND-002	`maker-refund`	TakerSellsForeign	PASS	1916 s	`47bca60e…`
BTC-REFUND-002	`maker-refund`	TakerSellsLez	PASS	1913 s	`58f0a0f6…`
BTC-RESTART-001	`restart-taker`	TakerSellsForeign	PASS	242 s	`016eb793…`
BTC-RESTART-001	`restart-maker`	TakerSellsForeign	PASS	231 s	`60a7f672…`
BTC-RESTART-001	`restart-taker`	TakerSellsLez	PASS	294 s	`89ee0667…`
BTC-RESTART-001	`restart-maker`	TakerSellsLez	PASS	252 s	`bf81f65d…`
BTC-CONCURRENT-001	`concurrent`	TakerSellsForeign	PASS	365 s	`c526e1d0…`, `316e938f…`
BTC-CONCURRENT-001	`concurrent`	TakerSellsLez	PASS	248 s	`82fe68ed…`, `dd2b4382…`

3. Notes on the run

The first attempt at the forward BTC-REFUND-001 failed in the driver’s preflight because the local LEZ devnet stopped finalizing (Bedrock logged 0 transactions (62 removed)), the upstream freeze described in deploy/README.md. The chain was recreated with up.sh --fresh-lez, the market re-bootstrapped, and the retry passed. No swap failed.
Two bundle defects surfaced on the fresh-chain path. up.sh --fresh-lez looks for :local images unless release.env is sourced first, and the vault-claim tool refuses the bundled lez-signer.key files until they are made owner-only (chmod 0600). Neither affects a first start, where the vaults are already claimed.
The batch was paused once between cases with down.sh and resumed with start.sh; the chain and the persisted swaps survived the stop.

4. Limits

These are driver-reported passes on a local API stack. They do not include the independent chain checks the gist attaches to its own records, they do not exercise the native Basecamp UI, and they are not public-network or security evidence. With these runs, every one of the five release-runnable BTC cases now has a pass in both directions on the candidate, which closes finding 1 in section 4 for those cases. BTC-CLAIM-001/002 and BTC-TIMING-001 were not run here: the first two need the reviewer’s patched driver from the gist, the third a funded public session.