Author

Topic: [ANN][HUC] Huntercoin - Worlds First Decentralized Game/World on the Blockchain - page 262. (Read 879724 times)

sr. member
Activity: 490
Merit: 250
what about a wallet without the game ?
Exchanges and pool don't need to have the game in it, so why not just providing a simple wallet version.

I also do have a couple of HUC left which I can't sell just because I am 12 days back and I don't want to ruin my SSD and wait for it to sync.

sr. member
Activity: 1176
Merit: 265
Game is so different now. Some players have 40-50 teams and stay in a spot. Difficult to find coins now Smiley
I remember the first day, I get around 1000 coins and was enough stupid to sell for 0.2 btc the 1000 looool.

Those players ARE coins Smiley
sr. member
Activity: 481
Merit: 252
I try the Linux daemon and crash, I try to have it on windows also and the pool on Linux.

the Linux one crash, I am not able to use it. the windows one run in no responding mode for seconds, then works again for some time, both systems I test have more then 16gb ram, dual 6 cores xeons, sas 15k rpm so the problem is in the code.

if I make time, I will try to debug it.

Definitely there is a problem with the linux wallet.

Qt freezes on any disk operation.  This is clear when you run it with the Qt debugger.

Are the disk operation threads all blocking threads?  Are they blocking Qt?

Or is it that there are so many players (20 000?) that the chain cannot be updated in the time between blocks, which is about 1 minute?

I do see app.processEvents() here and there, but is it in the critical (disk) loops?

Qt is the main loop, and should not be waiting for the threads.  Is that the mistake in the code?

Heavy disk activity is a known issue with Namecoin, which is the basis of Huntercoin:
http://forum.namecoin.info/viewtopic.php?f=21&t=1556

Perhaps one could just restore the Namecoin files like net.cpp and net.h to the original Bitcoin formats?
hero member
Activity: 619
Merit: 501
https://www.massict.com/
I try the Linux daemon and crash, I try to have it on windows also and the pool on Linux.

the Linux one crash, I am not able to use it. the windows one run in no responding mode for seconds, then works again for some time, both systems I test have more then 16gb ram, dual 6 cores xeons, sas 15k rpm so the problem is in the code.

if I make time, I will try to debug it.
full member
Activity: 140
Merit: 100
Game is so different now. Some players have 40-50 teams and stay in a spot. Difficult to find coins now Smiley
I remember the first day, I get around 1000 coins and was enough stupid to sell for 0.2 btc the 1000 looool.
hero member
Activity: 887
Merit: 1000

does this translate to huntercoin too?  I have been spoiled by Bitcoin and the ease it is to scan a QR code and have access to your coins. 
sr. member
Activity: 481
Merit: 252
The same thing happens also with Namecoin when the daemon is stopped.  Not sure where it comes from and whether or not it is a problem.

EDIT: Just checked it, for me the error is
Code:
UnlockRange: lock_error: boost::lock_error
...
Not sure if it is related to the problem you are experiencing.  But to my knowledge this error message never caused problems for me in Namecoin or Huntercoin.


Domob

If you run the client in Qt Creator after compiling and check the Window->Output Panes->Compile Output window you will see how the following operations freeze the huntercoin-Qt client:

askfor tx
askfor block
sending getdata
received getdata
AcceptToMemoryPool


The Flushing wallet.dat delay (about 30 seconds) was another problem but it was easy to get rid of.  I think these problems are also in Namecoin, but with far fewer transactions they are tolerable there.

I'm using Lubuntu 13.04, with a fairly slow drive.

Are the disk operation threads blocking or non-blocking?  Are they blocking the Qt interface from operating? 
legendary
Activity: 1135
Merit: 1166
The same thing happens also with Namecoin when the daemon is stopped.  Not sure where it comes from and whether or not it is a problem.

EDIT: Just checked it, for me the error is
Code:
UnlockRange: lock_error: boost::lock_error
...
Not sure if it is related to the problem you are experiencing.  But to my knowledge this error message never caused problems for me in Namecoin or Huntercoin.
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
I'm on the latest one my man, & I'm merge mining NMC, IXC, I0C, BTC, DVC, GRP without issues...... Smiley

EDIT: I'm pretty sure it's a boost problem, this is what I get when I close it manually:

lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argumentUnlockRange: lock_error: boost: mutex lock failed in pthread_mutex_lock: Invalid argument

.......this is the shortened version........ Cheesy
legendary
Activity: 1807
Merit: 1020
please fix the crash problem of the wallet, I did try to add it on my pool to make my miners happy but the wallet crash every 2-3min, and also consume more that 40-50% CPU the other coins are at 0.5-0.7% on my 6cores xeons.

if you want to succeed please do the wallet for Linux to work






did you allow it to download the chain? (maybe why it's using cpu?).. when a block comees in there will be a small spike, but shouldn't be using 40-50% all the time.. although, i'm not sure how mining effects it..

also check the new commit  by manicminer pool, maybe help will setup?
currently 2 large pools and some smaller ones are mining .. i know they have periodic crashes but not every 2-3mins, i'm assuming once every few hours, could be another issue.
I know there is an issue with the daemon, and if it's not fixed in a day or 2, i'll put up a bounty to get it sorted sooner..


I have to agree with them mate, it's impossible to merge mine this coin while the daemon keeps crashing randomly, sometimes it's every other minute & other times it's every other day - I've been merge mining this coin since it's inception on a 300gh/s system & not got a single HUC out of it, it's just not working.

Better get that bounty out there buddy  Cheesy

PS: The new commit crashes also.

check the latest one.. it's not to fix the random daemon crashes..

the 2 big pools have been mining none stop, albiet with auto-restarting the daemon, so am not sure how yours isn't working but theirs is.. also manic minerpool is working

will see if I get a response from some people today, and if there is no progress i'll put up a bounty..

p.s, are you able to merge mine namecoin?
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
please fix the crash problem of the wallet, I did try to add it on my pool to make my miners happy but the wallet crash every 2-3min, and also consume more that 40-50% CPU the other coins are at 0.5-0.7% on my 6cores xeons.

if you want to succeed please do the wallet for Linux to work






did you allow it to download the chain? (maybe why it's using cpu?).. when a block comees in there will be a small spike, but shouldn't be using 40-50% all the time.. although, i'm not sure how mining effects it..

also check the new commit  by manicminer pool, maybe help will setup?
currently 2 large pools and some smaller ones are mining .. i know they have periodic crashes but not every 2-3mins, i'm assuming once every few hours, could be another issue.
I know there is an issue with the daemon, and if it's not fixed in a day or 2, i'll put up a bounty to get it sorted sooner..


I have to agree with them mate, it's impossible to merge mine this coin while the daemon keeps crashing randomly, sometimes it's every other minute & other times it's every other day - I've been merge mining this coin since it's inception on a 300gh/s system & not got a single HUC out of it, it's just not working.

Better get that bounty out there buddy  Cheesy

PS: The new commit crashes also.
legendary
Activity: 1610
Merit: 1000
Crackpot Idealist
Looks like Poloniex is acting up again.


need a normal exchange service

It's generally pretty good. It's quite young, so all things considered, I'd say it's pretty good so far.

I would have to agree, I sometimes wonder about the dev's thought process, but all in all I'd say its pretty damn good for as old as it is.

It's not btc-e, but its sure not cryptsy either
full member
Activity: 182
Merit: 101
Huc game is great... often annoys me... but I like it... Smiley
sr. member
Activity: 448
Merit: 280
16,500 Players !

Amazing, hit 20,000 very soon Smiley
sr. member
Activity: 364
Merit: 250
Super Smash Bros. Ultimate Available Now!
The game is getting a lot more players, and it makes it harder.

Anyone have any strategies that they'd like to share?

http://huntercoin.info/ go to chokepoints or try stealing the crown. SmileySmiley

Its a pvp game, why whould anyone give away their strats?  Cheesy

 Grin
newbie
Activity: 24
Merit: 0
Its a pvp game, why whould anyone give away their strats?  Cheesy
newbie
Activity: 24
Merit: 0
The game is getting a lot more players, and it makes it harder.

Anyone have any strategies that they'd like to share?
copper member
Activity: 1380
Merit: 504
THINK IT, BUILD IT, PLAY IT! --- XAYA
Looks like Poloniex is acting up again.


need a normal exchange service

It's generally pretty good. It's quite young, so all things considered, I'd say it's pretty good so far.
full member
Activity: 168
Merit: 100
Looks like Poloniex is acting up again.


need a normal exchange service
Jump to: