Fix the Zcash BTCPayServer plugin in preparation for 2.1, publishing a working version of the new extracted plugin. A BTCPayServer plugin will be published both to the BTCPayServer plugin store, together with a .btcpay bundle on GitHub. An updated version of zcash-walletd will be published with tested and working Sapling support.
Orchard support can be added with a separate grant focusing on zcash-walletd. This can be worked on in parallel. Documentation will also be published, helping merchants to add ZEC to their BTCPayServer store.
The goals are to increase the amount of merchants accepting Zcash, allowing for Zcash holders to spend their ZEC more easily without having to convert to other cryptocurrencies first. Merchants will also be able to market their privacy friendly practices and better comply with privacy regulations such as GDPR, reducing the amount of data collection that they will be responsible for.
Fixes for crashes when running BTCPayServer 2.0 (work on local fork of 2.0, doesn’t need to be published as it is now obsolete with 2.1, the changes are outlined in the plugin PR below though)
I have created a btcpay-zcash GitHub organisation: btcpay-zcash · GitHub . This organisation will be jointly controlled by me (with the role of repository maintainer) and representatives of FPF and ZCG. The BTCPayServer Zcash plugin has been moved over to this organisation and I have merged the initial 2.1 fixes.
Here are the instructions for creating a local .btcpay build, that can be loaded via the Manage Plugins interface in a BTCPayServer instance:
All that is left for the first milestone now is to finish the transfer of the Zcash plugin on the plugin directory and publish the first working version of it.