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
The goal of this feature is to emulate being your own credit card provider. Here is one way you could implement it:
On the main page of zeus, under the Lightning & On-chain sections there could be a similarly styled button called 'NFC', 'Cards', 'NFC-Cards', 'LNURL Withdraw', 'NFC LNURL-w' or something similar.
Clicking this button would have 'send' and 'mange' settings.
Clicking 'send' would open a dialog where you could enter the max amount for the LNURL-w and then another button to use host-based card emulation to send the LNURL-w over NFC (disposable). https://developer.android.com/guide/topics/connectivity/nfc/hce
Could also achieve a lot of this more eloquently and natively using Offers. Great suggestion though will put it on our backlog to look into. Doing stuff with NFC cards is something we've discussed doing for awhile
Describe the feature
The goal of this feature is to emulate being your own credit card provider. Here is one way you could implement it:
On the main page of zeus, under the Lightning & On-chain sections there could be a similarly styled button called 'NFC', 'Cards', 'NFC-Cards', 'LNURL Withdraw', 'NFC LNURL-w' or something similar.
Clicking this button would have 'send' and 'mange' settings.
Clicking 'send' would open a dialog where you could enter the max amount for the LNURL-w and then another button to use host-based card emulation to send the LNURL-w over NFC (disposable).
https://developer.android.com/guide/topics/connectivity/nfc/hce
Clicking 'mange' would allow you to create LNURL-w's and write them to a NFC card. This section would also allow you to read existing NFC cards. You could also keep track of all the cards and their balances. (permanent)
https://docs.lnpay.co/api/lnurl-withdraw/how-does-lnurl-withdraw-work
https://twitter.com/BitcoinQ_A/status/1527286484385992707
The text was updated successfully, but these errors were encountered: