Four-hour Telegram reporting

The fuel-credit-daily-report Worker sends one compact report every four hours at 00:00, 04:00, 08:00, 12:00, 16:00, and 20:00 UTC. Delivery retries after 15 minutes if generation or Telegram delivery fails. A Durable Object deduplicates successful delivery by four-hour UTC period.

Report contents

Separate Testnet and Mainnet sections include:

• rolling 24-hour distinct users and indexed loan actions;
• reported transaction successes and failures;
• borrowed, repaid, claimed, defaulted, and due-next-24-hour totals;
• all-time users and loan status counts;
• all-time borrowed, repaid, outstanding, defaulted, locked collateral, and pool balances; and
• testnet/mainnet oracle health, selected source, market age, signature age, consecutive failures, and mainnet borrower-app status.

Amounts are calculated with exact integer arithmetic. Reports never include addresses, transaction IDs, signatures, secrets, or raw errors. Broad app-usage telemetry is currently disabled and is shown as not collected.

The rolling activity ledger begins when migration 0003_activity.sql is deployed. Opening time uses the onchain loan timestamp. Repayment, claim, and default time uses the indexer's first observation because those transition timestamps are not stored in contract state.

Deployment

Apply the activity migration to both indexer databases before deploying indexers and reporting:

bunx wrangler d1 migrations apply fuel-credit-testnet-index --remote --config workers/indexer/wrangler.jsonc
bunx wrangler d1 migrations apply fuel-credit-mainnet-index --remote --config workers/indexer/wrangler.mainnet.jsonc
bun run indexer:deploy
bunx wrangler deploy --config workers/indexer/wrangler.mainnet.jsonc
bun run reporting:deploy

Install TELEGRAM_BOT_TOKEN as a secret on fuel-credit-daily-report. TELEGRAM_CHAT_ID is non-secret Worker configuration. /health exposes only bounded delivery timestamps/day and a sanitized failure category; there is no public report trigger.