[alexg]

Hello,

Here’s some CSS you could use for your use case. This utilizes the new classes crypto-coin and fiat-coin: Known crypto coins have the class crypto-coin, known fiat coins (with respect to fixer.io data) have the class fiat-coin and other coins, such as custom coins don’t have these classes.

To hide the deposit QR code for coins that are not known to be crypto coins:

.dashed-slug-wallets.deposit .qrcode { display:none;}
.dashed-slug-wallets.deposit.crypto-coin .qrcode { display:inherit;}

And to hide the withdraw information for coins that are not known to be crypto coins:

.dashed-slug-wallets.withdraw tr:not(:first-child) { display:none;}
.dashed-slug-wallets.withdraw.crypto-coin tr { display:table-row;}

You could add these to your customizer. Hope this helps.

with regards

[alexg]

Hello,

There are no particular issues that I can think of.

Check the FAQ under “I want to replace an adapter with another one.”

Follow the instructions for the TurtleCoin adapter and let me know if you face any problems.

Good luck!

with regards

[alexg]

Hello,

Thank you for reporting this.

There is indeed an issue with this shortcode. I will release a fix today and I will notify you here again. In the meantime, you can downgrade to the previous version, 5.0.5.

with regards

[alexg]

Hello,

Version 5.0.6 is out, and has several new shortcode templates and a few new shortcodes. The Shortcode documentation and the accompanying PDF document have been updated to reflect the changes. It is now possible to output some values as pure text. See the “Textonly” and “Static textonly” paragraphs in the shortcode documentation.

If you need something more specialized in terms of HTML templates, you can always override the templates yourself, as discussed above (see the release notes for 5.0.0 for how to do this.)

Hope this helps. Let me know if you have any further questions on this topic.

with regards

[alexg]

Version 5.0.6 is out now. Many UIs now annotate their nodes with the crypto-coin and fiat-coin classes.

[alexg]

Hello,

Glad to hear that the new solution works for you (i.e. displaying fiat and crypto markets in different tabs).

You also mentioned the issue of qr codes for custom coins appearing in the [wallets_deposit] and [wallets_withdraw] UIs (from this other thread).

With the new HTML classes .crypto-coin and .fiat-coin that will be released today, you can do this with CSS. i.e. hide all qrcodes, then display the ones that are known to be crypto or fiat, according to the Excahnge rate providers.

I will not be hiding qr codes for custom coins by default for several reasons:

1. Custom coins are not a concept of the parent plugin, only the fiat coin adapter extension. They are a hack and should really not be used under normal circumstances. In fact I am strongly considering to remove the custom coins feature as it is a mess.

2. If I were to add such CSS rules into the plugin, it would hide the UIs for all coins, for users who have not set up fixer.io.

3. This would cause issues with people who have connected to a full node wallet for a coin that is not known to third party services yet.

Therefore you now have all the tools to implement what you suggest, with no more than two or three simple CSS rules which can be added to customizer.

We can continue this discussion if you like, but I have repeatedly told you that I will NOT be implementing this change. But look out for version 5.0.6 where UIs will be annotated with the HTML classes .crypto-coin and .fiat-coin. If you’ve set up fixer.io, then any coin that does not have these classes is likely to be a custom coin.

with regards

[alexg]

Hello,

Thank you, and yes, I am aware of Changelly. If you wish to provide similar functionality to your users with this plugin, there is a ShapeShift extension. ShapeShift is essentially the same as Changelly.

If you wish to instead provide your own Changelly-like functionality, based on the Exchange extension, you can build a solution yourself: The Exchange extension has a JSON API that allows you to place instant market orders at the spot price.

Alternatively, you can use the recent [wallets_exchange_market_order] shortcode to provide a UI to the Exchange that reminds of ShapeShift/Changelly. See the relevant release notes.

Integrating with the liquidity of other exchanges is (as stated above, and in the Exchange extension’s FAQ) out of scope of this plugin. To be clear, I will not be offering a solution for this feature. You can do this manually, or you can use the JSON API to build such an automated solution if you like. But this would be a completely different product/service than the ones I have available.

Please let me know if you have any other questions.

with regards

[alexg]

Hello,

First of all, if you are concerned with how to display data in your own HTML markup, the best way to do this is by overriding the templates. Since 5.0.0 this is done in a way that is standard to WordPress, i.e. you copy the template files and hack the markup, placing the new files under your theme or child theme. For more information please see the relevant release notes, and the accompanying documentation.

Regarding your question about API docs: There are two major APIs to the plugin, the PHP API and the JSON API.

The plugin’s documentation is found in the bundle download of the plugin, which you can get here. The same is true for the Exchange extension, which also has a bundle download. Both bundles include a PDF document which includes documentation on the JSON APIs.

Additionally, there are instructions on how to communicate with the API using a bearer token from the command line using curl. Instructions are given in the JSON API page and in the documentation. The user can display or refresh their bearer token using the [wallets_apikey] shortcode.

Using the JSON API you can construct any kind of interface including web interfaces or standalone applications. Additionally, you can call the JSON API from any programming language where you can do HTTP requests and parse JSON.

Have a look at the docs and let me know if you have any questions.

I have began dev and will be releasing plaintext shortcode outputs over the next few days, but this can only be implemented for shortcodes that output simple values. My recommendation to you is that you first look into the templating system, before attempting to hack a new solution using the JSON API. But it’s up to you.

with regards

[alexg]

Please relax everyone. A number of users have asked me for a KYC solution, and now that there is one, the plugin RECOMMENDS that you use it. You can choose to ignore the recommendation if you believe that you are in a jurisdiction where these laws don’t apply to you. It’s up to you. Nothing has changed. I am not forcing you to do anything.

[alexg]

OK, nevermind, it doesn’t matter where the shortcode is.

I looked at the JSON API endpoint: http://tgtrade.com.ng/?__wallets_apiversion=3&__wallets_action=get_coins_info

and the response looks as if I’m not logged in.

This means that some server-side cache is caching the JSON API responses.

If you know of any such cache that you’re using, you must add an exclusion (white list) for any URLs that have the __wallets_action GET parameter.

Let me know if you can’t find this.

with regards

[alexg]

I have signed up to your site. Could you please tell me which page the shortcode is on?

[alexg]

I have added the plugin as a non-essential dependency. In other words, the plugin recommends to the admin that they use this plugin. The admin can choose to dismiss the notice.

No one is pressuring me, KYC is an obligation of site operators.

[alexg]

Since Token of Trust is such a good fit, the Exchange extension now uses TGMPA to recommend that the admin installs Token of Trust. i.e. it is a non-essential dependency since version 1.3.2 of the Exchange extension.

[alexg]

In version 1.3.2 of the Exchange extension I have added two new buttons to the [wallets_exchange_markets] shortcode. The buttons filter markets by fiat-denominated or crypto-denominated. The buttons are only shown if both types of market exist. I have also added relevant HTML classes to the rows in the [wallets_exchange_markets] and [wallets_exchange_markets template="static"] shortcodes. See the changelog for details.

[alexg]

Yes @alexg, we are working on proving OTC to our site owners. We also build any custom functionality a site owner may want to implement.

[Author]

Posts