Allow comments for LNURL-PAY invoices #65
Labels
Clear labels
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
security
ui/ux
wontfix
integration
btcpay
integration
discourse
integration
ejabberd
integration
email
integration
ldap
integration
lndhub
integration
mastodon
integration
nostr
integration
remotestorage
Something is not working
Graphic/visual design
Config, builds, CI, deployment, etc.
Documentation
This issue or pull request already exists
Improving existing functionality
New functionality
Dive in, and start contributing
Something to consider
Not a bug
Small contribution
Medium contribution
Large contribution
Currently not actionable
Manual IT ops activities
Looking for an answer
release
major
release
minor
release
patch
All your base are belong to us
User interface, process design, etc.
This won't be fixed
Milestone
No items
No Milestone
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/akkounts#65
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Allows senders to add a short message to payments, which will be stored as invoice memo by LND/LndHub, and then should be shown in the receiver's wallet so they can know where a certain payment came from, when they didn't actively request it.
https://github.com/fiatjaf/lnurl-rfc/blob/luds/12.md
2418acd727to4c51b9c966This branch is running in production now, and actually working (so you can review it by using it).
It requires another LndHub change, which I'm going to propose separately (currently just manually changed on the server).
I created a new repo for our LndHub fork (it was still using @bumi's repo with a manual fix for the onchain txs), and pushed my memo additions to it:
9b81cc6287That repo is currently running on
bitcoin-2(Chef PR incoming).nice addition!
you should switch to the Go version :)
How? You're very welcome to help with that! I'd love nothing more than a clean database for those transactions and balances.
We'd "only" need to migrate the users. There is no automation for that yet. the rest is exactly the same.
Will see when I get to writing a migration script. But I will likely start only with the balances and not indiviudal transactions.
Balances-only is fine. But people do have balances and some do use their accounts, so we have to migrate those.
There is currently no way to see who has which balance, since we haven't written a front-end for that Redis data and LndHub doesn't offer one.