Remove outdated .env.example and update README for enforcer integration

Author: gosunuts

.gitignore

@@ -15,7 +15,7 @@ core.*
 /tmp/
 /.bitcoin-rs/
 /data/
-/.env
+.env
 
 # Re-include project plan tracked in-repo (global ~/.gitignore drops PLAN.md).
 !PLAN.md

README.md

@@ -36,38 +36,41 @@ That starts a mainnet node storing state in `.bitcoin-rs` and serving JSON-RPC
 on `127.0.0.1:8332`. See [docs/getting-started.md](docs/getting-started.md) for
 backend selection, RPC authentication, and checking sync progress.
 
-### Docker Compose
+### Enforcer integration
 
-The enforcer integration Compose configuration builds the production `fjall` +
-`bitcoinkernel` profile, stores node and enforcer data under `data/`, exposes
+The Compose example under `tools/bip300301-enforcer` is specifically for
+running bitcoin-rs together with the BIP300/301 enforcer; it is not the general
+bitcoin-rs deployment path. It builds the production `fjall` + `bitcoinkernel`
+node profile, starts both services, stores their data under `data/`, exposes
 P2P, and binds RPC to the Docker host's loopback interface only. One
-`BITCOIN_RS_NETWORK` selects the matching bitcoin-rs and enforcer network; the
-`drynet4` selection derives its mainnet consensus rules, custom P2P magic, fixed
-peer, and disabled DNS seeding inside bitcoin-rs.
+`BITCOIN_RS_NETWORK` selects the matching network for both services. The
+`drynet4` selection derives its mainnet consensus rules, custom P2P magic,
+fixed peer, and disabled DNS seeding inside bitcoin-rs.
 
-Set explicit RPC credentials in `.env`, then start the node:
+Set explicit RPC credentials in `.env`, then start bitcoin-rs and the enforcer:
 
 ```sh
+cd tools/bip300301-enforcer
 cp .env.example .env
 # Edit .env and set BITCOIN_RS_RPC_PASSWORD before starting the node.
 
-docker compose --env-file .env -f tools/bip300301-enforcer/docker-compose.yaml up --build -d
-docker compose --env-file .env -f tools/bip300301-enforcer/docker-compose.yaml logs -f node
+docker compose up --build -d
+docker compose logs -f
 ```
 
 Check sync progress inside the container. This uses the credentials already
 provided by Compose and does not evaluate `.env` as shell code:
 
 ```sh
-docker compose --env-file .env -f tools/bip300301-enforcer/docker-compose.yaml exec node sh -c \
+docker compose exec node sh -c \
   'curl --user "$BITCOIN_RS_RPC_USER:$BITCOIN_RS_RPC_PASSWORD" \
     -H "content-type: application/json" \
     -d "{\"jsonrpc\":\"1.0\",\"id\":\"sync\",\"method\":\"getblockchaininfo\",\"params\":[]}" \
     http://127.0.0.1:8332/'
 ```
 
 Stop the process without deleting its chain data with
-`docker compose --env-file .env -f tools/bip300301-enforcer/docker-compose.yaml down`.
+`docker compose down`.
 Compose allows up to 5 minutes for the full clean checkpoint before forcing
 termination. Chain data remains under `data/` until it is explicitly removed.