Kick them out if they are not in the list.

Once a user entered, he'll be removed from the list. i.e. if he changed his name, nobody else could enter with his username.

See discussion: https://twitter.com/andyorange/status/1565289782002982912

under Global Watches.

I use woofbot personally to watch my own addresses. But I also want to use it in a group so we can watch certain entities BTC movements.

Any interaction I have with the bot in a group is the same as if I interact in a direct message. If I restart the bot in the group, messages go to that group instead of me. Ideally the group should be a new user in the dashboard/console. I'd love to have group watchlists, etc separated from individuals with the bot.

in addition to the channel ids

Instead of setting the relevant fields to false, these functions delete the field.

There are probably no side effects, but this breaks the mongoose modeling.

A migration is needed too.

WatchReboot, UwatchReboot, WatchNewBlocks, UnwatchNewBlocks, Links - still find the user with the telegram id (ctx.from?.id) but it was already discovered and is given as a second param after ctx.

The Quit function also follows this, but maybe we should keep it this way (using the telegram-id) because it is special indeed.

Whether it is connected to LND or not.

If CoinGecko is not responding when the first price-watch is set, it could theoretically take a lot of time to respond to the user.

Make App work with Start9.com

/about returns unknown version, so there might be other problems too.

Use telegram buttons to allow user to autocomplete something like "/unwatch address xyz".

The app seems to stop scanning new blocks, and the Queued Tasks is stuck at 2.

Probably due to a flood of events when the node becomes online again.

Do some operation if the user is not responding to any message (sent periodically) for a certain time.
Any message from the user could restart the intervals.

The operation could be sending a Telegram message to a specific user (assuming the user initiated a chat first - I don't think a Telegram bot can initiate chats with random users).
The operation could also be broadcasting a given transaction.

Time could be measured by the current block-height - in case we don't trust the computer's clock.

Get a notification when there are no-blocks for a given number of hours (i.e. 24 hours).

On the main page, alongside the command list it would be nice to see if the command has any mandatory or optional parameters. It will be easier than just having to do the command first on Telegram to get the answer for that.

Allow to associate every user to one or more groups.

Allow admin to limit each command to:

• Everyone
• None
• Specific groups

(Unsubscribe commands should always be open for everyone).

This will be useful in the future to prevent users from getting notifications about sensitive information (i.e. lightning node earning fees).

See: bitcoin/bitcoin@085b3a7

When a command that needs parameters is executed without parameters, we need to reply with a message asking for parameters and expect the user to reply to it. If the user does reply - execute the command with those parameters.

All the short commands can then be removed.

Spending from a UTXO of a transaction that is still in the mempool, could lead to sophisticated double-spend attempts (instead of spending the current UTXO twice, the attacker can try to spend the previous transaction's UTXO).

The current mechanism doesn't cover this - it only watches for transactions that conflict with the watched transaction-id, not with its parent transaction. It can get incredibly complicated to watch all the chain of transactions, but a warning about this kind of transaction would be good enough.

Hi! I'm building @runcitadel, a FOSS Umbrel alternative. I'm planning to integrate WoofBot there. I got it running based on your Umbrel PR. Would you be okay with me adding @woofbotapp to @runcitadel, which is licensed under the GNU AGPL?

Doesn't show if the user started watching lightning invoices being created and paid.

Right now the price watch will only be deleted after the next time it triggers (due to price change), and the handler finds out that the user no longer exists.

All the "00000000000" could be replaced with "0...0"
Even if we're on test environment and there are no zeros in the prefix, it's ok to begin block ids with "0...0".

This should also simplify the mempool-links command

Having a command to automatically see if the node has receive any on-chain or lightning transaction (maybe with an option to see the routing fees that have been earned)

A '$' is missing before the {BotCommandName.Links}:

Let the admin set some other server for /mempoollinks than "https://mempool.space"

After setting the token there were two responses for each message/command.

Maybe a new Telegraf instance was created but the old one kept running.

Would be best in each handler to check that the notifying bot is the active one, and to carefully clear event listeners from the old Telegraf instances.