[alexg]

This has now been addressed in version 1.3.2 of the Faucet extension.

[alexg]

Oops yes this is a rather important feature for faucets!

I will try to fix this as soon as possible. Thank you for reporting.

[alexg]

There was a bug in the redirect code that affected only Apache but not Nginx. This is now fixed in version 1.3.1 of the Faucet extension. Thank you.

[alexg]

OK thank you for the additional info.

It doesn’t make sense for you to expect a deposit to go through if the transaction was initiated via the CoinPayments interface. What needs to happen is this:

1. The user visits a page with the [wallets_deposit]. The plugin then requests a new address from the wallet (in this case CoinPayments) and assigns it to the user. The mapping is stored into the addresses table.

2. The user then sends funds to that address. The wallet receives the funds, then informs the plugin. In the case of the CoinPayments adapter, this is done via the IPN message. The plugin then creates a deposit transaction for that user.

3. Next time the user views their balance, the plugin sums all the transactions including the new deposit and this new amount is reflected in the total balance for that coin.

Unless the address was stored in the addresses table and mapped to the user’s WordPress user id, the deposit will not go through.

Here’s what you can do to rectify this:

1. Figure out the user’s WordPress ID. This is an integer number that you can find via Admin -> Users.
2. Insert the mapping manually (you would not have to do this under normal circumstances). Here’s how you could do this:
INSERT INTO wpk4_wallets_adds(account,symbol,address,created_time) VALUES(5,'LTCT','A_DEPOSIT_ADDRESS',NOW());
This would associate user with user_id=5 with the LTCT address A_DEPOSIT_ADDRESS.
3. Go to your CoinPayments IPN history, and click the button to resend the IPN message.

This should resolve your current issue. In the future, never allow your users to use the CoinPayments platform directly. They should not even have access to that, since it is your site’s wallet.

Hope this helps.

[alexg]

Hello,

Thank you for the very detailed description of this issue.

According to your IPN history, the IPN message did indeed arrive to your plugin instance.

Since the message did arrive, the only other reason why it would not appear in your transactions list would be if the deposit address was not bound to your user.

Can you please hit the following query into your SQL console?

SELECT
	*
FROM
	wpk4_wallets_adds a
WHERE
	symbol = 'LTCT' AND
	address = 'YOUR_DEPOSIT_ADDRESS'
ORDER BY
	created_time DESC;

Please replace YOUR_DEPOSIT_ADDRESS with the actual address you used for this transaction.

This will confirm whether this address is indeed bound to a user.

Please let me know what you find.

regards

[alexg]

Thank you. I will investigate.

[alexg]

I have improved the redirect mechanism in Faucet 1.3.0. Now it should redirect to whatever the referral link was but without the referral code.

regards

[alexg]

Hello Klaus,

As long as you can provide a coin adapter for your coin’s wallet, you should not have any problem to only offer a wallet for that coin to your users. You will have to disable the built-in Bitcoin core node adapter (uncheck the “Enabled” option in the adapter settings).

If your coin is a direct fork of Bitcoin then you can connect to a running instance of your wallet using the Multi-adapter extension. Please refer to the documentation section “Coin Adapter development” for instructions.

If your wallet is different then you will need to implement parts of the coin adapter by extending the abstract class Dashed_Slug_Wallets_Coin_Adapter. Inspect the file wp-content/plugins/wallets/includes/coin-adapter.php and pay special attention to the methods under “// Wallet API”. You should create a class that extends these methods to connect to your wallet and to provide information about your coin. There instructions are in the PHPdoc comments and I remain available to answer any questions you may have.

To issue an initial amount to your users perhaps it’s best if you let the users create wallets, then, when everything is set up correctly, simply send a transaction to all the user deposit addresses.

Hope this is helpful. Do let me know if you have more questions or if any of this was not clear.

kind regards
Alex

[alexg]

Hello,

Yes I already intend to add coinhive to the faucet, I simply haven’t found the time to do this yet. I also think it is a good fit for the project.

Thank you for your suggestion.

[alexg]

The JavaScript error should now be resolved in the latest version 3.1.0 released today.

[alexg]

Hello Mario,

Thanks for all the information you sent me.

I am not certain that these two problems are related. However, I believe I can include a quick fix about the JavaScript error in the next patch release of the plugin.

About the problem with the internal transfer:

When you enter a destination user in the [wallets_move] shortcode, the plugin attempts to interpret this as a WordPress login name, a user email, or user slug. I believe the user “Mario” that you have created is an entry in your membership plugin. It is very likely that this entry corresponds to a WordPress login name of “mario” in your WordPress records. Can you please do the following?

1. Try to send to user “mario” with lowercase (small “m”) and see what happens.

2. Go to your WordPress admin screen, and then to “Users” -> “All Users”, then find the user record and click on “Edit”. What is the entry under the “Username” entry? This is the WordPress login name of that user.

3. What happens if you attempt to send to the user’s email?

If there are any differences between the user name in the wordpress records and the records of your membership plugin, then this would be the cause of the problem you are facing.

Please let me know if you attempt these three things.

kind regards

[alexg]

Glad you found it useful!

[alexg]

Hello,

If you want to provide a CLAM adapter, you might find it easier to do this using the new multi-adapter, which works for many coins:

Full Node Multi Coin Adapter extension

You should then have no problem implementing a CLAM faucet.

It is possible that PayPal does not accept your bank or credit card.

You are welcome to pay for membership via cryptocurrencies if you wish.

Please send the equivalent of $9.95 at one of the following addresses and I will activate your three month membership manually.

Bitcoin Address: 1DaShEDyeAwEc4snWq14hz5EBQXeHrVBxy
DOGE Address: DASHEDj9RrTzQoJvP3WC48cFzUerKcYxHc
LTC Address: LdaShEdER2UuhMPvv33ttDPu89mVgu4Arf

kind regards

[alexg]

Hello,

Yes this is expected behavior. The plugin’s job is not to enforce any SSL policy on your website – it simply warns you if you are not using SSL. The correct place to enforce such a policy is at your web server’s configuration (Apache or Nginx, usually).

kind regards

[alexg]

Thank you I am investigating this.

[Author]

Posts