[alexg]

Thanks for the info. This is related to the other error you reported. If the cron job is not running, then that’s the reason for the transactions not confirming. Focus on determining why the cron job is not running, following my recommendations on the other thread.

with regards

[alexg]

Hello,

The plugin does not ever throw a 502 error, therefore it doesn’t look like your request is reaching the plugin.

You should check intermediate things, like your CDN, .htaccess file, check your access logs, etc.

Can you enable verbose debug output and check if the cron job starts? i.e.

1. Go to Wallets -> Cron job -> Verbose log output (debug) and enable the setting.

2. Check your WordPress debug log. When you trigger the cron link, it should write to the logs:

cron jobs STARTED
… (etc)
cron jobs FINISHED

Do you see the start and finish lines?

If you see only the start but not the finish, please let me know, because the cron jobs are crashing mid way for some reason.

If you do not see the start message, the problem is not with the plugin and you should try configuring your CDN, firewalls, etc.

Let me know please what you find.

with regards

[alexg]

Knockout does not bind observables to hidden values, even if you try. However from your code it doesn’t look like you’ve even tried to add any bindings.

Instead, follow the instructions I gave earlier. There is no reason for you to use knockout for this, as you have nothing that needs synchronizing. Some plain old jQuery or even vanilla JavaScript will do the trick.

with regards

[alexg]

Hello,

Thanks, that’s a valid point.

In the future I plan to add an email notification to potentially notify users about filled orders. This will make it clearer to the user what part of which order was filled at what rate, but must also be able to be turned off.

If a part of the order is filled immediately after placement, this info can also be added to the response message. I will have to look into this.

with regards

[alexg]

Thanks Megan,

I appreciate your help. Don’t put any more effort into it. When I do get around to do this task I will take it from there, and it will be done right for all the template types.

with regards

[alexg]

Tether costs around $1 most of the time, but not always so. If I’m not mistaken, its price is near $1 because its issuer is prepared to buy it at $1, or sell it for $1 in large quantities. Anyone who attempts to sell it for less or buy it for more, will not be competitive in the market.

To achieve the same, you could enter very large orders of your coin in your market around the price you want to set. Of course you would first have to own these coins, but since you are issuing the coin, you should be able to do this easily.

with regards

[alexg]

@bigblue The option you mention is there so that user requests do not get slowed down by the subsystem that downloads exchange rates.

If you set up a cron job trigger, then all the data downloads will occur on those triggers, rather than during user requests.

To set up a cron job trigger, simply set up something that hits the cron url periodically. How you do this is up to you. On most linux systems, its a simple matter of running curl on a cron. I believe cpanel also lets you do this if you don’t have shell access.

with regards

[alexg]

I have just now uploaded 0.7.1-beta, which fixes the issue with the market history table.

Again, thanks for spotting it!

I will keep you updated on this thread about displaying the market depths.

with regards

[alexg]

Hello Megan,

I see the bug you’re referring to. I’ll fix it ASAP for the next patch. Thanks!

The orderbook structure is something that I do like to add soon. Thanks for the HTML, it will be helpful.

with regards

[alexg]

You can always start over if you empty the two tables:

TRUNCATE wp_wallets_orders;
TRUNCATE wp_wallets_trades;

To be clear, this will remove all exchange data. Don’t do this unless you really want to delete everything!!!

If you also need to reverse the trades that have been already executed, so that the funds are returned to the users as if the trades never happened:

DELETE FROM wp_wallets_txs WHERE category='trade';

Before you do anything else, could you please run this query? I’d like to understand if these orders are still open due to some sub-satoshi amount not having been filled.

SELECT amount,filled,status FROM wp_wallets_orders WHERE ( amount - filled ) < 0.00000001 AND amount > filled;

If you can email or post me the output, it will be very helpful for me to see what’s going on.

Thanks again

with regards

[alexg]

Hello,

By “bad” I assume that you mean the amount is zero.

I believe this is due to a previous version that had allowed this type of order to be inserted. I am not certain if the amounts are zero or if they are simply less than one satoshi, there is no way to tell from the screenshot.

In any case, the user who entered the orders should be able to cancel them, from the [wallets_exchange_orders] UI. This should be the easiest way.

Another way would be to directly delete them from the database:

1. Backup your database.

2. Assuming that your table DB prefix is wp_, you can do this in your SQL console:

DELETE FROM wp_wallets_orders WHERE amount < 0.000000001;

(That’s eight zeroes after the decimal, followed by a 1) This will delete all orders with amounts less than one Satoshi.

[alexg]

Not really. The plugin cannot be used for token sales.

Of course, if you want to distribute a large number of coins at some set price, you could do what they do at YoBit with ICOs. That is, they set buy/sell walls.

But the exchange is built for markets, not sales.

[alexg]

I do not believe there is a hard limit on scalability, but be reasonable. Don’t expect to fit millions of users on a MySQL database.

Another bottleneck is the server resources. Every JSON API call requires some CPU, memory and disk resources. You can minimize this by slowing down or disabling frontend polling.

But if you are planning to have hundreds of thousands of users, that means that your business is large enough that you can hire a team of developers to build you a brand new system from scratch. No need to base it on WordPress. There are far more efficient platforms out there, the advantage of WordPress on a LAMP stack is its ease of use and large user base, not its performance.

I am guessing that this plugin can be used with up to a few thousand users on a powerful server. YMMV.

with regards

[alexg]

I believe it should work.

The plugin does not use this RPC command and does not need txindex or rescan.

If you do have any results, I will appreciate any info you can post.

with regards

[alexg]

Hi Alex

It worked

Thanks for awesome support :).

Have a nice day

Regards

Joe

[Author]

Posts