Issue with telegram Bot

[hsdredgun]

Description
After upgrading to LND v0.21.0-beta.rc1, the BOS Telegram bot is unable to fetch payments. LND v0.21.0 introduced a migration of the payments database from the KV store to a native SQL (SQLite) backend (kv_payments_migration, schema version 14).

Environment

• LND version: 0.21.0-beta.rc1
• BOS version: 20.1.4
• DB backend: SQLite (db.backend=sqlite, db.use-native-sql=true)

Steps to reproduce

1. Upgrade LND from v0.20.x to v0.21.0-beta.rc1
2. Allow kv_payments_migration to complete
3. BOS Telegram bot no longer returns payment history

Expected behavior
BOS Telegram bot fetches and displays payments as before.

Actual behavior
Payments cannot be retrieved via the Telegram bot after the SQL migration.

P.S. Additionally, the bundled lightning library crashes with ExpectedEventTypeInChannelSubscription on subscribe_to_channels.js — LND v0.21.0 emits a new gRPC channel event type that the current lightning package does not handle, causing the bot to crash and reconnect every ~3-4 minutes.

[hsdredgun]

I was able to fix the bots with this patch: ( here is a summary step from the robot 🤖)

Bug 1: Bot crashes every ~3 minutes with ExpectedEventTypeInChannelSubscription

Root cause: LND 0.21 added a new FULLY_RESOLVED_CHANNEL event type that the lightning package doesn't recognize. It arrives as a raw integer, so
update.type.toLowerCase is undefined, throwing an error and killing the subscription.

File: lnd_methods/offchain/subscribe_to_channels.js

Patch (two separate lines, find and replace each):

// BEFORE (line ~190):
return emitError(asError('ExpectedEventTypeInChannelSubscription'));

// AFTER:
return; // skip unknown event types (LND 0.21 compat)

// BEFORE (line ~210):
return emitError(asError('ExpectedEventDetailsForTypeInChannelSub'));

// AFTER:
return; // skip unknown event details (LND 0.21 compat)

▎ Note: BOS has this file in 10 nested locations (nested node_modules inside ln-telegram, paid-services, goldengate, ln-accounting, probing). All copies need
▎ to be patched.

---

Bug 2: SubscribeChannelBackups fires constantly — backup file sent to Telegram every few minutes

Root cause: In LND 0.21, SubscribeChannelBackups fires on every HTLC/payment event (not just channel open/close). The backup content is genuinely different
each time (it includes HTLC state), so content comparison doesn't help.

Correct fix: Compare the channel.backup file's mtimeMs on disk instead — this file only gets written on real channel open/close events.

File: telegram/start_telegram_bot.js — find the subscribeToBackups block and replace:

// BEFORE:
const sub = subscribeToBackups({lnd: node.lnd});

subscriptions.push(sub);

sub.on('backup', ({backup}) => {

// AFTER:
const {statSync: _statSync} = require('fs');
let lastBackupContent = (() => {
try {
return _statSync(process.env.BOS_DEFAULT_LND_PATH + '/data/chain/bitcoin/mainnet/channel.backup').mtimeMs;
} catch(e) { return null; }
})();

const sub = subscribeToBackups({lnd: node.lnd});

subscriptions.push(sub);

sub.on('backup', ({backup}) => {
const {statSync} = require('fs');
try {
const {mtimeMs} = statSync(process.env.BOS_DEFAULT_LND_PATH + '/data/chain/bitcoin/mainnet/channel.backup');
if (mtimeMs === lastBackupContent) { return; }
lastBackupContent = mtimeMs;
} catch(e) {}
// rest of existing backup send logic unchanged...

Result: Backup is only sent to Telegram when the channel.backup file actually changes on disk — i.e., on real channel open/close events.

---

Both patches are workarounds until the lightning npm package officially supports LND 0.21's updated gRPC event types and backup subscription behavior.

[alexbosworth]

i pushed a change, do you still see the same issue?

[hsdredgun]

Not working, no forwards showing and connected to every few min is still there, I have give a patch to ziggie please review it. I tested it for 5 days no issue.