Yes you will need a Counterparty compatible wallet to use the tokens. Also you need to submit a Counterparty compatible address where tokens will be delivered after the sale end.
To buy DataBits in the ICO you will be using ShapeShift which is integrated in the checkout page o you should be able to use XCP too.
thx, but I see no way to buy with XCP from my Counterparty wallet... https://counterwallet.io/ |
|
|
|
|
it is a Counterparty Token and a counterparty wallet needet, how to take part of ICO with XCP?
thx
|
|
|
|
And now, the new Price List. After 6 month of 30/50% Discount i thought a lot about new prices and i think this is a fair new price list. From now, all the prices must be referred to this list  and what is with the prices (or your customer-friendly accommodation ) for already salaried APIs which are no more working because of inadequateness of exchanges like e.g. Btc-e
Bter
TheRockTrading? thx  |
|
|
|
http://rawx.io/en/news/future-of-rawx/Not Found
The requested URL /en/news/future-of-rawx/ was not found on this server. how to get our coins from mcxnow.com? https://bitcointalk.org/index.php?topic=293035.msg3138433#msg3138433https://mcxnow.com/This site can’t be reached
mcxnow.com refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED RAWX has shut down on December 15, 2016.
We are planning to reopen in 2017.
Make sure to check back every now and then.
Withdrawals will be handled until June 31, 2017.
Please note: I can only handle withdrawals from your RAWX balance. I do not have access to balances of old mcxNOW accounts.
To request a withdrawal write an email to withdrawal@rawx.io.
|
|
|
|
|
Hi
Da es sich ja um Counterparty Token handelt und eine counterparty wallet benötigt, gibt es eine Möglichkeit mit XCP an der ICO teilzunehmen?
|
|
|
|
It is a typo of the OP
it is nodemon not nodaemon
both not working... |
|
|
|
I think he wanted to say that he is affected of this, but used the wrong translations of the german word. I'm not sure about the rest of the sentence, but if you don't like errors, why did you use the beta and not just the stable version?  Beta version can always have bugs. you can't blame the dev for it as it should be obvious that something like this can happen. 1. yes that meaning 2. I have installed the beta because of a necessary reboot, CAT had to be closed and it requires consistently hours to get CAT working as is was before the reboot, - therefore restart of CAT shall be done (for me) so infrequently as possible. And because it was time to restart the PC I took the new beta. But you have a point there: in future I will never take beta.  Learning from this mistake |
|
|
|
~snip
npm install -g nodaemon
you are right: it installs it as global in that way. Kudo! npm install -g nodaemon
npm ERR! Linux 4.4.0-59-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "nodaemon"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/nodaemon
npm ERR! 404
npm ERR! 404 'nodaemon' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
|
|
|
|
Actually the error i'm seeing in case of a lost connection are ECONNECT and Socket Hang Up. I could try to handle the socket problem with node.js https parser and handle the ECONNECT error with a file change (for example) so nodemon would immediately restart it (even a dummy.js file would be good). If you want to test it, you can install it with Then launch the bot with Then try to change any settings in config.js or params.js and you will see your bot auto-restarting npm ERR! not a package /home/xxx/trade/gunbot/nodemon
npm ERR! addLocal Could not install /home/xxx/trade/gunbot/nodemon
npm ERR! Linux 4.4.0-59-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "nodemon"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! path /tmp/npm-29947-053bf887/unpack-aa5777fa/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/tmp/npm-29947-053bf887/unpack-aa5777fa/package.json'
npm ERR! enoent ENOENT: no such file or directory, open '/tmp/npm-29947-053bf887/unpack-aa5777fa/package.json'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
|
|
|
|
Mir auch, und wenn ich nur Coins in meiner Wallet halten würde anstatt auf Börsen zu traden, hätte ich heute deutlich MEHR BTCs
Hast du einen herben Verlust erlitten durch Gox? nicht nur Gox..  |
|
|
|
coinexchange and c-cex , both are good exchange
Liqui/TuxExchange |
|
|
|
Thanks for your feedback, glad to hear that it's fire-and-forget, as that's really what I'll need for the small-scale hobbyist purpose I intend (and also to mitigate emotion on my side).
I hope it will be in future fire-and-forget because e.g. today rebootet the router and all tasks have stopped and never revived |
|
|
|
Mir auch, aber wenn ich nur Coins in meiner Wallet halten würde anstatt auf Börsen zu traden, hätte ich heute deutlich weniger BTCs
Mir auch, und wenn ich nur Coins in meiner Wallet halten würde anstatt auf Börsen zu traden, hätte ich heute deutlich MEHR BTCs |
|
|
|
These show up occasionally but regularly. Some more about timeouts but that's just polo being flooded (or slow) or my internet connection.
my assumption is that sometimes if there is a slow internet connection (as it is typically one time a day if all are online) the bot does not resume. I had it already several times that all tasks (Linux Terminator) had stopped at the same time and never recovered... only a Strg+C and restart helping |
|
|
|
I would use 2 different accounts to trade the same coin against different pairs. Anyway: bought at? And sold at ? bought at??? because was also gain of other pairs unfortunately sold all at 925 USDT |
|
|
|
This is not a 4.6 problem, it's only a 4.7 BETA problem. Already fixed You were shocked about what?  I have overwritten all with 4.7 BETA |
|
|
|
IMPORTANT FOR BETA TESTER
A little problem i've already fix (it's a regression problem you won't be affected if you don't load an XML file from CAT 4.6)
- The parameter "STOP PING CREATION IF CURRENT MARKET SELL PRICE IS > X" have default value 0 in CAT 4.6 and 99999+ in CAT 4.7
So if you load a 4.6 XML File, you will have a console message like :
2017-01-31 17:36:27| BSP : |Stop Ping Creation If Current Market Sell Price is > 0.0000| Current Market Sell Price Is : 879.9996
And PING creation won't continue.
Solution : Update that parameter to 9999999 (That is CAT 4.7 Default Value).
I Repeat : In 4.7 OFFICIAL, i've added a check to let's you load a 4.6 File without problems.
Thanks
I was shocked about this and CAT is tranquilized since I got the beta because of no delight to sacrifice pointless time done again... hope it will work in future |
|
|
|
we just managed it. we expect at soonest looking forward to Linux wallet |
|
|
|
Try a short password on the register screen. Also, no special characters.
this is/was the issue ▲▲▲ |
|
|
|
|
Show Posts
