Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added sequence diagram for github booster to the README #19

Merged
merged 3 commits into from
Aug 27, 2024

Conversation

dhalsim
Copy link
Collaborator

@dhalsim dhalsim commented Aug 18, 2024

Starting with the Nostrize Booster feature for Github.
Added sequence diagram.

Will need a special relay for storing zap/boost events, possible in a different repo

In the Extension, we can write the code as if this relay exists.

There may be a need for a new setting such as, publish zap/boost events only to nostrize relay. otherwise all the relays would get the zap events but I don't think it is necessary

I need a lightning node too, but it is related to the relay code, not here

After getting the boost events from the relay, should transform it into Boost format:

    {
      type: "repo",
      from: "nostrize",
      to: "nbd-wtf/nostr-tools",
      created_at: agoInSeconds({ hours: 34 }),
      amountSats: 21000,
      message:
        "One of the coolest nostr software out there 😎 a must have for every client developer",
    }

@dhalsim dhalsim merged commit 492da38 into main Aug 27, 2024
@dhalsim dhalsim deleted the boost/system-design branch August 27, 2024 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant