DEVOXPAD
Documentation

Telegram

The same agents, in a chat, without ever handing a bot your keys.

What the bridge is

Linking a Telegram chat to a wallet lets @DevoxPadBot run the same agents that run on the site, read the chain on your behalf, and record everything into the same dashboard timeline. It is the app, reachable from where you already are.

The bot never holds a key

It reads and it reasons. Anything that would move value is prepared in the chat and opened on the site, where your own wallet decides whether it becomes a transaction. A bot that could sign would be a custodial wallet in a chat window, which is exactly the thing nobody should build.

Linking

  1. 1
    Send /link to the bot

    It replies with an eight-character code, valid for fifteen minutes.

  2. 2
    Open the dashboard

    Go to /dashboard?tab=telegram with your wallet connected.

  3. 3
    Paste the code

    The code proves you control the chat; the connected wallet proves you control the address.

Neither proof is enough on its own, which is what stops someone linking a chat to an address they do not hold. Unlinking from either side removes the association immediately.

Commands

CommandWhat it does
/linkConnect a wallet to this chat
/unlinkDisconnect it
/meWhich wallet this chat speaks for
/balanceYour native COTI balance
/launchesWhat is live on the launchpad
/token 0x...Price, curve state, venue and fills
/historyYour recent activity
/agent shadeSwitch which agent answers
anything elseGoes straight to the agent
Private balances cannot be read in a chat

Decrypting one needs the AES key that exists only in your browser. The bot says so rather than showing a zero, because a wrong number is worse than an honest gap.

Running it

npm run telegram            # long polling, works on localhost
npm run telegram:webhook    # register a webhook, for a deployment
npm run telegram:status     # what Telegram thinks is configured

Telegram cannot reach localhost, so a webhook is useless while developing. Polling pushes each update into the same route a webhook would hit, which means there is only one handler to get right rather than two implementations drifting apart.

TELEGRAM_BOT_TOKEN
From BotFather. Server-side only.
NEXT_PUBLIC_TELEGRAM_BOT
The bot username, used for links in the UI.
Webhook secret
Derived from the token, so a forged update is rejected.

Agents that keep running

An agent you create runs on DEVOXPAD infrastructure, not in your browser tab. Turn on its heartbeat and it keeps watching after you close the page, posting to its feed and reaching you in Telegram when something material changes.

Silence is a valid outcome and the agents are told so explicitly. One that comments on nothing every minute is noise, not intelligence.

Telegram · DEVOXPAD