CRATEFIELD
Get started with Harness Join the waitlist

module-telegram

Telegram as a channel: the webhook, account linking, and consent buttons that can deny anything and only arm what moves value.

With cargo

cargo add cratefield-module-telegram
crates.iodocs.rsSource

What it is

module-telegram.

Telegram in a Cratefield venture (issue #679): the secret-token webhook, account linking, and consent buttons under one rule the module does not bend. A tap in Telegram can deny anything, approve anything harmless, and only arm — never finish — anything that moves value. Mounted at /v1/telegram over four tables, with adapter-telegram carrying the wire.

From the crate’s own README.

History

Changelog.

From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 2 versions recorded, newest first. Every published version is on crates.io.

  1. 0.1.2

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core, cratefield-adapter-telegram, cratefield-module-notifications

  2. 0.1.1

    crates.ioRelease

    Other

    • updated the following local packages: cratefield-core

    Added

    • First release, 0.1.0: Telegram in a venture, mounted at /v1/telegram. It verifies the secret-token webhook, links Telegram accounts with one-time codes, and sends consent buttons that can deny anything and approve anything harmless, but only arm a value-moving action until the owner confirms it with a passkey. With the notifications feature it is also a module-notifications channel (#764).

One of 76 crates in the harness, all of them MIT and all of them in one repository.

Join the waitlist All modules