This is something i feel that could be built by any coder familiar with nostr kinds.
If I were to do this Id build a service around it and probably base fees around both a time frame (e.g. base daily/monthly cost since its a monitoring service), and a fee per event handled.
Theres quite a bit of functionality needed to support such from the configuration and top up side
- auth with nostr and/or lnurl auth
- add/edit config (define rules for... relays to listen/check, pubkey for events to listen to references, phrases to look for in original post, phrases in reference posts, amount of sats to zap, comment to include in zap, start time, end time, limit number of posts to zap)
- check balance, add funds
and then extend with more rules and
- list campaigns (for multiple per acct)
- reports
Amazing. I know it can be done. But it's a complexity issue. Can't be spun up in a single day, probably. 🤔
for a full service, no.
but for a single pass script run locally to zap possibly. this may be viable if you run your own LND node and dont mind using command line
My friend, I have been a GUI user for too long. CLI is a challenge, for which I feel I am ready.
how many events are you typically handling every day for zapping?
Let's aim high. Say 50 to 100. My project is growing.
Yeah. Ideally bot would handle unlimited or up to a given amount. At the point you are at youre experiencing the labor cost side that doesnt scale well. A bot makes sense, just needs to be affordable to still be viable
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed