Topic: [ANN] [TIX] Tickets | TIX/CNY Market on Bter | First on Cryptsy XPM Market - page 8. (Read 114727 times)
November 26, 2013, 12:38:57 PM
Just passed gold coin and up to about 850k. 100 coming soon. Digicoin is next on the list
November 26, 2013, 11:35:37 AM
Scratch that, about to break $800k
November 26, 2013, 10:59:24 AM
$650k+ Market Cap now. Bet you guys wish you had listened when I said it would sky rocket, huh? 
November 26, 2013, 02:26:43 AM
only stales y Hw!!!!!! why?
You are using the wrong mining program or your .bat is wrong
November 26, 2013, 02:26:11 AM
$400k market cap now. Told you it would be before Thanksgiving Still time to get in, not to 100 yet
Still time to get in, not to 100 yet 
November 25, 2013, 09:07:37 PM
only stales y Hw!!!!!! why?
November 23, 2013, 05:36:04 PM
I can not make any action in the pool
November 18, 2013, 10:42:40 AM
closed my pool for good, ill put the db up with my new pool's for people to collect their balances.
November 11, 2013, 11:52:12 PM
the price is lower
November 11, 2013, 11:51:13 PM
I am using the GPU miner provided and attempted to mine on coinmine.pl - miner shows "Block Found for Pool 0!" but nothing is reflected on coinmine - not even a hashrate. Are additional settings need?
Hi - whats your account id? I will check it
feeleep
November 11, 2013, 09:08:53 PM
I am using the GPU miner provided and attempted to mine on coinmine.pl - miner shows "Block Found for Pool 0!" but nothing is reflected on coinmine - not even a hashrate. Are additional settings need?
November 07, 2013, 12:34:55 AM
Updated the github for the getbalance issue. Sorry it took so long
Uhm.. when using github it is good to reference the issue that was fixed in the commit, so the issue also gets closed and a reference between the two is created.
That other issue I mentioned after you said the checkpoint was fixed seemed to go away after restarting the daemon, by the way.
November 07, 2013, 12:18:22 AM
Updated the github for the getbalance issue. Sorry it took so long
November 03, 2013, 09:35:15 AM
If you are still getting that checkpoint message, PM me and I will give you a node to add that will fix it
Well, I don't. Instead I get a much cooler message:
Code:
"errors" : "EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_21thread_resource_errorEEEEE \nboost::thread_resource_error \nLotteryTickets in ProcessMessages() \n"
November 03, 2013, 08:39:10 AM
If you are still getting that checkpoint message, PM me and I will give you a node to add that will fix it
November 03, 2013, 08:18:48 AM
Checkpoints have been updated, that message should be gone today
Working on the update that was posted to github right now
Working on the update that was posted to github right now
November 03, 2013, 07:57:45 AM
November 03, 2013, 07:55:54 AM
Cleaned up post a bit - workforcrypto.com looks nice so far good job
October 31, 2013, 10:16:26 AM
October 30, 2013, 04:21:09 PM
That's the first one. We haven't even launched it yet we are still working on it. I'm not going to beg you not to drop it, but we have the dev team working on more projects to support the coins instead of pumping out new bullshit than any others you will find.
Where is this unknown dev team ? https://github.com/LotteryTickets/LotteryTickets is abandoned, there is a pending patch there for fixing the getbalance bug.
It's not abandoned at all. There are many known ways around that particular issue and it will be addressed in the clients next update. It's not enough for an update on its own
That is an issue that affects many coins. To say it's a TIX problem is a bit unfair, even though we will have it fixed in the next update
Have you used github and git before ? An active dev team would surely reply to open issues, and apply the patches if appropriate or discuss the issue. Applying a patch doesn't involve making a new release. It is a TIX problem since that repo is the TIX repo, the patch there shows it is a bug in TIX. If you forked this from anywhere else, that is also a bug in the other coin, to which you should apply the same patch.
The "many known ways around" that issue are all bad workarounds, especially when the fix is a very simple one which eliminates all of them.
Jump to: