[alexg]

Hi,

You have brought up a number of points, let me answer as many of them as I can:

First, I do not know if you can use the block.io service over tor. At least the API URL doesn’t seem to be contactable from within tails. That would explain why it didn’t work for you.

The CoinPayments adapter can possibly work with the curl parameters that you mentioned, I haven’t tested it though. If you have tested it, I would very much like to know what you found, otherwise I will try to make it work myself at some later time and release a patch if needed.

The process to switch to another adapter is as follows (I will add it to the FAQ):

1. Deactivate the first coin adapter
2. Delete your deposit addresses. Simply do a
DELETE FROM wp_wallets_adds WHERE symbol IN ('BTC','LTC','DOGE');
in your SQL console. This will let new deposit addresses to be generated by the new adapter. If you do not do this your deposit addresses will be from the old adapter/wallet.
3. Install and activate the new adapter.

The CoinPayments adapter is well-tested over clearnet. Can you confirm that you can use it over clearnet? That would eliminate the possibility that you’re doing something else wrong. If it works over clearnet but not tor then we can work from there.

Also, stepping back from the details, you are obviously interested in anonymity, so I believe you might be better off setting up your own wallet, rather than using a third-party service. I’m curious, why don’t you try to install your own Bitcoin wallet on a server? I normally recommend users against this, but you seem to be one of the edge cases who might be better off doing this.

If you do not want to keep the entire blockchain online, you could use the built-in Bitcoin adapter with this wallet:

https://github.com/prasos/bittiraha-walletd

In any case, make sure to only have only one adapter enabled for each coin that you use. The plugin will warn you about this.

Let me know how it goes.

[alexg]

If you want to connect over tor, at the very least I imagine that the API endpoint should be an onion address, so that’s one reason why it doesn’t work. The PHP code that you sent me is already in there, but the adapter is not meant to connect to the tor API of CoinPayments.

Unfortunately to test and debug this I will need to setup a tor site and this will take me some time because I’ve never done it before.

In the meantime, you could try editing the line in wallets-cp.php that reads

const API_ENDPOINT_URL = 'https://www.coinpayments.net/api.php';

Make it point to their API endpoint at their onion address and see if it works. It’s worth a shot.

User balances update automatically when a deposit is inserted into your DB and its status changes to done. This happens once a transaction reaches the required number of confirmations. If the deposit does not appear in your transactions table, even in unconfirmed state, then that means that it was not discovered by the cron mechanism for some reason. We will need to debug this.

If you wish, you could enable and check your WordPress logs, and let me know if you see anything suspicious.

[alexg]

My apologies I somehow missed your question while doing other stuff.

I have not tested the site with tor. Did you edit the PHP code and change the API endpoint?

I will try it out and let you know, in the meantime you could check your logs if you like.

regards,
Alex

[alexg]

Hello,

Please read the FAQ. It is not a good idea for me to tell you how to do this. If you are not comfortable installing applications on a Linux server then please use one of the web wallets, block.io or CoinPayments. It will save you a lot of pain in the long run. The reason is that you will need to administer the wallet yourself if you install it on a server you own. Also, you will need either a VPS or dedicated server. Shared hosting will not work.

If on the other hand you are comfortable with linux and the command line, instructions for how to install bitcoin are here https://bitcoin.org/en/full-node#linux-instructions

It does not matter which host you are using, just make sure you take note of the hardware and network bandwidth requirements which are quite high. https://bitcoin.org/en/full-node#minimum-requirements

best regards,
Alex

[alexg]

Hello,

At the moment paypal is the only payment option on the site.

I plan to build something for crypto payments and when it is deployed I will let you know.

best regards,
Alex

[alexg]

Hello,

I could send you the schema in SQL, but it is safer if you do the following:

1. Delete the wp_wallets_revision option from the DB:

DELETE FROM wp_options WHERE option_name = 'wallets_db_revision';

Make sure to replace wp_ with whatever prefix your DB is using.

2. After deleting the option, deactivate the plugin and reactivate it.

I will make a note to make the uninstall script delete the DB revision so that in the future a simple deactivate/reactivate cycle will repair the schema without manual intervention. This will be rolled out in the next release.

Let me know how it goes.

regards,
Alex

[alexg]

Hi,

A calculator can be implemented as a shortcode/widget on the main plugin, not necessarily as part of the WooCommerce extension.

This is now on my backlog, thanks for the suggestion. I will try to implement it soon-ish.

best regards,
Alex

[alexg]

Hello,

If you wish to gain access to the premium plugins you will need to visit the homepage at https://www.dashed-slug.net and click the button that says “Become premium dashed-slug member”. Membership costs $9.95 per 3 months. All the benefits of premium membership are listed on that same page.

thanks and regards,
Alex

[alexg]

Thank you so much for reporting this and for taking the time to debug the root cause!

You are of course correct, when a site uses SSL (as it should, nowadays), the correct API endpoint is secure-api.solvemedia,com. If it does not, then it’s api.solvemedia.com. Source: https://solvemedia.zendesk.com/hc/en-us/articles/203648204-Implementing-Over-HTTPS

This change is implemented in the faucet version 1.1.2.

Again thanks, I appreciate it.

regards,
Alex

[alexg]

I have found why the captcha is not shown.
In the file /wallets-faucet/includes/claim.php i have canged
//api.solvemedia.com/papi/…. to
//api-secure.solvemedia.com/papi/….

now it works

[alexg]

Hi, can you please check the following:

1. You can only set a faucet owner to be a user with the manage_wallets capability. Check that you have at least one user with that capability.

2. Once you do successfully set a user, you will not be able to claim funds from the faucet while logged in as that user. You will need to setup another account to test the faucet.

Also, are you on a multisite installation?

regards,
Alex

[alexg]

OK I had a look and I will post a short and a long explanation:

Short version:
You can delete the file wallets-faucet/includes/third-party/class-tgm-plugin-activation.php and your immediate problem should go away.

Long version:
TGMPA is a very common library for tracking dependencies among wordpress themes and plugins. For this reason, many authors use it. The version that I have included into the faucet plugin, TGMPA 2.6.1, is careful enough to not re-declare itself if it is already declared. The error you are getting is triggered from your meta4delicious theme, which I assume has an older version of TGMPA, that did not do that check.

I would recommend that you let the author of that theme know about this, so they can update to a more recent TGMPA version.

Let me know if deleting the file fixes your problem.

regards,
Alex

[alexg]

Thanks for reporting this.

I will fix it and release a new faucet version soon.

I will let you know when the fix is out.

regards,
Alex

[alexg]

The plugin does not call any of those methods.

There is no premium version of the plugin, but there are some premium extensions to it.

All is explained on the homepage https://www.dashed-slug.net

regards,
Alex

[alexg]

Remember to set sane values to transaction fees on plugin activation.

[Author]

Posts