Fix accidental API key exposure in source files

[dewhush]

What's happening here?

I noticed that some API credentials were accidentally committed to this repository. This is a pretty common issue — it happens to the best of us! Here's what this PR does:

Changes

Files cleaned up:

• ./.env

• Removed hardcoded API keys from source files

• Added .env.example with placeholder values so new contributors know what env vars are needed

• Updated .gitignore to prevent environment files from being committed in the future

What you should do after merging

1. Rotate the exposed credentials immediately — Any API key that was in a public repo should be considered compromised, even if you revert the commit. Bots scrape GitHub constantly.
2. Use environment variables or a secrets manager (like dotenv, Vault, etc.) for sensitive values
3. Check your git history — the old keys may still be visible in previous commits

Quick setup after merge

cp .env.example .env
# Edit .env with your actual API keys

Happy to answer any questions!

---

If you found this helpful, tips are welcome:
ETH: 0x1478f1BDEACc7b434b4405350A15993cDcddc79F