[alexg]

Hi, this was how it was in a much earlier version when the plugin was in its infancy and I got a large number of requests to do the UI as it is now.

The only thing I could do is provide an option between the two ways of doing this.

I cannot promise you that I can do this any time soon as it is a low priority thing compared to other tasks. As it is, the UI clearly states that the fees are subtracted from the amount so I do not believe there is any source of confusion.

Thank you for sharing your thoughts on this.

kind regards

[alexg]

Hi,

Thanks for the suggestion. Unfortunately this is not very easy to do.

As it is, withdrawals are done with the [wallets_withdraw] shortcode, and intra-user transfers are done with the [wallets_move] shortcode, which will be improved soon at the upcoming 3.0.0 release. If a user attempts to withdraw to a deposit address of the same system, the plugin performs in the backend an internal transfer (aka move) instead. The frontend has no way to know which addresses belong to different users.

I would suggest that you use your page’s text to inform users about this. You could encourage them to use internal transfers or otherwise notify them that if they are sending to a deposit address to another user on the same site, no blockchain transaction will occur.

kind regards

[alexg]

What page does the referral link take you to?

Normally adding a get parameter to the main URL for your site should still take you to the homepage.

1. Can you email me a screenshot of that page or otherwise describe the page you are being redirected to?

2. Does the URL in the address bar change to something else?

Thanks.

regards

[alexg]

Thank you for reporting your findings.

As I said before, I do have plans to improve frontend performance. This is already scheduled for a later release.

regards

[alexg]

Yes, this happens if you attempt to display a faucet for a coin whose coin adapter is not online.

Glad you solved it.

[alexg]

The issue with the checkbox in multisite is now resolved in 2.13.7.

[alexg]

SSH tunneling is needed if you have set up a full node on a machine different than the one you are running WordPress on, i.e. for the connection to the JSON-RPC API of Bitcoin core and friends. (for more, see here: https://en.bitcoin.it/wiki/Enabling_SSL_on_original_client_daemon )

It is not needed or recommended for the cloud wallets.

I do not have plans to integrate the plugin with GoUrl.

[alexg]

I do not have plans to implement either POW or POS mining features.

I do want to create a plugin that lets users invest and receive interest according to settings that the site admin chooses.

However it is unlikely that I will find time to do something like that for the time being. There are more pressing tasks at the moment.

kind regards

[alexg]

Thanks for noticing, I will fix the issue with the checkbox in multisite.

Another thought about your performance issue: Does your performance improve if you reduce the number of coins enabled in the CoinPayments adapter? Enabling too many coins can slow down the frontend when you use that adapter. This is something I plan to improve on.

[alexg]

Glad to be of help, megeanwasson 🙂

best of luck with your project!

[alexg]

Unfortunately no, I have not put together a guide on how to do ssh tunneling to a full node wallet.

To clarify, this is recommended practice from the Bitcoin developers and is only needed when the wallet runs on a different server than your WordPress installation. If they are both on the same machine, tunneling is not needed.

I will try to add step-by-step instructions in the documentation when time permits. In the meantime, you could have a look at the following instructions I found with a Google search:

https://gist.github.com/EnigmaCurry/bdd9fd28d7a73fe52eb4

P.S. In the future can you please open a new thread for each distinct request? This helps keep the forums clean for people who look for similar info in the future. Thanks.

[alexg]

Hello,

You could try contacting the developer of that code.

regards

[alexg]

Hello,

The code you mentioned above is correct and does not cause any problem as far as I can tell.

You have another error in your JavaScript console, coming from a file titled clamlive.js:

TypeError: wrapper is null clamlive.js:8:2

kind regards

[alexg]

Hello again,

Yes, you have already requested this and I have implemented an on/off switch. It will be out today with the next release.

I highly doubt that this will improve your site’s performance.

If you have a large number of users, it is very likely that the delay is caused by the get_users_info JSON call. If you do not need to use the [wallets_move] shortcode, then simply disable the send_funds_to_user capability from your admin menu. This is needed only until I can improve the way [wallets_move] works.

Alternatively, it might be wise to reduce the number of coins that you have enabled in the CoinPayments adapter.

kind regards

[alexg]

Thanks for the clarification.

The CoinPayments adapter is a coin adapter for the Bitcoin and Altcoin Wallets plugin. It cannot be used as a payment gateway.

Are you using the WooCommerce payment gateway available here? https://www.dashed-slug.net/bitcoin-altcoin-wallets-wordpress-plugin/woocommerce-cryptocurrency-payment-gateway-extension/

[Author]

Posts