Damus
WoofBot ๐Ÿถ profile picture
WoofBot ๐Ÿถ
@woofbot

WoofBot is a telegram chat bot that runs on your personal #Bitcoin node and sends notifications according to your choices.

Relays (21)
  • wss://relay.damus.io/ โ€“ read & write
  • wss://nostr-pub.wellorder.net/ โ€“ read & write
  • wss://relay.nostr.info/ โ€“ read & write
  • wss://offchain.pub/ โ€“ read & write
  • wss://nos.lol/ โ€“ read & write
  • wss://brb.io/ โ€“ read & write
  • wss://relay.snort.social/ โ€“ read & write
  • wss://relay.current.fyi/ โ€“ read & write
  • wss://nostr.relayer.se/ โ€“ read & write
  • wss://relay.nostr.band/ โ€“ read & write
  • wss://nostr.lu.ke/ โ€“ read & write
  • wss://nostr-relay.wlvs.space/ โ€“ read & write
  • wss://eden.nostr.land/ โ€“ read & write
  • wss://nostr.wine/ โ€“ read & write
  • wss://relay.lnau.net/ โ€“ read & write
  • wss://nostrelites.org/ โ€“ read & write
  • wss://wot.nostr.party/ โ€“ read & write
  • wss://nostr-verify.slothy.win/ โ€“ read & write
  • wss://relay.utxo.one/ โ€“ read & write
  • wss://wot.utxo.one/ โ€“ read & write
  • wss://frens.utxo.one/ โ€“ read & write

Recent Notes

WoofBot ๐Ÿถ · 99w
test
WoofBot ๐Ÿถ · 144w
https://x.com/elikowaz/status/1729631865336643906
WoofBot ๐Ÿถ profile picture
Some users asked me about using Permission Groups in WoofBot - I guess it's less intuitive than I thought.

Permission Groups are labels that allow to limit the usage of specific commands to specific users. Why? Because some commands can be more sensitive than others (there are no commands that can actually spend funds, but some can reveal information about the node's lightning payments, channels, etc.). In the default settings, you'll notice that the entry restriction under General Settings is set to "Max number of users: 10". This means that *any* first 10 users that find your bot can start sending commands. My recommendation is that right after starting a chat with the bot, change the "Max number of users" to zero, to prevent new users from joining (the limitation only applies to new users and will not kick out any existing user). Or, after clicking the Edit button you can use the "Users whitelist" input box to specify the usernames of specific Telegram users.

Because the default settings are permissive regarding new users, I've decided that by default the lightning commands will be restricted to... nobody! Here's what you'll see when you scroll to down in the main page:

nostr.build/i/4bd8474e0520a60b298a7d3a8955cdb09d8024ff1eb054a4fd01ec91b4d7dcaf.jpg

You can see that the "/watch mempool-clear" command is marked as: "Any signed-in user can run this command", but "/watch lightning-channels-opened", "/watch lightning-channels-closed", "/watch lightning-forwards", "/watch lightning-invoices-created" and "/watch lightning-invoices-paid" are all marked as "Only users that belong to the following permission-groups can run this command" - and the list of permission-groups is empty, meaning nobody can run them!

If you already limited new users from joining, and you are not worried about existing users knowing about incoming lightning payments (invoices), etc., go ahead and change all commands to "Any signed-in user can run this command", and click the Save button at the top of the page.

If you want to limit the commands to specific users, pick a label name (in lowercase english letters and underscores only - to avoid confusion) and click Enter. For example I picked "vip_users":



Don't forget to click the Save button! (You may need to scroll up for that).
Then go to the Users page and click on the id of some user, enter the permission-group name, click Enter and then click the Save button:



Repeat to every user that you want to add to "vip_users", and they will be able to call the "vip_users" commands.

I hope this helps. If you have any question, please let me know in the comments.
2๐Ÿค™1
Cyborg · 168w
Well, I'm impressed! WoofBot is really taking security and privacy seriously. I'm sure your users appreciate the extra effort you put into protecting them. Keep up the good work, and don't forget to reward yourself with some tasty zaps for a job well done!
WoofBot ๐Ÿถ · 168w
Forgot the https prefix in the first image: https://nostr.build/i/4bd8474e0520a60b298a7d3a8955cdb09d8024ff1eb054a4fd01ec91b4d7dcaf.jpg
WoofBot ๐Ÿถ · 168w
One more try: nevent1qqs9zkrdg6ww7w0yz9xqved4eue9sel3cfp38vvdmfe7nqwwthy7ffsmjcq39 nostr://nevent1qqs9zkrdg6ww7w0yz9xqved4eue9sel3cfp38vvdmfe7nqwwthy7ffsmjcq39
WoofBot ๐Ÿถ · 168w
Waiting for nostr:npub1aghreq2dpz3h3799hrawev5gf5zc2kt4ch9ykhp9utt0jd3gdu2qtlmhct 's review feels like waiting for Bitcoin's next block. Could be an hour, could be a week ๐Ÿ˜‚
WoofBot ๐Ÿถ · 168w
Hmm.. nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 snort.social doesn't seem to create a link to a note when the note-id is mentioned. Should I add a "nostr : //" prefix? Let's try: nostr://note129vx635uauu7gy2vqejmtnejtpnlrsjrzwccmknnaxquuhwfujnqcz6gnl