For the complete documentation index, see llms.txt. This page is also available as Markdown.

🤖Notification Bot

Bot subscriptions, confirmation and the scope of position alerts.

The Frankencoin API Telegram Bot, @FrankencoinApiBot, reports proposals, position activity and other indexed events. FCS holders can use governance alerts to follow proposals; borrowers can follow their positions. Receiving an alert does not submit a transaction or establish voting eligibility. The FCS governance guide explains how to act on a proposal.

How to find it?

Open the linked bot in Telegram and send /help. The commands below are implemented in telegram.service.ts at commit 4fdbd1007a2c75bddff2aaadf2d370e5dc296dd4. They were checked against public source on 18 September 2026, not by sending messages to the live bot.

Subscription Handels

The heading above is retained for existing links. Subscription commands are:

Command
Effect

/help

Show available commands

/status

Show active governance, all-position and owner subscriptions

/start GOV

Subscribe to governance alerts

/stop GOV

Remove governance alerts

/start ALL

Subscribe to all-position alerts

/stop ALL

Remove all-position alerts

/start <owner address>

Subscribe to positions belonging to a complete 0x plus 40-hex-digit owner address

/stop <owner address>

Remove that owner subscription

Angle-bracket text is a placeholder, not a literal command argument. The first message registers the chat in the inspected implementation and enables governance and all-position alerts by default. /status shows the resulting state; unwanted categories can then be removed explicitly. The older /MintingUpdates toggle shown in historical material is not the command model above.

After subscribing, the bot returns a confirmation. Send /status and check the category or full owner address. To test the subscription controls without creating a protocol event, remove and re-add the category, checking /status after each change. This checks the subscription response, not future event delivery.

Basic Messages

Welcome and Environment Information

Help and status identify the chat and subscriptions. Event messages link to relevant transactions, addresses or application views.

Minter Proposals

Governance alerts include minter proposals and vetoes, interest-rate changes and CCIP proposals or rate-limit changes.

Minter Proposals Vetoed

Historical minter-veto notification
Historical message format.

Position Proposals

Historical position-proposal notification
Historical message format.

Challenges Started

Historical challenge notification
Historical message format.

Minting Updates

Historical minting update
Historical message format.

Expiry and price alerts

The inspected source includes expiry notifications at the seven-day and one-day thresholds, and after expiry. Price alerts compare the service's collateral price feed with the position's liquidation price, using warning bands and cooldowns. Owner subscriptions follow the position's owner address; they are not subscriptions to a position address.

Notifications depend on service uptime, indexing, price coverage and Telegram delivery. They do not execute repayment or liquidation-price changes, and a missing alert does not change the contract's expiry or stored price.

Historical subscription screenshots

These local assets preserve the older interface; the textual commands above describe the pinned implementation.

Historical subscription settings
Historical subscription interface.
Historical subscription confirmation
Historical subscription interface.

Last updated

Was this helpful?