Currently, we have the fields:
Master key (XPUB): text
Use SegWit: on/off
Culture/Currency: Selection list
This should be changed to the new workings of the application. Initially, settings fields can be:
OpenNode API key - User should paste the API key with "invoice permission" generated on OpenNode.co.
Allow on-chain payments - OpenNode generates addresses for both LN invoicing and on-chain payment and returns both on the API "Create charge" (https://developers.opennode.co/reference#create-charge). Initially, only LN payments needs to be supported by later on-chain payments could be supported also. LN payments are usually preferred because of lower fees and faster confirmation.
Reference Currency - Selection list. Initially, only BRL and USD need to be available. Later this could be expanded to the whole list returned by https://api.opennode.co/v1/currencies.
Language - Initially, LibrePay is focused on Brazilian users (Portuguese language). But localization and multi-language support should be thought from the beginning. The first additional languages to be implemented after the app is stable will be English and Spanish.
Currently, we have the fields:
Master key (XPUB): text
Use SegWit: on/off
Culture/Currency: Selection list
This should be changed to the new workings of the application. Initially, settings fields can be:
OpenNode API key - User should paste the API key with "invoice permission" generated on OpenNode.co.
Allow on-chain payments - OpenNode generates addresses for both LN invoicing and on-chain payment and returns both on the API "Create charge" (https://developers.opennode.co/reference#create-charge). Initially, only LN payments needs to be supported by later on-chain payments could be supported also. LN payments are usually preferred because of lower fees and faster confirmation.
Reference Currency - Selection list. Initially, only BRL and USD need to be available. Later this could be expanded to the whole list returned by https://api.opennode.co/v1/currencies.
Language - Initially, LibrePay is focused on Brazilian users (Portuguese language). But localization and multi-language support should be thought from the beginning. The first additional languages to be implemented after the app is stable will be English and Spanish.