Oak

⬑Index

status:draft since:v0.3.5

Goal

The goal is to make it easy for Nostr users to tip other Nostr users for specific notes

• from any Nostr client¹
• non-custodially²
• privately³
• using standard LNURL

Definitions

Owner: the Nostr user from whom the bot accepts tip commands

Pairing: the process by which the Owner info (pubkey, relays) is configured in the bot

Architecture

The bot has an LN client and a Nostr client. The LN client has sufficient permissions to pay invoices.

The bot's Nostr client listens for the owner's NIP-25⁴ reaction events. To do that, the bot starts with one or several "seed-relays" which it queries for possible NIP-65 Relay List Metadata⁵ events sent by the owner. If some are found, the bot will listen on those relays. If none are found, the bot will listen on the seed relays defined during pairing.

Each time the bot sees a positive reaction⁶ from its owner, it:

• looks up the author of the reacted-to note
• looks up the profile of that author
• looks up the lud06 (LNURL) and lud16 (LN Address) fields in the profile
• if any of them is present, it uses its LN client to send a tip

The LN tip can include a reference to the reacted-to note in its memo, such as "Tip for your note1abc...".

1. ^{^} From any client that supports NIP-25 Reactions, such has likes
2. ^{^} Using direct commands to an LN node
3. ^{^} Without publishing Nostr notes with payment details
4. ^{^} https://github.com/nostr-protocol/nips/blob/master/25.md
5. ^{^} https://github.com/nostr-protocol/nips/blob/master/65.md
6. ^{^} Any reaction where the content is a + or an emoji is considered a positive reaction. NIP-25 also supports negative reactions, where the content is -. These are ignored by the bot.