[alexg]

Hello,

In the latest version 1.0.3 of the Exchange extension I have addressed the issue regarding timezones. Any new orders/trades will be recorded with the correct time.

Thanks again for spotting this!

with regards

[alexg]

Hello,

These are limit orders. It helps to spell out clearly what they mean:

The first user (market maker) bids to buy 1 LTC and is willing to pay up to a limit of 2 Test per LTC.

Then, the other user (market taker) wants to sell 1 LTC and is asking for as little as 1 Test per LTC.

Therefore the two limit orders match at the rate of the market maker (2 Test per LTC). The format of the market name is BASE_QUOTE, same as in Bittrex. Other exchanges use QUOTE_BASE but I find BASE_QUOTE convenient because the markets can easily be sorted and grouped by base currency.

As for the issue with UTC times, I believe I see the problem now, and will provide a fix shortly.

with regards

P.S. In the future let’s try to use one thread per issue to avoid confusion. Thanks!

[alexg]

Hello,

Glad you found the solution.

For the benefit of others reading this:

The simplest solution would be to name your functions using unique names, for example:

function wallets_multiadapter_coins_filter_coin1( $coins ) {
    $coins['COIN1'] = array(
    
    ...etc...
}

add_filter( 'wallets_multiadapter_coins', 'wallets_multiadapter_coins_filter_coin1' );

…and…

function wallets_multiadapter_coins_filter_coin2( $coins ) {
    $coins['COIN2'] = array(

    ...etc...
}
add_filter( 'wallets_multiadapter_coins', 'wallets_multiadapter_coins_filter_coin2' );

with regards

[alexg]

Hello,

Thanks, I will check.

with regards

[alexg]

Hello,

1. Yes

2. Yes

3. At the time when the vendor withdraws a commission, the commission amount is calculated at that time, taking into account the market rate at the time of the withdrawal, not the time of user checkout. In other words, the actual value transacted matches the fiat value paid by the customer in crypto. A vendor then does not have any incentive to wait for the “best” time to withdraw, by observing any fluctuations in the value of the cryptocurrency.

[alexg]

Hello,

I have not seen this issue. To be sure, can you perform at least one test checkout using the wallets gateway, then see if there is a withdrawal button afterwards?

with regards

[alexg]

Hello,

My apologies for the long delay, it turned out that there were a number of issues with the gateway that had to be fixed before I could give you a reply.

Please see the release notes for version 2.2.0 of the payment gateway: https://www.dashed-slug.net/wcmp-bug-fixes-version-2-2-0/

I have also updated the plugin’s FAQ section. New entries:

• how does checkout work in WCMp?
• how do withdrawals work in WCMp?
• how do refunds work in WCMp?

Please let me know if you have any further questions about the plugin after reading this.

with regards

[alexg]

Hello,

Please see the release notes for version 2.2.0 of the payment gateway: https://www.dashed-slug.net/wcmp-bug-fixes-version-2-2-0/

Refunds are now fixed and are described in the plugin’s homepage. Please let me know if you spot any issues.

with regards

[alexg]

Hello,

It turns out that this was an issue with checkout at the WooCommerce level, not WCMp level. After checkout orders are now set to status “Processing”, as they should.

Please see the release notes for version 2.2.0 of the payment gateway: https://www.dashed-slug.net/wcmp-bug-fixes-version-2-2-0/

with regards

[alexg]

Hello,

Apologies for the long delay, it turned out that there were a number of issues with the gateway. Hopefully I have addressed all of them now, but please let me know if you spot any other issues.

Please see the release notes for version 2.2.0 of the payment gateway: https://www.dashed-slug.net/wcmp-bug-fixes-version-2-2-0/

I have found it is simpler for admins to pay commissions in the same currency as that the user has paid in. This eliminates any need for conversion, which can be done manually by the vendors.

Withdrawals are now fixed and are described in the FAQ section.

with regards

[alexg]

Hello,

Thanks again for your comments. I have moved your post to a new thread, as you have mentioned two issues that are unrelated to the previous one:

About trade times: I have double-checked again the user history and market history views. Everything should be always saved in UTC time in the DB. The times in the frontend are displayed using moment.js, which translates the times to local using the browser. This ensures that each user sees times according to their own timezone. The browser uses the settings from your OS. Can you check that you have set the timezone of the computer you’re using correctly? Also, which views do you see the problem in? As mentioned before, I checked the user history and market history.

About the matching engine: Could you please provide a clear example with values that you think should not match? What bid and what ask did you enter with two different users? Please either provide screenshots or a complete example with actual values, so I can reproduce the issue. Thank you.

with regards

[alexg]

Hello,

Yes, thank you. I am already aware that this is needed since May of 2018. It makes sense. Also, it has been requested before:

​https://www.dashed-slug.net/forums/topic/suggestion/
​https://www.dashed-slug.net/forums/topic/pending-unconfirmed-withdrawals/
​https://www.dashed-slug.net/forums/topic/transactions-filters/
​https://www.dashed-slug.net/forums/topic/some-suggestions-on-the-search-for-transactions-and-possible-automations
​https://www.dashed-slug.net/forums/topic/pending-unconfirmed-withdrawals/

When I find the time to implement this, I will let you know here and there will be an announcement.

with regards

[alexg]

Hello,

1. I am not sure why this is the case. Is it possible for you to set the server time to your local timezone? What happens then?

2. If you have already set up a trigger for the main cron job task, then that is enough. As long as WordPress is being triggered then the Airdrop cron mechanism will also run. It will execute any past (pending) airdrops, at most one per minute, then it will check for any future airdrops again once per minute and will execute any airdrops whose time has come.

3. Regarding the issue with non-matching collations, this is something that you should address before anything else. It is very likely that it causes several user-related issues and yes, it is also likely that it is what’s preventing you from running airdrops for specific roles. The issue might have been created by a plugin that created tables manually without first checking the result of $wpdb->get_charset_collate(); (https://developer.wordpress.org/reference/classes/wpdb/get_charset_collate/)

with regards

[alexg]

Hello again,

Version 1.0.2 is out now. The problem should be resolved. Thank you again for posting and apologies for the delay.

If you set API memoizing to 0 (not memorizing), then it might impact performance, the option is there only because some people experience non-expiring transients for unknown reasons. If you are not facing any issues then it’s best to leave the value at its default. This caches the public outputs of the API so that multiple requests do not slow down your system too much (But, in any case, this should not be your only protection against DoS attacks).

with regards

[alexg]

Hello again,

Another question: in the market where order placement does NOT work,

1. do you get a popup with a new order ID but then the ID never shows up? and

2. is the symbol of one of the coins longer than 5 characters?

If so, I plan to release an update where the character limit for symbols will be 8 characters. If this is the cause of this issue then it will be resolved by the next patch to the Exchange.

with regards

[Author]

Posts