[alexg]

Thanks for letting me know.

I have not tested the adapter with this particular wallet.

Once I do I will let you know what I found here.

with regards

[alexg]

Hello,

The performance improvement will be more apparent if you have many users performing transactions. If there are no transactions to execute then it will not make any difference.

The expected result is the one you report. It is also shown in the documentation in the JSON API reference.

with regards

[alexg]

Hello,

Probably the theme developers will be able to solve the problem.

If not, then it should be a simple matter of fixing it with some CSS.

If you want me to try and determine a solution, email me some credentials and I will login and look at it.

with regards

[alexg]

Hello,

The box you are checking is for internal transfers. If you want to disable admin confirmations for withdrawals, you must uncheck the box that is titled “Admin condfirmation required” under the “Withdraw transaction confirmations” section.

About the [wallets_transactions] shortcode, it seems your theme’s CSS is causing some trouble with it.

1. Could you please confirm that the problem does not show when you change to another theme?

2. If you like, I can login and maybe come up with a few CSS rules that you can add to fix the display issue. Email me some credentials if you want me to look at this.

3. You can also try out the alternative template, [wallets_transactions template="rows"].

Let me know please.

with regards

[alexg]

Hello,

It is true that you need to pass the apiversion argument in all JSON API calls. I must update the documentation to that effect.

You can initiate an internal (move) transaction via the API. Authentication is basically the login that you did via curl. However, if the plugin requires that transactions are confirmed (by the user or the admin) you cannot override this when entering transactions via the JSON API. ( In contrast, you can override the need for confirmation if you enter transactions via the PHP API, using the skip_confirm argument.

If you check the “Enable legacy JSON APIs” option, that allows you to pass older apiversion arguments, but you cannot omit it altogether.

Hope this helps. Please let me know if I did not answer your question fully, or if you have any further questions.

with regards

[alexg]

Hello,

Please tell me the following:

1. Does the problem persist when you switch to a standard theme, such as twenty eighteen?

2. Do you see any JavaScript errors in your browser console?

3. Do the following shortcode variants work? [wallets_exchange_market template="dropdown"] and [wallets_exchange_market template="simple-dropdown"]

thanks

with regards
Alex

[alexg]

Yes, you are correct. I have not tested Loco Translate, there is not something you’re missing.

The procedure is as described in the manual. If you try this and it does not work, please let me know.

with regards

[alexg]

Hello,

Thank you. Personally I think that this is too complicated and unnecessary. Currently, users can perform deposits without filling in any forms, and this is how most exchanges and online services work, so this is what users will expect. Introducing more complexity into the deposit process will not solve anything.

Withdrawals require confirmation because there is a security risk with withdrawing money. Depositing money on the other hand should not be difficult because it does not pose a risk. Therefore, there is no need for admins to confirm deposits. Once a user has performed an irrevocable deposit transaction on the blockchain, there is no situation where you would not want that money to be deposited to their account.

with regards

[alexg]

Yes, this is possible.

However in the meantime, I would recommend that you do the following:

Do not disable wp-cron, but do install the system cron. Most of the load will be removed from user requests.

with regards

[alexg]

Hello,

Yes, this is why. The coin adapters rediscover deposits from the wallets when possible. Additionally, the block.io adapter restores the user deposit addresses.

If you are using any other coin adapter, simply deactivate the plugin, delete all data, then activate the plugin again. If you have deleted the deposit addresses then these will not generate deposits: even if the transactions are rediscovered, they will no longer be associated with your users.

If you are using the block.io adapter, I would recommend that you start again with a brand new wallet, since you are deleting everything anyway.

with regards

[alexg]

Hello,

Version 1.1.0 of the Airdrop extension is now released. Airdrops can now be filtered by user role.

with regards

[alexg]

Hello,

Version 1.1.0 of the Airdrop extension is now released. Airdrops can now be filtered by user role.

with regards

[alexg]

Hello,

This is intentional. The fees are always charged on the base coin, not the quote coin of the market.

Suppose that user 1 is a buyer and user 2 is a seller. Then, the four transactions that you see are:

one tx for removing the base coin from user 1 (fees are charged in this tx)
one tx for adding the base coin to user 2 (fees are charged in this tx)
one tx for removing the quote coin from user 2 (no fees)
one tx for adding the quote coin to user 1 (no fees)

Hope this helps.

[alexg]

Hello,

Thank you for noticing this and for reporting it.

I will fix the bug in the next patch release of the faucet. In the meantime, you can do one of the following:

1. Install a newer version of PHP.

2. Go to referral.php line 169 and remove the ampersand character (&).

Any of these two will work.

[alexg]

Hello,

Thank you for the clarification.

It is definitely possible to bind to the wallets_transaction action, observe the incoming data, and if the transaction is a stake reward, send an email using wp_mail. You can implement this easily in your functions.php file or a small separate plugin. Take care, because different wallets implement rewards differently: Some wallets remove all your balance, then add your balance again, plus the reward. In other wallets, the reward amount is added separately in a new transaction. So look at your wallet’s listtransaction output first.

I am not planning to add a feature where POS rewards are added to the admin account. Part of the reason is that due to incompatibilities between POS wallets, this will cause problems.

with regards

[Author]

Posts