[alexg]

MyCryptoGive.com

Work in progress with currently over 1600 registered users.

[alexg]

Hello,

I’ve done some preliminary analysis on grin and I thought I’d update you.

I am not sure if they are a good fit for the plugin as it is right now.

The host:ip destination format can be easily mapped to “addresses”. This is what KuCoin and Bittrex do. In fact KuCoin does a POST request to pass the TX data, while Bittrex uses the file method. Interesting. KuCoin uses a url fragment to uniquely identify the user that does a deposit. Bittrex accepts a file upload.

Unfortunately, completing a transaction (deposit or withdrawal) involves an extra step that I never accounted for when creating the core plugin. The recipient must return a file to the sender to complete the transaction. This complicates things by a lot.

For now I will focus on creating a coin adapter for TurtleCoin and its clones, as this was also a user request. I will have to rethink how the main plugin can be refactored to allow for mimble wimble coins. I’m letting you know because it might take some time before I can provide a solution for mimble wimble. It will definitely require changes to the core plugin.

with regards

[alexg]

Hello,

I have done some preliminary work yesterday on TurtleCoin.

I was not aware of this family of coins and I am pleasantly surprised by how easy they are to setup compared to Cryptonote, and the wallet API doc is very helpful.

I believe that I should be able to create a TurtleCoin adapter soon (perhaps in a few weeks time, if all goes well). It would be a nice addition to the collection of available coin adapters.

My goal is to provide support for TurtleCoin and all its forks. I will let you know again here, once I have any more news.

with regards

[alexg]

Hello,

Yes, I have already added this to my backlog.

Like I said, I want to add this feature at some point. I will let you know here once I do. It is not a simple matter of reusing a form.

with regards

[alexg]

Hello,

As it turns out, it was already possible to modify the comments for cart payments. (I had forgotten about this setting.)

In the latest version 2.3.2 of the payment gateway it is also possible to modify the tags appended to the internal transfer. See the payment gateway’s settings admin page for details.

Make sure to always include the Order ID somewhere in the tags, so that you can easily find the transaction afterwards.

with regards

[alexg]

@bigblue Pagination has been added to version 2.0.0 of the Tip the Author extension. Release notes: https://www.dashed-slug.net/tip-the-author-extension-reworked/

with regards

[alexg]

Fixed. Thank you for spotting this.

[alexg]

Thank you. I can add this feature in the next release of the payment gateway. I will notify you here.

with regards

[alexg]

No, but it is possible for the admin to select the coins that are acceptable as payment by the user in the shopping cart. Go to WooCommerce -> Settings -> Payments -> Bitcoin and Altcoin Wallets -> Accepted coins, and Ctrl+click the coins you wish to allow, then click on “Save Changes”.

The vendor normally receives commissions in the same currency as that used by the customer to pay for the cart.

If the customer used some other gateway rather that the cryptocurrency gateway, then the vendor will receive their commission in the currency that they have designated as “Fallback currency for commissions” in the vendor dashboard. If this fallback currency is not available in the site’s wallet, the vendor will get an error message and can contact the admin about this. The commission can then be retried when the admin has replenished the wallet’s funds.

I am aware that this is not ideal, but unfortunately it is not possible for me to improve the commissions gateway any further. It was hard enough to get this to work, as WCMp is not easy to extend with payment gateways, and I had to resort to all sorts of DB hacks to make this work.

with regards

[alexg]

Thanks for letting me know, I will investigate this today. For reference, the lastest changelog is as follows:

2.0.0

• Change: The tipping UI is now a template in file templates/tip.php, can be overridden by themes in wp-themes/THEME/templates/wallets-tips/tip.php.
• Change: The tipping UI is now shown even if the current user is the article author.
• Add: The tipping UI now loads past tips for a post via a JSON API, and includes pagination.
• Add: The number of tips loaded per page in the new pagination feature can be set by the admin.
• Change: The default layout of the UI has been improved.
• Add: Map file is now added for the minified version of the JS code.
• Change: The JavaScript code is now loaded lazily (only as needed).
• Improve: All the frontend strings are now translatable via po files (language domain: wallets-tips-front).

[alexg]

Hello,

There are several things you can look at.

First, check to see if the exchange rates are shown in the boxes below the Exchange rate settings.

Also check to see if you can get exchange rates from other exchange rate providers.

To check the exchange rates stored on the DB using wp-cli, do a wp option get wallets_rates | egrep '(LTC|BTC|ARMS)'.

Enable debugging and click on the “Clear/refresh data now!” button again. Check the logs to see if any errors are shown.

In case you want to inspect the code using error_log() debug prints, the relevant code that needs to work is this: https://github.com/dashed-slug/wallets/blob/5.0.1/includes/rates.php#L1186-L1233

The code first identifies the enabled coin adapters, then it determines the CG ids for these coins, it determines the site’s default fiat symbol (usually USD), and finally queries the server for the price of these coins against the fiat symbol.

You can inspect what $url is constructed, what the $json response contains, and what is returned in the $rates array:

error_log( $url );

error_log( $json );

error_log( print_r( $rates, true ) );

Hope this helps. Please let me know if you find any issue with the code, or if you need any more help with debugging.

with regards

[alexg]

Thank you. It does look like this wallet has a completely different API.

I could possibly create an adapter, but I don’t know when I can look at this, as it will require some analysis. Too many people at this time stay at home and play with the plugin due to the current situation. There is a high demand for a grin-like adapter, so this might need to take precedence.

If you are going to attempt creating a turtlecoin/2acoin adapter, focus on providing an implementation of Dashed_Slug_Wallets_Coin_Adapter that implements all methods. A somewhat dated article on this: https://www.dashed-slug.net/developers-coin-adapters-api/

Also, when a new deposit is discovered, the adapter should trigger the wallets_transaction action. More on this here: https://www.dashed-slug.net/howto-create-update-transactions-from-php/

I’ll try to give you more info as soon as I perform an initial analysis on the API spec you gave me.

with regards

[alexg]

Hello,

I’ve moved your posts to the support forum for the Monero adapter.

If you’ve put the code under some kind of version control before making changes, you can easily diff your changes with the original code. The get_balance() method has an if..then…else construct. In the code you posted above you seem to have deleted the else branch.

The adapter maintains an association of WordPress blog_urls to wallet accounts. If your installation is single-site, there will be only one blog url. If you are on multisite, there will be many. But if you are on a multisite installation AND the plugin is network-activated, this means that user balances are shared across all sites, and therefore the coin adapter must sum over all the sites. Hence the if/else construct.

When the plugin is network-activated, users may potentially be holding balances on various sub-sites, therefore there is a need to store balances on different wallet accounts. But if the plugin is not network activated (which is the usual for most installations), then the else branch is executed.

I would recommend that you restore the code and try your changes again. What you’re interested in is probably the else branch, which calls RPC get_balance once for the account corresponding to the one blog that your site has.

Additionally, if you are encountering issues with a cryptonote wallet, you can open a new thread on this support forum, and I can investigate to see what’s going on.

with regards

[alexg]

Hello,

I have moved your question to a new thread. Start by choosing one or more coin adapters, then proceed to install them.

Once you get this done, you can proceed to install some app extensions depending on what your needs are.

You can also have a look at the FAQ, and the accompanying documentation (the pdf file in the bundle download of the plugin).

If you’re getting started, it is useful to check at least the glossary section of the manual.

Let me know if you get stuck somewhere or if you have questions.

with regards

EDIT: I noticed now that you’re asking about the Exchange extension. If you have followed the installation instructions you should have created one or more markets. Do you see the markets?

The markets will be empty at first, as explained on the extension’s homepage (see disclaimer about liquidity). This is as designed.

[alexg]

Hello,

The detection of HTML comment removals was not 100% accurate in some edge cases. If you can view the shortcode [wallets_balance template="list"] without problems, then don’t worry about it.

Thank you very much for spotting the other issue you mentioned regarding 403 errors. Turns out that, now that the JS code is lazy-loaded, some of the extensions can force the main plugin to load the JS code, even if the user is not logged in. I can fix this easily in the next patch of the plugin. I will notify you, but don’t worry about it, as it doesn’t cause any serious issue, other than minor performance reduction.

with regards

[Author]

Posts