You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Wallet of Satoshi and Aqua Wallet abstract the need to understand with what you are paying. Goal should be iin general that users fund a wallet by one of the supported types (LN, onchain, Liquid, Minnts and so on) and can spend it on whatever comes along.
Generating and reading as many payment methods as possible will make LNbits more interoperable
and ease the overall UX and abstract the asset from the user.
This is expecially interesting for any sort of checkout (tpos, nostrmarket, satspay/wordpress plugin)
With this is mind concerning the technical solution this FR intends to push supporting and generating Unified-QR-Codes (BIP21) on LNbits.
For clarification: BIP21 means only 1 QR on one screen instead of two.
Would be wonderful if BIP21 also works for Boltcard extension and voucher.
Prerequisite : onchain wallet extension is installed and has a (synched when its about withdrawing) onchain wallet.
SatsPay now
Unified QR codes hold additional data, meaning they can become large and cause scanning difficulties with some devices. Therefore preferably this is mixed with introducing BOLT12 to still allow presenting slim QRs !
Especially for Boltcard that might be a need
Static payment UQR that can be presented, printed, written to a NFC-tag or used in other extensions
The checkboxes in those extensions` config part should leave in favour of an attional combobox for the onchain wallet., onchain can be NULL. Where both are given present in consequence a UQR iadditionally / instead.
Important
Tip from the BIP21/12 webpage (https://bitcoinqr.dev/) : If its a zero-amount-invoice and the user switches between the "units" to pay delete the amount to prevent expensive user mistakes.
Describe alternatives you've considered
Reading has to be supported for the old and new QRs. There will always be wallets, which cannot handle them. Still it should be the goal so a starting support is a push in that direction for others, too
Animated QRs are an alternative solution that should be more widely supported than this BIP/s
Give a hint notice on the Onchain-QR tab when the fee is lower onchain than on btcln (sic)
With the DFX extension that could even include asynchronous fiat on/offramps
With the Cashu extension also mint-QRs could be included
The existing tasks of core and extensions (e.g. Scrub + Split + lnurldevices + Boltz) may not get broken by this change.
Additional context
General tips on implementing BIP21 and code-snippets for test and production https://bitcoinqr.dev/
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
Wallet of Satoshi and Aqua Wallet abstract the need to understand with what you are paying. Goal should be iin general that users fund a wallet by one of the supported types (LN, onchain, Liquid, Minnts and so on) and can spend it on whatever comes along.
Generating and reading as many payment methods as possible will make LNbits more interoperable
and ease the overall UX and abstract the asset from the user.
This is expecially interesting for any sort of checkout (tpos, nostrmarket, satspay/wordpress plugin)
With this is mind concerning the technical solution this FR intends to push supporting and generating Unified-QR-Codes (BIP21) on LNbits.
For clarification: BIP21 means only 1 QR on one screen instead of two.
Would be wonderful if BIP21 also works for Boltcard extension and voucher.
Prerequisite : onchain wallet extension is installed and has a (synched when its about withdrawing) onchain wallet.
SatsPay now

Unified QR codes hold additional data, meaning they can become large and cause scanning difficulties with some devices. Therefore preferably this is mixed with introducing BOLT12 to still allow presenting slim QRs !
Especially for Boltcard that might be a need
Write a UQR with LNbits
The checkboxes in those extensions` config part should leave in favour of an attional combobox for the onchain wallet., onchain can be NULL. Where both are given present in consequence a UQR iadditionally / instead.
Important
Describe alternatives you've considered
The existing tasks of core and extensions (e.g. Scrub + Split + lnurldevices + Boltz) may not get broken by this change.
Additional context
The text was updated successfully, but these errors were encountered: