Remove allowed_users.txt from tracking, add local/umbrel mode, UMBREL_IP support

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

README.md

@@ -50,6 +50,7 @@ TELEGRAM_BOT_TOKEN=your_bot_token_here
 ### 3. Add your Telegram user ID to the allowed users list
 
 ```bash
+cp allowed_users.txt.example allowed_users.txt
 nano allowed_users.txt
 ```
 
@@ -82,6 +83,61 @@ You should see `Electrum daemon started. Launching bot...` followed by the bot s
 
 ---
 
+## Local / Umbrel Mode
+
+Use this mode to connect to your own Electrum server running on Umbrel (or any local node) on your home network.
+
+> **Note:** `umbrel.local` does not resolve inside Docker containers — mDNS is host-only. Use the actual **IP address** of your Umbrel device (e.g. `192.168.1.100`).
+
+### Setup
+
+```bash
+cp .env.example .env
+nano .env
+```
+
+Fill in `TELEGRAM_BOT_TOKEN` and set your Umbrel's IP:
+
+```
+UMBREL_IP=192.168.1.100
+```
+
+```bash
+cp allowed_users.txt.example allowed_users.txt
+nano allowed_users.txt
+```
+
+### Start
+
+```bash
+docker compose -f docker-compose.local.yml up -d --build
+```
+
+### How it works
+
+On first start, the entrypoint writes `./electrum-data/config` with:
+
+```json
+{
+    "auto_connect": false,
+    "enable_proxy": false,
+    "oneserver": true,
+    "server": "192.168.1.100:50001:t"
+}
+```
+
+If the config file already exists it is left untouched, so manual edits survive restarts.
+
+> **If the connection doesn't work:** check `./electrum-data/config` after the first run and make sure the server string still ends in `:t` (TCP). Electrum may rewrite it to `:s` (SSL) on first connect. If it did, stop the container, change it back to `:t`, and restart.
+
+### Check logs
+
+```bash
+docker compose -f docker-compose.local.yml logs -f
+```
+
+---
+
 ## Tor Mode
 
 Tor mode runs Electrum through the Tor network. It uses a separate Docker Compose file and Dockerfile so the standard setup is not affected.