Zaxounette
commented
3 years ago Developer Call N°1 Notes
Attendees: @Kukks , @NicolasDorier , @rockstardev , @pavlenex , @dennisreimann , @Zaxounette
The postGRE version used by BTCPay is in end of life in one month. Nicolas is pushing to get this updated today or tomorrow, PR already available
- Entails a bit of risk since we need to move the database
- There is also risk in defaulting the new version to new installations
- For this we could use two different fragments
Joinmarket added to the btcpay docker image. Joinmarket still requires extensive CLI knowledge and is not usable by everyone at this point.
- JoinInbox by Openoms is available as a simplified UI that can be included in BTCPay as well
- Nicolas will explore this further
- We also want to provide sain defaults
- While still enabling the user to customize the configuration so that every instance launched doesn't have the same exact configuration
- Joinmarket doesn't use ENV variables for configuration, but only through the config file
LNURL branch is being worked on by Dennis #2804 includes the basis of LNURL - code is big, but already broken down #2897 includes the above code and Dennis polished the UI as well
LN payout support #2517
- LNURL pay-request was used for this feature
- Custom LNURL library included
Dennis to finish the LNURL PR's before moving on to the LNBank PR
- Would also like to see the LND on-chain wallet being possible to use as a hot wallet inside BTCPay
- Would need the ability to import wallet by it's seed, as well as ability to import an Xpriv key
- We would need to directly fetch the seed
- Still a possible issue with the gap limit for the Lightning node itself
- Entails privacy breaking issues, as well as problems with funds reconciliation between the LN wallet and BTCPay wallet
- Unknown what happens when we try creating multiple wallets in the LN-cli
- Dennis to work on this and find a solution, and Rockstar to be the cheerleader
Other implementations use the bitcoind on-chain wallet, like LDK or eclair for example.
- Making a solution compatible with the different implementations needs to be explored.
- If we build support for Xpriv support, it shouldn't be explicitly publicized, but given as a solution to support questions and disaster recovery situations
- We can build this as an obfuscated solution, like the Bitpay invoice converter was in the past
In generally, we rely on third-party tools to do all LN related things.
- One other effort Dennis wants to push is make available the LN balance in the BTCPay Server interface
RBF and CPFP when?
- Next step in Nicolas's task list is payment notifications
- After that task, CPFP
Lightning Address UI
- Dennis working on this so that Kukks can integrate the LNURL config into this restructure
Consensus on scheduling these calls every two weeks.
Agenda
After a while, we're reviving our dev calls. The calls will be fixed time, bi-weekly with a chair and note-taker. The goal of dev calls is to be a focused 1 hour discussion around specific pull requests and issues targeted for the next release of the BTCPay Server.
The goal of dev calls isn't to provide support for custom integrations, though developers are more than welcome to discuss that once we're done with the call on an after-call.
The agenda should be determined up-front.
Agenda
Check your timezone
https://everytimezone.com/s/04c65d89
Join the call
https://meet.jit.si/btcpayserverdev
Calendar invite
Subscribe to the BTCPay Server calendar. More info here. ).