.gitignore

/target
**/*.rs.bk

# Operator-local helper (writes ../blitzpool_version/commit.txt for the
# frontend version pill). Same script as the TS public-pool repo.
/write_version.sh
.env
.env.local
.DS_Store
*.swp
*.swo
.idea/
.vscode/

# Local config + secrets (prod env mirror, FCM service-account JSON,
# blitzpool.toml with real keys). Anything an operator drops here
# stays out of git — point `bin/blitzpool --config` at a file inside.
.local/

# ── docker-compose full-setup deployments ───────────────────────────
# Persistent state (blockchain, PG, Redis, logs) — multi-GB, never
# committed. The `data/` directory under any `full-setup/`-style
# layout is generated by `prepare.sh` and lives only on the
# deployment host.
full-setup/data/
# Operator secrets — keys (SV2 authority privkey, FCM service-account
# JSON, web-push VAPID pair) and per-stack runtime configs. Examples
# (`*.example.toml`) ARE committed; the actual `blitzpool.toml` /
# `blitzpool-regtest.toml` / `blitzpool-testnet4.toml` are not.
full-setup/keys/
full-setup/blitzpool.toml
full-setup/blitzpool-regtest.toml
full-setup/blitzpool-testnet4.toml
full-setup/.env
full-setup/docker-compose-mainnet-pg.yml
full-setup/docker-compose-mainnet-pg-split.yml
full-setup/docker-compose-regtest-pg-split.yml
# Operator-local shell scripts (build_and_deploy, cutover, rolling-update,
# ad-hoc one-shots). prepare.sh is the only sh script tracked in-repo.
full-setup/*.sh
!full-setup/prepare.sh

# ── Local scratch docs — never committed ────────────────────────────
# Design drafts, planning/triage scratch files. Live locally for
# reference; kept out of git so a stray `git add .` can't sweep them in.
DESIGN-*.md
DEFERRED.md
CHECKLIST.md