How we use Cloudflare and GitHub

Cloudflare: eyes and hands

1. Workers — two scripts: the central sementsul-edge accepts reports at /api/report-bot, webmaster client workers log bots by botManagement.score.
2. D1 — the bot_logs relational base: IP, hit counter, webmaster wallet, processed flag. Free limits cover the start with margin — watch the D1 dashboard metrics.
3. The worker never blocks traffic itself — only logging. A conscious choice: fewer false bans (see False positives).

GitHub: memory and cashier link

1. Actions oracle every 15 minutes: reads new D1 rows → calls the contract → marks processed → rebuilds blocklist.txt and telemetry.json.
2. Pages serves the static site: telemetry, base, blog, llms.txt. No backend.
3. Keepalive keeps cron alive: GitHub puts schedules to sleep after 60 days of silence, the hourly pulse prevents it.

BNB Chain: money

The SementsulV2 contract holds 250M of reserve on its own balance and honestly burns 10 SML per mint. IPs never go on-chain — only their hashes, cheaper and more private.