Just bought some TIX. Stupid move? 
it has an active trade life but will die if people just buy for short term like all coinsIt's the most used coin on WorkForCrypto.com
Topic: [ANN] [TIX] Tickets | TIX/CNY Market on Bter | First on Cryptsy XPM Market - page 6. (Read 114752 times)
November 30, 2013, 09:29:45 PM
It's the most used coin on WorkForCrypto.com
November 30, 2013, 09:29:14 PM
Just bought some TIX. Stupid move?
Nah, now there is just more room to go back up
November 30, 2013, 09:27:48 PM
Just bought some TIX. Stupid move?
it has an active trade life but will die if people just buy for short term like all coins November 30, 2013, 02:32:45 PM
Just bought some TIX. Stupid move?
November 29, 2013, 09:42:15 PM
I think this is the only thread where ggdice.com is mentioned as supporting TIX so I guess I can use the thread to announce something 
I will be traveling starting on Dec 1st. I will be back January 1st, 2014. If someone makes huge deposits (which happened before), or wins too much, and can't withdraw, the best way to contact me will be through the email available in my profile here. I can't guarantee fast responses, but any issues will likely take at most 48h to be solved.
Thanks.
I will be traveling starting on Dec 1st. I will be back January 1st, 2014. If someone makes huge deposits (which happened before), or wins too much, and can't withdraw, the best way to contact me will be through the email available in my profile here. I can't guarantee fast responses, but any issues will likely take at most 48h to be solved.
Thanks.
November 29, 2013, 08:29:54 PM
botpool down?
I can't access the site but my miner appears to still be connected
I can't access the site but my miner appears to still be connected
November 29, 2013, 03:54:50 AM
Again stop transactions ?
November 29, 2013, 12:55:25 AM
Every thing is working fine at tix.coinmine.pl TIX mining pool, it was Cryptsy that was having the issue. I want to thank feeleep for doing his best to help me out.
November 28, 2013, 05:40:35 PM
Finally my QT sync's completely. After re-downloading the QT and the blocks, now I don't get the damn error anymore. Plus I did all the addnodes too, now I can trust the using QT again...lol
Excellent news. Told you everything was ok
November 28, 2013, 05:35:38 PM
Finally my QT sync's completely. After re-downloading the QT and the blocks, now I don't get the damn error anymore. Plus I did all the addnodes too, now I can trust the using QT again...lol
November 28, 2013, 03:09:05 PM
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap
What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong
Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT
November 28, 2013, 01:47:59 PM
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap
What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong
Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT
Just strange that even if it's a minor issue, why haven't the QT and/or checkpoint been updated? I sent a ticket to Cryptsy about the deposit/transaction issues and believe it's fine to deposit from a pool as long as it's not a P2Pool. I know Cryptsy is having issue with server overload at the moment, hopefully they get those new server online asap and fix any database issues in the transition.
Checkpoint I can do without updating the QT. I'll post the node I'm using to update checkpoints this weekend after Thanksgiving shit is done. It won't help anything except get rid of that error message, though. It doesn't affect functionality at all
So the checkpoint is too old message is the only issue you guys are having with the QT itself? That's a nice easy fix that can be hotfixed. Won't even need to download a new QT, I can just update the checkpoint server
Cool, thanks. Seems like Cryptsy has just fixed the issue with deposit and withdrawals.....It would be nice to kind of spruce up the QT and update it a little, but not a major thing if the checkpoint is getting updated.
We have some fun things planned soon
Right on...Sweet....
November 28, 2013, 01:43:38 PM
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap
What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong
Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT
Just strange that even if it's a minor issue, why haven't the QT and/or checkpoint been updated? I sent a ticket to Cryptsy about the deposit/transaction issues and believe it's fine to deposit from a pool as long as it's not a P2Pool. I know Cryptsy is having issue with server overload at the moment, hopefully they get those new server online asap and fix any database issues in the transition.
Checkpoint I can do without updating the QT. I'll post the node I'm using to update checkpoints this weekend after Thanksgiving shit is done. It won't help anything except get rid of that error message, though. It doesn't affect functionality at all
So the checkpoint is too old message is the only issue you guys are having with the QT itself? That's a nice easy fix that can be hotfixed. Won't even need to download a new QT, I can just update the checkpoint server
Cool, thanks. Seems like Cryptsy has just fixed the issue with deposit and withdrawals.....It would be nice to kind of spruce up the QT and update it a little, but not a major thing if the checkpoint is getting updated.
We have some fun things planned soon
November 28, 2013, 01:39:51 PM
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap
What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong
Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT
Just strange that even if it's a minor issue, why haven't the QT and/or checkpoint been updated? I sent a ticket to Cryptsy about the deposit/transaction issues and believe it's fine to deposit from a pool as long as it's not a P2Pool. I know Cryptsy is having issue with server overload at the moment, hopefully they get those new server online asap and fix any database issues in the transition.
Checkpoint I can do without updating the QT. I'll post the node I'm using to update checkpoints this weekend after Thanksgiving shit is done. It won't help anything except get rid of that error message, though. It doesn't affect functionality at all
So the checkpoint is too old message is the only issue you guys are having with the QT itself? That's a nice easy fix that can be hotfixed. Won't even need to download a new QT, I can just update the checkpoint server
Cool, thanks. Seems like Cryptsy has just fixed the issue with deposit and withdrawals.....It would be nice to kind of spruce up the QT and update it a little, but not a major thing if the checkpoint is getting updated.
November 28, 2013, 01:38:10 PM
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap
What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong
Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT
Just strange that even if it's a minor issue, why haven't the QT and/or checkpoint been updated? I sent a ticket to Cryptsy about the deposit/transaction issues and believe it's fine to deposit from a pool as long as it's not a P2Pool. I know Cryptsy is having issue with server overload at the moment, hopefully they get those new server online asap and fix any database issues in the transition.
Now deposit on Cryptsy working.
November 28, 2013, 12:34:34 PM
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap
What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong
Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT
Just strange that even if it's a minor issue, why haven't the QT and/or checkpoint been updated? I sent a ticket to Cryptsy about the deposit/transaction issues and believe it's fine to deposit from a pool as long as it's not a P2Pool. I know Cryptsy is having issue with server overload at the moment, hopefully they get those new server online asap and fix any database issues in the transition.
Checkpoint I can do without updating the QT. I'll post the node I'm using to update checkpoints this weekend after Thanksgiving shit is done. It won't help anything except get rid of that error message, though. It doesn't affect functionality at all
So the checkpoint is too old message is the only issue you guys are having with the QT itself? That's a nice easy fix that can be hotfixed. Won't even need to download a new QT, I can just update the checkpoint server
November 28, 2013, 12:32:08 PM
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap
What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong
Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT
Just strange that even if it's a minor issue, why haven't the QT and/or checkpoint been updated? I sent a ticket to Cryptsy about the deposit/transaction issues and believe it's fine to deposit from a pool as long as it's not a P2Pool. I know Cryptsy is having issue with server overload at the moment, hopefully they get those new server online asap and fix any database issues in the transition.
November 28, 2013, 12:14:14 PM
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap
What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong
Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT
November 28, 2013, 12:08:49 PM
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
November 28, 2013, 12:05:46 PM
sent coins from coinmine.pl to cryptsy and bter and they are showing up at neither hours later
I'm having the same issue too. I send them from http://tix.botpool.net to cryptsy TIX wallet, nothing at all.
Any idea?
Jump to: