Blocktronics in Telegram

@BlocktronicsBot brings Blocktronics into Telegram.

Ask it for a token with /token AERO and it answers with a picture first: the token's card, then its read word with the reason, a few key figures and the day they run to, with buttons to open the token, swap or set an alert on it.

/today and /attention send the market's day and the tokens where several signals meet; /vs puts two tokens side by side and /learn sends a topic from this hub with its card. In any chat, type @BlocktronicsBot and a token to share its card there.

Link the chat to your account (Connect my account in the bot, or Telegram on your account page) and your alerts arrive there with their chart. Signals on your watchlist and a morning brief at 08:00 UTC are on from the start; each turns off with one tap.

In a group, everyone gets the public cards. A paid read is paid by whoever asks, unless a linked admin sponsors the group with /sponsor and a daily cap; each charge posts a receipt in the group.

1. 1

   A token's answer: its card, drawn by the same renderer as the MCP's, then a caption from the site's own read of the token.

2. 2

   Each picture is drawn once for its card, token and the day its data runs to; after that Telegram's own copy is sent again.

3. 3

   Who pays a paid read in a group: the sponsor, while the asker may spend and today's total stays within the cap; otherwise the asker, from a linked account.

   payer = sponsor if (spent today + price ≤ daily cap), else the asker
4. 4

   Alerts reach a chat only once it is linked to the account; a chat Telegram refuses is unlinked and never retried.

HighShape, not data

Several alerts in your chat at once: several of your conditions were met; each message names its token and its numbers.

LowShape, not data

A quiet chat: none of your alerts met its condition; the morning brief still comes at its hour.

RisingShape, not data

A group's spend today nearing its cap: past it, each asker pays for their own reads.

FallingShape, not data

A new UTC day: the group's cap counts from zero again.

Evidence in the data, never advice

• A picture shows the day its data runs to; a figure the token doesn't have shows as a dash, never as zero.
• In a group the bot sees only commands and replies to it, so plain chat there goes unanswered.
• Readout and Outlook cost credits in the bot as on the site; while paying with credits isn't on yet, the bot says so instead of answering.