BEARWHALECD only shows 1 open BUY order at counterwallet.io but there are 3 open BUY orders that show up at xcpdex.com
LTBCARD only shows 2 open BUY orders at counterwallet.io but there are 3 open BUY orders at xcpdex.com
ETHXCPCARD only shows 2 open BUY orders at counterwallet.io but there are 4 open BUY orders at xcpdex.com
Ill just post a compiled list of them and edit as I find new ones. All of the following market pairs have discrepancies between counterwallet and xcpdex.
Bah… Well, I was able to put in an order using xcpdex for SJCXCARD and the order went to counterwallet just fine that way. However, when I tried doing a BUY 1 SJCXCARD for 5.1 XCP the order posted as 0.00000001 SJCXCARD at 0.00000005 XCP for a total of 100,000 SJCXCARD.
So not sure what is up with that. Had to cancel that order.
I’ve burnt through about .0025 Bitcoin in miner fees the last 24 hours trying to solve this riddle.
LOL
I’ll try again using xcpdex, this time using full decimals, like buy 1.00000000 for 5.10000000 and see what that looks like but the summaries doing it both ways looks the same…
Order Amount: 1.00000000 SJCXCARD
Order Total: 5.10000000 XCP
Effective Rate:
SJCXCARD/XCP 0.19607843137255
XCP/SJCXCARD 5.1
The last order I put through had an identical summary but for some reason the orders were processed as 0.00000001 SJCXCARD for 0.00000005 XCP for a total of 100,000 SJCXCARD.
Here is the discrepency between the 2 sites. This is viewing the same order on both sites.
xcpdex:
410301 Open 5.1 XCP 1 SJCXCARD 13UwfPDF2a5Dx5sZD8aUm7YKc1HzKkj1Li
counterwallet:
CureCoin 5.1 XCP 100,000,000 SJCXCARD 5.1 XCP 100,000,000 SJCXCARD ~17 days from now (@ Block #413301)
Meanwhile, blockscan is showing the same as counterwallet while xcpdex is showing the correct order amounts. Both counterwallet and blockscan are showing a discrepancy.
A non-solution (as far as non-mobile users are concerned) at the moment is to use something like Indiesquare Wallet (which works with CW pass phrase).
It could be (pure speculation on my side) that one of outdated 3rd party JS libraries in CW is dropping or failing to fetch some orders. I recently submitted a PR for Ubuntu 16.04 support and on that occasion I installed CW and spotted a fair number of warnings related to those, but I’m not good with grunt and npm to figure it out. Just in case you’re interested:
2016-04-29 13:08:35,813|DEBUG: RUNNING COMMAND: cd ~xcp/counterwallet && npm install
npm WARN package.json counterwallet@1.7.0 No license field.
npm WARN peerDependencies The peer dependency grunt-contrib-nodeunit@~0.1.2 included from grunt-chrome-compile will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency grunt-contrib-compress@~0.5.0 included from grunt-chrome-compile will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency grunt-contrib-clean@~0.4.0 included from grunt-chrome-compile will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency grunt-contrib-concat@~0.3.0 included from grunt-chrome-compile will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4.0.0.
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated graceful-fs@1.1.14: graceful-fs v3.0.0 and before will fail on node releases >= v6.0. Please update to graceful-fs@^4.0.0 as soon as possible.
npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v6.0. Please update to graceful-fs@^4.0.0 as soon as possible.
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v6.0. Please update to graceful-fs@^4.0.0 as soon as possible.
npm WARN deprecated npmconf@0.0.24: this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN cannot run in wd phantomjs@1.9.7-15 node install.js (wd=/home/xcp/counterwallet/node_modules/mocha-phantomjs/node_modules/phantomjs)
npm WARN cannot run in wd counterwallet@1.7.0 grunt (wd=/home/xcp/counterwallet)
cryptojs@2.5.3 node_modules/cryptojs
Now, you can’t just do sudo npm install grunt@~0.4.0 to update those, you’d have to do something like sudo su -s /bin/bash -c 'sudo npm install lodash@4.0.0' xcp I believe. But I’m not quite sure and haven’t had time to learn more about it.
I wish I could recall who fixed the first asset that I ran into this problem with. They knew exactly what the issue was and fixed it within 2-3 days of being notified of the issue. It was when there was live chat support built into the counterwallet platform that seems to no longer exist. That individual responded to me reporting the issue there and solved it almost immediately.