[alexg]

Hello,

You bring up a valid point.

1. Since there is now a proper templating system, I intend to create new templates that output the raw values for things like the currenct balance. Unfortunately this is not possible for more complex output, like the list of past transactions, which has to be a table in one way or another. I will let you know on this thread when I implement this.

2. You are correct that you need to know some CSS. However, if you do not, then I would argue that this is a problem. On the one hand, themes will never be similar in terms of CSS, so I can’t provide one set of rules that works every time. And on the other hand, how are you going to offer a website that handles peoples money if you are not a web developer? The plugin and its extensions are aimed at developers. If you wish to learn CSS, start by learning the selectors, then go on to read about selector specificity. Unfortunately there’s no way around this.

3. It’s a good idea for me to look into providing editor blocks (I will not be looking into Elementor specifically, only WordPress Gutenrberg blocks). As I am currently very busy, I cannot undertake any new development at the moment. This should not be a big problem, since you can always enter shortcodes as blocks.

4. The data is also available in its raw form. Look into the JSON-API for details.

5. It’s not true that there are no classes to differentiate between deposits and withdrawals. The selectors are .dashed-slug-wallets.withdraw and .dashed-slug-wallets.deposit. Use these to focus your rules on one form or the other.

In conclusion, please learn some CSS because it’s impossible for me to provide a set or rules that works for everyone everytime, and because you want to know this if you are building websites. I will notify you again here when I release shortcode templates with plain value outputs.

with regards

[alexg]

Thanks,

I will review this plugin when I get to it.

with regards

[alexg]

@zachkinsey Thank you for sharing your thoughts. Unfortunately, what you are proposing is a totally different plugin, not a new feature. The available exchange extension is a regular exchange, not an OTC exchange, and furthermore it does not communicate with other exchanges. If you are looking for an OTC exchange, perhaps you could look elsewhere.

@UberNomad Looks good. Does your product offer the OTC functionality that the OP requests?

[alexg]

Hi Zach,

We have built a SaaS platform at Fintech Systems (https://fintechsystems.ltd) that does everything you want and more.

Buy, Swap, Trade, Custom Market Data API, Integrated Eth wallet, smart contracts, build your own token, create funding contracts, publish your smart token to the wallet, a full affiliate system etc etc. Borrow, Lend, Sell coming soon.

Save yourself the headache and come talk to me. You can find me in LinkedIn (https://www.linkedin.com/in/graemeconradie/), or inside my collaboration platform FinChat – https://chat.fintechsystems.ltd, create an account and ping me (Graeme).

Graeme

Attachments:

You must be logged in to view attached files.

[alexg]

Apologies, I was thinking of the other thread related to the Exchange.

The same holds for the UIs of the parent plugin. I will be adding classes so you can distinguish between fiat/crypto.

I will not be providing a way to distinguish between fiat and custom coins.

Hope this is clear.

[alexg]

Are you referring to WC Marketplace?

First of all, you should disable automatic disbursement, as instructed in the admin screens by the plugin. The payment gateway requires that the admin pays commissions manually.

The payment gateway has nothing to do with deposit addresses. Payments are done internally.

Your client was able to change their deposit address using one of the two ways I described above.

However this is not related to the Marketplace. The [wallets_deposit] UI and these deposit addresses are for users who wish to deposit funds to their account. When a user checks out a cart, they can only pay with funds that they have already deposited. These funds are transferred to the admin account that you specify in the WooCommerce gateway admin settings.

with regards

[alexg]

Thank you.

As discussed before, I will introduce classes into the market table rows, indicating which markets have fiat/crypto base and quote currencies.

Using these, you will be able to hide rows and thus display one UI with fiat markets, and another with crypto markets, as needed.

with regards

[alexg]

OK, then the plugin works as intended.

To be clear, I am not planning to do the changes required to separate fiat from custom coins.

My recommendation is that you do not use custom coins with the Exchange if this is a big problem.

with regards

[alexg]

The deposit addresses can be refreshed by the user, via the button in the [wallets_deposit] shortcode, or via the Coin Adapters admin screen. This is normal. Old deposit addresses are retained, so that any deposits to them are still credited to the correct user.

However, this has nothing to do with eCommerce. If you’re using the WooCommerce payment gateway, note that the customer does not send payment for a cart to an address. Instead, the customer first deposits currencies to their own wallet, via their own deposit address, and then when the cart is being paid, the amount is transferred from the user’s wallet to that of the designated admin. This is explained in the WooCommerce payment gateway extension’s homepage.

Hope this helps.

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

with regards

[alexg]

I’ve been looking again into this.

Have you set up fixer.io? If you set up fixer.io, then the plugin knows which coins are crypto and which are not.

Then, fiat coins are not shown in the [wallets_deposit] and [wallets_withdraw] UIs. This feature was implemented in 4.0.0.

Apologies, but I forgot about it! This entire thread could have been much shorter!

[alexg]

Hello,

This is a good idea.

It’s not possible to distinguish between fiat/custom, only between crypto or fiat/custom. I can modify the frontend templates, so that each row has classes denoting whether the base or quote symbol is crypto or fiat/custom. Then you’ll be able to style the rows differently, or even hide one type or the other using CSS.

I can also do this for the main plugin’s UIs. Changes to the parent plugin must happen before any changes to the Exchange extension.

I will notify you here when I release these changes.

with regards

[alexg]

Hello,

Glad it’s working now. You may still want to disable the message queue subsystem, if it’s something you’re not using.

Regarding your other question, I can’t give you a simple answer without more information. Very often clients think they know what they want without an understanding of the difference between business requirements and implementation details. Please open a new thread and describe your client’s motivation for doing this. We can then explore possible solutions.

with regards

[alexg]

OK, thank you for the additional info.

I tested again with Monero 0.16.0.0 and I got the same result.

It appears my installation instructions are outdated, so please accept my apologies; hope you didn’t waste too much time on this. I have now updated the instructions on the adapter’s homepage.

Step 3: I have added the --no-zmq parameter to the monerod command, because now the daemon binds ZMQ to port 18082 by default, but we don’t need it. If you actually need to use ZMQ for a different application connecting to the same wallet, then you should use a different RPC port.

So, the full command would be:

monerod --rpc-bind-port 18081 --rpc-login monero_daemon_user:monero_daemon_pass --no-zmq

Step 4: You should start the wallet CLI with the daemon-login parameter, which should match the username/password that you set on the daemon.

So, the full command would be:

monero-wallet-cli --daemon-login monero_daemon_user:monero_daemon_pass --wallet-file /path/to/monero/wallet

Let the CLI sync the wallet (wallet sync is a separate process to the daemon sync). Then, proceed to start the monero-wallet-rpc service. This is the service that provides the API that the WordPress plugin uses.

Please let me know if you face any more issues.

with regards

[alexg]

Hello @zhak,

If you set the BTC withdrawal fee on the CoinPayments adapter to 40k then this is the fee paid to CoinPayments. This goes to pay the blockchain transaction and a portion is retained by CoinPayments for providing the wallet hosting service. If you were to set the fees to a higher amount, then the rest would remain with your site’s hot wallet. For example, if you set the fees to 50k, then 10k satoshis remain on your site’s hot wallet.

The deposit fee is 0.5%, as imposed by the platform. For more information please see: https://www.coinpayments.net/supported-coins

The CoinPayments platform is provided as a convenience. If you really care about controlling the fees you can set up a full node. However, you would also need to consider the cost of running – and maintaining – a full node wallet into your business plan.

Hope this helps.

with regards

[alexg]

I have reviewed the Token of Trust plugin and it does indeed look like a good fit. It assigns user Roles depending on whether a user is verified.

It is possible to use the Wallets → Capabilities menu to control which Role can do what.

Therefore, an admin can disallow withdrawals or trades for people who are not verified.

Thank you @casperdre, this is a good solution. From now on, Token of Trust what I recommend admins use when they need KYC for legal compliance.

[Author]

Posts