git / moonbite-network / .gitignore · raw

blockchain_monitor.logblockchain_node.log.git-rewrite/__pycache__/*.pyc# Runtime SQLite databases. These are per-deployment state, not source: when# they were committed, every deploy overwrote whatever users had written with# a stale local snapshot. Each module recreates its schema on startup, so an# absent file is the normal cold-start case, not an error.*.db*.db-journal*.db-wal*.db-shm# Signup capture: runtime data, and it holds email addresses. It was# committed here, so every deploy overwrote the live list with the copy from# git, in a public repository.notify_signups.jsonlrelease/miner/downloads/# Build outputs: the Windows miner bundle and the staged .exe binaries are# generated by deploy/miner/build-windows-bundle.py. Keeping them out of git# prevents a second, divergent copy of a binary from being committed alongside# release/bin (the drift the 2026-10-03 audit flagged). Each build emits its own# SHA256SUMS.txt for verification.release/dist/release/miner/*.exe*.tar.gz*.zipCURRENT_TUNNEL_URL.txt# Release signing: the SECRET signing key must NEVER be committed (deploy/RELEASE-SIGNING.md)*.keydeploy/moonbite-release.key# Flutter build cache + runtime logs: regenerable, never tracked (carry local paths/PII)mobile/build/mobile/.dart_tool/mobile/.flutter-plugins-dependenciesblockchain.lognode_output.log# Opsec (audit 2026-10-09, H4/M10): local tool state, audit notes and runtime# logs/data carry machine paths, hostnames and user data. Never track them..claude/AUDIT_*.mdAUDIT_*.diff*.jsonl*.logbackup_2026-07-31/# Clean-slate: build outputs are never committed; CI rebuilds them from source.release/bin/release/wallet/reactor-app/pkg/*.exe*.zip*.tar.gz*.dll*.so*.dylib