feat: zaps #78
No reviewers
Labels
No Label
1000k
100k
10k
200k
20k
500k
50k
5k
75k
backend
blocked:design
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
P1
P2
P3
question
scope:intl
scope:nip
scope:query_tracing
scope:ux
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Kieran/snort#78
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "zaps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Deploying with Cloudflare Pages
140d87e
View logs
Awesome!
You can put this in Util?
Follow-up PR implements zap sending (WIP) and has some improvements on this https://github.com/v0l/snort/pull/80
We should also validate that the
ZapReceipt
pubkey matches the pubkey listed in the recipients lightning service, otherwise i can just fake zaps to peopleThis is wrong, were not using this format anymore, can you revert to previous?
The
description
tag contains the zap note and the hash of this should match the description hash of the invoice