CORS error when configuring Personal Bitcoin Wallet

It’s also unclear what key I should use. I created a wallet with Jaxx and it gives me three public keys, “Account”, “External” and “Internal”.

Hi Sarmatopia, thanks for sharing these details.
We’ll look into it and get back to you asap.
I am not familiar with Jaxx, will have a look at which of these 3 public keys is recommended in this case.

Hi Sarmatopia,
Since Jaxx does not support displaying public keys, I assume you have used an external tool to find your public key address(es).
May I suggest this tutorial that indicates clearly which public key to copy:
https://help.cointracker.io/en/articles/2887147-how-to-add-my-jaxx-liberty-wallet-to-cointracker

We were not able to reproduce the issue you encountered. I will test using ‘incorrect’ public keys and if that’s the cause, improve error handling and message display in the plugin.

I hope that by following the above tutorial, and using the ‘right’ public key, you will be able to activate our plugin without further issues.
Feel free to message us by email at [email protected] if it is more convenient for you.
In any case, I will update this topic for your and others’ benefit once fixed.

Note:
For your own security, do not trust online tools.
It is recommended to download the web page at https://iancoleman.io/bip39 (used by the tutorial) as html file. Disconnect from the internet, open the html page locally in your browser and use it in this way.
Once you have the needed information, delete the html file and reconnect to the internet.

Thanks for the quick reply!

This error seems not related to the key, as Firefox says “Cross-Origin Request Blocked” (a HTTP security measure). When I add the key, the attempt by the browser (presumably the Tripe-A JavaScript) to use your API at https://moneyoverip.io/api/add_pub is blocked. The solution for that is either to add the correct CORS HTTP header or to perform the request server-to-server via wp_ajax_.

For reproducibility, I’m using Firefox 69.0.3 on MacOS.

And Jaxx does allow viewing the public keys through its own interface:

You can see all of the address/key pairs associated with your wallet at Menu > Tools > Display Private Keys.

https://support.decentral.ca/hc/en-us/articles/224342787-What-is-the-difference-between-a-public-address-and-a-private-key-

View post on imgur.com

The instructions you linked gave me the “Account Extended Public Key” which matched the Jaxx “Account” xpub key.

Now that I am re-testing I am not getting the CORS error but I am still getting the error message:

Bitcoin Payment Gateway requires wallet updates. Please update your Settings to benefit from recent security improvements.

I’m a reasonably skilled WordPress developer so let me know what you need and we can troubleshoot this together. I like your plugin (otherwise!).

Hi Samartopia,
Thanks for your feedback! I believe it would be easiest to have a Skype or Slack call (or chat). My colleague has reached out to you by email, I was in copy.

Let me know by email where to reach you for a chat ?? ?

Seems my email bounced. Please ping us at [email protected] so we can discuss this in further detail.

I have discovered possibly part of the problem. I was testing on a staging site created with wp-staging plugin: https://www.ads-software.com/plugins/wp-staging/

This added an additional login across the entire staging site, including the REST API, so would return a HTML page with “You need to login to access that page” when you were POSTing to the return_url.

Unfortunately, I’m still getting the admin message “Bitcoin Payment Gateway requires wallet updates. Please update your Settings to benefit from recent security improvements.” I’ve updated to the latest version of your plugin.

I also tested in Chrome on MacOS but there was no difference.

I’ve updated my email address to the correct one.

I added some error_log() to triplea_handle_api_tx_update() but don’t see it being called by your server (although testing with Postman confirms the logging is working).

All resolved, thank you very much!

Highly recommended.

Thanks for not giving up on us too soon and for giving us the time to release the improved version!
Hope it will serve you well!