This is the flow I came up with. It saves a new Private Key to the database un-encrypted for every transaction, which sounds like a bad idea. However, the database is encryted anyway and those keys will hold coins for a little amount of time, as the funds will be moved to the cold wallet as soon as the background monitoring task detects that the payment was fulfilled. I could also use a encrypted field in the DB to save the private key, but I don't think it's necessary.What do you think? Is this a nice, safe way of accepting cryptocurrency payments?I'm not interested in using BTCPay or other solutions because:BTCPay does not support MoneroI have more control over this simple payment system than the whole complex BTCPay architecture, which does have more space for flawshttps://i.redd.it/t8z3vjlwfbw21.png
Submitted May 05, 2019 at 11:12AM
No comments:
Post a Comment