dashed-slug.net

Hello,

The only advise I can think of is this:

1. Whatever caching mechanism you use, ensure that the JSON-API responses are not cached. So, exclude any URLs that contain the __wallets_action GET parameter to be on the safe side.

2. Some users in the past have had issues with transients not expiring because they use caching plugins, and have enabled the memcached option without actually connecting to a memcached daemon. So, whatever you use for caching, it’s best if you understand what it’s doing 😉

3. Some caching plugins also minify/tidy the HTML content. You should disable this on pages where the UIs are used. The reason is that the UI depends on HTML comments (<!-- -->), and these should not be stripped from the output.

Hope this helps.

with regards

Hello,

Glad that you find the plugin useful!

The shortcodes are here: https://www.dashed-slug.net/bitcoin-altcoin-wallets-wordpress-plugin/shortcodes/

If you are interested about snippets showing how to interact with the PHP API, you will find them in the PHPdocs: http://wallets-phpdoc.dashed-slug.net/classes/Dashed_Slug_Wallets_PHP_API.html

If you need to know the names of the text filters that you can use to modify various UI texts, you can check the accompanying documentation to the plugin. The documentation is the PDF file in the bundle download available from the dashed-slug website.

For any other code examples you may need, ask me.

with regards

If you only ran it once, then this is the expected behavior.

Also, check to see if there is a confirmation required either by an admin or by the user. By default, users who request withdrawals receive a confirmation link in their email that they need to click. Once the user, and an admin, if required, have confirmed the withdrawal, it can progress from unconfirmed to pending. Then, on the next cron job run, the withdrawal is accepted.

So, in conclusion, what is the transaction status, and how many retries is it at? You can check the transaction status at “Wallets” -> “Transactions”. Hit the cron job url a few times and see how the transaction state changes.

Also, is your adapter in a locked state? (see the article for details)

Let me know.

• This reply was modified 5 years, 6 months ago by dashed-slug.net.

Hello and welcome,

Sounds like your cron job mechanism is not running for some reason.

Withdrawals and internal transfers are processed whenever the cron jobs run.

So, go to “Wallets” -> “Cron job” and click the link once to run it manually. Normally, your withdrawals or a batch of withdrawals should first go from unconfirmed to pending, and on the next run they will be either executed, or the number of retries will go to 2. If a withdrawal fails, the sender will receive an email with an error message (but only if emails work on your server).

Once you’ve established that withdrawals are running when you trigger the cron jobs manually, you can then look into how to trigger that url automatically from elsewhere.

I’ve also put up a relevant article about debugging outgoing withdrawals here: https://www.dashed-slug.net/how-to-debug-outgoing-withdrawal/

Hope this helps.

Please let me know if you’ve resolved the issue or if the withdrawals are still stuck.

with regards,
Alex

This can be done with the Airdrop extension.

Simply assign a User Role to the users who want to be affected, and then perform an airdrop to that user role. The amount can be a fixed amount or a proportion of another balance that they already hold.

To perform a single airdrop manually, use Tools -> Airdrops.

To perform a recurring airdrop (i.e. one that executes on regular intervals), create a new Airdrop via the admin interface. This will execute repeatedly with the parameters that you choose (unless if the wp-cron mechanism is disabled on your site).

Note that the Airdrop extension does not actually transfer funds, it only creates “fake” deposits to the affected users, so that their reported balance increases. It is up to you to ensure that the hot wallet balance is large enough to accommodate for the users withdrawing their new funds. After your airdrop, go to Wallets -> Adapters and compare the hot wallet balance with the sum of user balances.

For more information on the Airdrop extension, see here: https://www.dashed-slug.net/bitcoin-altcoin-wallets-wordpress-plugin/airdrop-extension/

with regards

Hello,

This is the support forum for the parent plugin. What you are describing is related to the WooCommerce Payment gateway extension. Please post your request at the appropriate forum and I’ll look at it.

Please also include the following with your request:

1. How did you select a cryptocurrency that has insufficient balance? The payment gateway only presents currencies with sufficient balance as options on checkout.

2. Assuming that your balance has decreased since the checkout page was rendered, was there an order placed? In my tests, if such an edge case occurs, an order is created, but its status is “Pending payment”, so there is no danger of the order being fulfilled. Do you see an order created under “WooCommerce” -> “Orders”, and what is its status?

Please post your reply at https://www.dashed-slug.net/forums/forum/woocommerce-cryptocurrency-payment-gateway-extension-support/

Thank you

with regards,
Alex

Glad to help!

Hello,

There’s no such feature right now, but you can easily hook into the plugin’s PHP API. This way you can add any logic you want for rejecting transactions based on coin, amount, sender, receiver, etc.

In this situation we’ll hook into wallets_api_move with a priority that is less than 10, because at 10 we actually perform the transaction. If you throw an exception on a hook that runs earlier, this will prevent the transaction, and will display your error message to the user.

function disallow_small_moves( $args = array() ) {

	if ( 'BTC' == $args['symbol'] && $args['amount'] < 0.0001 ) {
		throw new Exception( 'You cannot move less than 0.0001 Bitcoin' );

	} elseif ( 'LTC' == $args['symbol'] && $args['amount'] < 0.001 ) {
		throw new Exception( 'You cannot move less than 0.001 Litecoin' );
	}
}

add_action( 'wallets_api_move', 'disallow_small_moves', 0 );

Here we’ve set lower limits to move transactions for Bitcoin and Litecoin.

Don’t forget to add your code into your child theme’s functions.php file or as a separate plugin. Don’t edit your theme or plugins directly, because any changes will get overwritten when you update your components.

Let me know if you have any further questions about this.

with regards,
Alex