# SwitchBitcoin pre-alpha — bug report

Copy this file, fill every section, send it through your onboarding channel.
One report per problem. SAFETY: never include your mnemonic, passphrase, or
RPC password — `diag` output is safe by construction; terminal scrollback
from `init` is NOT (it showed the mnemonic once).

## What happened (one sentence)

## Exact steps to reproduce
1.
2.
3.

## Expected vs actual
- expected:
- actual:

## `switchbitcoin-cli diag` output (paste the whole block)
```
(run: switchbitcoin-cli diag)
```

## The failing command + its FULL stderr
```
(re-run the failing command and paste everything it printed)
```

## Environment
- Bitcoin Core version (`bitcoind --version` first line):
- network (testnet4 / regtest):
- OS:
- if swapping: was your partner on the same build? (`switchbitcoin-cli version` both sides)

## Discovery (fill this ONLY if the problem involved `discover …`)

Skip this whole section for manual `swap --make` / `--take` reports.

- `switchbitcoin-cli discover doctor` output (paste the whole block — it names
  your network, quorum, relay list, CURATED-vs-CUSTOM verdict, and Tor state):
```
(run: switchbitcoin-cli discover doctor)
```
- which verb: `doctor` / `scan` / `offer` / `offer --serve` / `take` / `take --meet-only`
- relay set you were configured with (the exact `[discovery] relays` line, or
  "the shipped curated list unmodified"):
- relay list verdict `doctor` printed: CURATED / CUSTOM
- was the round's third relay up at the time? (ask if unsure): yes / no / unknown
- Tor: which binary and version (`tor.exe --version`), and bridges or direct?
- refusal class you saw, if any — the exact `discovery: …` string, or the
  enum name from `/status` `last_refusal` (e.g. `RelaysTooFew`, `TorRequired`,
  `ParamsDigestMismatch`, `NotAnOnion`, `InsufficientPow`, `OfferCooling`):
- timings, if it was a slowness report (see the guide's table for what is
  normal): Tor bootstrap ___ s, relays connected ___ s, PoW mint ___ s,
  rendezvous dial ___ s
- did anything get leased or funded? (`status` before/after — a pre-dial or
  dial failure should leave the ledger untouched and say so):

## Severity (your call)
- [ ] funds appear stuck or lost (report IMMEDIATELY, keep the wallet running)
- [ ] a swap failed in a way the guide's troubleshooting table doesn't explain
- [ ] wrong/confusing output, docs, or UX
- [ ] other

## Anything else (timing, mempool conditions, `status` before/after, ...)
