Discord Bot foundation

[joelamouche]

THIS COULD BE DONE EITHER IN TYPESCRIPT OR RUST

Write a simple bot that listens to user messages.

The bot has a db of activity point events:

• userName
• amount
• eventType: for now it's "message", in the future we could add "vote", "affiliate", etc
• date
• processedStatus: bool

On each message, add an event in the db

Later on we will have endpoints to get unprocessed user balances and mint them

[PeterOche]

i'll love to work on this issue

Recommended by OnlyDust for high-quality and dependable contributions.

[joelamouche]

Great @PeterOche !
Don't hesitate to check out our website theguild.dev, create a profile and join our discord.
What is your plan for this ticket? Rust or Typescript?
Please write some specs on this ticket before you start working.
And also provide a approximate time estimate pls

[PeterOche]

Great @PeterOche ! Don't hesitate to check out our website theguild.dev, create a profile and join our discord. What is your plan for this ticket? Rust or Typescript? Please write some specs on this ticket before you start working. And also provide a approximate time estimate pls

Thank you @joelamouche
I will be using Typescript
My Time Estimate: 24 hours

Plan and specs (TypeScript)

Service: New discord-bot service (Node 20 + TypeScript 5).

Libraries:
discord.js (Gateway intents: Guilds, GuildMessages, MessageContent).
pg (PostgreSQL client), zod (env validation), pino (logging).
Database: Reuse existing Postgres in docker-compose. Raw SQL migrations for consistency with repo (like backend/ and indexer/).

Schema:
Table: activity_events
Fields:
id UUID PK
user_name TEXT NOT NULL
amount INTEGER NOT NULL DEFAULT 1
event_type TEXT NOT NULL CHECK (event_type IN ('message'))
date TIMESTAMPTZ NOT NULL DEFAULT NOW()
processed_status BOOLEAN NOT NULL DEFAULT false
user_id TEXT NOT NULL for future-proofing against display name changes

Behavior:
On every non-bot message in any configured guild/channel, insert an event:
event_type = 'message'
user_name = message.author.username (and user_id = message.author.id if we add it)
amount = default 1 (configurable via env)
processed_status = false
date = NOW()
Basic duplicate guard: ignore messages from bots; optional rate limit (e.g., max N messages per user per minute) via an in-memory token bucket to prevent spam.

Config (env):
DISCORD_BOT_TOKEN
DISCORD_APP_ID
DISCORD_GUILD_ID (optional; if unset, run in all guilds the bot is in)
POINTS_PER_MESSAGE (default 1)
DATABASE_URL (inside docker: postgresql://guild_user:guild_password@postgres:5432/guild_genesis)
LOG_LEVEL (default info)

Docker:
Add discord-bot service to docker-compose.yml, depends on postgres.

Observability:
Structured logs for connects/disconnects, inserts, and errors.
Health check endpoint not required (headless worker), but can expose /: ok via tiny HTTP server if desired.

Security:
No user PII beyond Discord user_name (and user_id if added).
Bot token only from env; do not log token or message content.

[joelamouche]

Sounds good!

What is DISCORD_GUILD_ID (optional; if unset, run in all guilds the bot is in) ?

[PeterOche]

Sounds good!

What is DISCORD_GUILD_ID (optional; if unset, run in all guilds the bot is in) ?

DISCORD_GUILD_ID is the Discord server (guild) ID where you want the bot to track messages. If i don't set it, the bot will track messages in ALL Discord servers it's added to.