[alexg]

Hello,

Thank you very much for identifying and reporting this issue!

I will investigate and fix this as soon as possible.

with regards

[alexg]

They used the withdraw feature

[alexg]

Hello, thanks for your kind words!

Since the faucet balance is the balance of the user whom you’ve designated as faucet owner, you can use the “static” template of the wallets_balance shortcode, like so:

[wallets_balance template="static" user="faucet_owner_user" symbol="LTC"]

This would show the Litecoin balance of the user with username faucet_owner_user.

See here for a reference to the various shortcodes you can use: https://www.dashed-slug.net/bitcoin-altcoin-wallets-wordpress-plugin/shortcodes/

In the next version of the faucet, the actual shortcode for displaying the remaining balance will be suggested in the admin panels, so you can copy and paste it easily.

with regards

[alexg]

About your question regarding transactions, here’s a complete example:

https://example.com/?__wallets_apiversion=3&__wallets_action=get_transactions&__wallets_tx_count=10&__wallets_tx_from=0&__wallets_symbol=BTC

This would retrieve the first 10 BTC transactions. Don’t forget to add authentication parameters to your call.

You can always observe the XHR requests in your browser to see how the plugin does it.

This is where the GET parameters get passed into the PHP API:

https://github.com/dashed-slug/wallets/blob/4.2.0/includes/json-api.php#L1157-L1168

And the relevant PHP API:

https://wallets-phpdoc.dashed-slug.net/classes/Dashed_Slug_Wallets_PHP_API.html#method_api_transactions_filter

with regards

[alexg]

@bigblue Thank you for your comments. You can currently perform as many individual airdrops as you want. What is missing, is a way to automate recurring airdrops. These would be useful for investment-type applications.

[alexg]

Header-based bearer auth is already supported in API version 3, exactly as you describe. You must still pass the user ID as a GET parameter though.

The advantage of this approach is that you are not including secret information in the URL, where it could be logged in server access logs. Version 4, when it is out, will continue to have this feature.

with regards

[alexg]

Did these users use the plugin’s withdraw feature? Or did they initiate the transaction from the CoinPayments platform?

[alexg]

That is correct. For now, you can only do key-based auth with ugly URLs.

This shouldn’t be a problem, as pretty URLs are for end-users only. A developer should be able to use HTTP GET params!

But I am taking a note of your comment, for JSON API version 4!

thank you

[alexg]

Your .htaccess file is huge. It will take some time to analyze and I am currently extremely busy. I will get back to you. It is likely that this is indeed the problem.

In the meantime, you can try the recommended default for WordPress: https://codex.wordpress.org/htaccess

I am not sure if something else will break when you replace all these rules, so keep a backup of your current .htaccess file.

with regards

[alexg]

Yes, this is a much requested feature. It will be implemented as part of the Airdrop Extension.

Please see this thread: https://www.dashed-slug.net/forums/topic/suggestion-cron-job-for-airdrop/

with regards

[alexg]

Thank you. Looks good.

When I find the time to work on this, it is more likely that I will use one of the freely available options. I believe this will benefit more users.

with regards

[alexg]

Hello,

Yes, you need to assign the access_wallets_api capability to the user. If you wish to use the API with an administrator account, use any plugin that can edit capabilities to assign access_wallets_api.

Since the user_id is required for remote access, it can be added to the get_nonces call. This way you can login first using cookies, obtain the login credentials programmatically, then continue accessing the API using the key. This will be added in the next patch.

with regards

[alexg]

Hello,

You can find detailed instructions in the accompanying pdf documentation that comes with the bundle download of the plugin.

You can get the bundle download from: https://www.dashed-slug.net/downloads/

Please see under APIs -> Wallets JSON API -> Programmatic access to the Transactions API

You must first assign the access_wallets_api capability to the user.

You can use the plugin’s capabilities section to assign this capability to all user roles except the Administrator (for safety). If you wish to use the API with an administrator account, use any plugin that can edit capabilities to assign access_wallets_api.

with regards

[alexg]

Hello,

I have copied this feature over from the Exchange extension into the parent plugin, and improved it somewhat. The details are in the documentation file. Please see the relevant release announcement here: https://www.dashed-slug.net/json-api-key-access/

Please let me know if you have any questions about this feature, after reading the relevant part of the documentation.

with regards

[alexg]

Hello,

Yes you are correct. This would be useful. I will add it to my list.

This will hopefully go into the next release. Thank you.

with regards

[Author]

Posts