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
Great idea @guerrerocarlos. I've been playing around with Bitcore, but I find a lot of work to get everything working correctly, but maybe I'm just not understanding some of the documentation.
With your package for payments, do you need to connect to or a run a full Bitcoin node? I checked one of the dependencies, and it seems like it is calling the insight website to get the info. But I was confused because I can't see how one would be able to "subscribe" to transaction details using the insight website. If the package uses Insight, have you experienced any issues with site outages, etc.?
Thanks!
The text was updated successfully, but these errors were encountered:
Oh, you also touch on issue I was struggling with. The bitcore documentation also recommends the HD process you describe to create the private keys and only have the public key on the "public" server. I was struggling to figure out how you transfer the public key to the node.js server that would be open to public. But from your example, it seems like you can just copy/paste as an environment variable, hard coded, etc.?
Great idea @guerrerocarlos. I've been playing around with Bitcore, but I find a lot of work to get everything working correctly, but maybe I'm just not understanding some of the documentation.
With your package for payments, do you need to connect to or a run a full Bitcoin node? I checked one of the dependencies, and it seems like it is calling the insight website to get the info. But I was confused because I can't see how one would be able to "subscribe" to transaction details using the insight website. If the package uses Insight, have you experienced any issues with site outages, etc.?
Thanks!
The text was updated successfully, but these errors were encountered: