Burn Bot Project Admin projects.json editor (local admin API)

Password-protected helper UI to inspect all configured burn bot projects and update the central projects.json via the local admin API. The API runs on the same host and port as this UI.

Admin login

Authenticate against the local admin API. On success, a session cookie is created and all subsequent API calls use that session.

Admin password This password is validated on the server (bcrypt hash in ADMIN_PASSWORD_HASH). It is never stored in this UI.

Existing projects

Loaded live from the local admin API. Arrays are shown as pills; Telegram-related IDs include deep links where possible.

Create new project

All required fields must be filled. The form will construct the full JSON object according to the current schema and send the updated list to the admin API.

writes via /admin/projects

Project ID (internal, unique) Short machine-friendly identifier, e.g. xxx_tales or calamus. Used by the bot to look up this project and must be unique across all entries.

Project name (human readable) Display name for this project, e.g. "XXX Tales" or "Calamus". Only used for admin interfaces and logging.

Project enabled When enabled, the burn bot will actively process events and messages for this project. Disable to temporarily suspend all activity.

Info bot chat IDs (required, at least one) Telegram chat IDs where the InfoBot sends burn events and status updates. Use comma or newline separated values. At least one is required to test the InfoBot.

Linked chat IDs Main chats/groups directly associated with this project (e.g. trading chat, main community group). The bot will use these IDs when mapping inbound messages to projects.

Pending chats Optional list of chats that requested to link with this project but still await manual approval. The bot can move them from this list to linked_chat_ids when approved.

Admin user IDs (required, at least one) Telegram user IDs that are allowed to manage this project (approve chats, change settings via commands, etc.). Must contain at least one ID.

Admin chat IDs Optional dedicated admin-only chats for this project. The bot can send error messages, warnings and operational notifications here (e.g. missing project mapping, RPC issues).

Push chat IDs Telegram chats where the bot may push announcements or burn-related broadcasts for this project. This is separate from InfoBot event streams to allow more targeted communication.

Push user IDs Optional list of Telegram user IDs that should receive direct push notifications (e.g. project owners or key stakeholders).

Primary RPC URL Main Solana RPC endpoint for this project, e.g. https://api.mainnet-beta.solana.com. The bot uses this to query token supply, burn transactions and on-chain state.

Additional RPC URLs (optional) Optional list of backup or premium RPC endpoints. You can enter comma or newline separated URLs. The bot can later be extended to rotate or fail over between these endpoints.

Token mint address Solana token mint address for the token that is being burned, e.g. your meme coin or RWA token. Used for supply queries and validating burn transactions.

Burn wallet address Solana wallet address that receives burned tokens. The bot can track incoming transfers here and treat them as burn events.

Project owner wallet address Optional project owner wallet (e.g. Phantom). Can be used for internal verification, manual tests or linking web dashboards.

Connect base URL Base URL for user wallet connections and on-chain signing flows, e.g. a project-specific connect page. The bot can include this in deep links so users connect their wallet to your platform.

Burn page base URL Base URL for the public burn page where users can see burn events, statistics and call-to-action buttons. The bot may link here when broadcasting burn notifications.

Current projects.json

This reflects the in-memory representation of your projects as loaded and saved via the admin API.

Note: The actual file lives on the server. This view is synced by calling /admin/projects. Each save creates a backup on the server.