Harmony One AI Bot

Telegram wallet

http://harmony.one/telegram-wallets

Env variables

Env variable name	Required	Default	Description
TELEGRAM_BOT_AUTH_TOKEN	true	-	Telegram bot auth token
TELEGRAM_API_ID	true	-	Telegram API id
TELEGRAM_API_HASH	true	-	Telegram API hash

Bot paid features

Bot paid features includes audio-to-text translations, AI image generator, QR code generator, etc.

Mission

The bot should support payments in ONE token

Requirements

Each bot user (telegram user) should be mapped to a deposit blockchain account.

Deposit account must have the following properties:

1. Each account should be unique to the Telegram userId
2. Deposit address should be available for the user and the bot
3. Bot should be able to transfer ONE tokens from deposit address as a payment
4. Private key of deposit account data should not be stored in the persistent storage

Solution

Each telegram userId can be mapped to the deposit account with sha hash function. To make it impossible to create the same account, knowing the mapping algorithm, we can add a secret string on the bot side.

Example of creation of the deposit account:

const privateKey = web3.utils.sha3("<BotSecret>_<TelegramUserId>");

const account = web3.eth.accounts.privateKeyToAccount(privateKey);

console.log(account.address); // 0xd10063CFC4fEea79367Be6d8C1eC6a2251ebCAD1

• BotSecret is a random string stored in the bot RAM
• TelegramUserId is a 8-digit number representing the telegram userId

Pros:

• Almost unique mapping userId -> deposit account (sha3 collisions probability is very low)
• Private key is not stored in the persistent storage
• Deposit account can be computed by bot on the fly, based on secret from RAM and telegram userId from the request

Cons:

• Deposit blockchain account created in centralized way. Considering that the user doesn't need this account to store tokens, but only to refill for the bot's services, this shouldn't be a problem.

Payment flow