All PM Sent. For Each Problems PM Me or write here. during the day i will update the Guide  |
|
|
|
I'm going to send the new Version |
|
|
|
Just to add some feedback on market freezes. It is possible to limit read-only API calls (such as get balance, get suggested prices for ping orders) to 60 seconds? I was waiting more than 10 minutes to get balances before I restarted CAT to have the button active and clicked it again. The market freezes often when there is 503 error - is the algo ready to recover from such state? Almost all markets frozen between 19:00 to 01:00, here is the error log (no error in DOS window): 2013-12-29 02:49:23 - HTTP ERROR Server returned HTTP response code: 500 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 04:21:53 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 05:42:39 - Lost An Order (Maybe Cryptsy Problem)EMD/BTC ID 24014132 - Sell 199.86852916@0.00006342 Remaining 0.00000000
2013-12-29 06:07:09 - Lost An Order (Maybe Cryptsy Problem)TGC/BTC ID 24022058 - Buy 198.66272609@0.00002386 Remaining 198.66272609
2013-12-29 09:24:31 - HTTP ERROR Connection timed out: connect TRY TO RECALL
2013-12-29 09:32:33 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 10:15:48 - Lost An Order (Maybe Cryptsy Problem)FST/BTC ID 24024880 - Buy 394.81474599@0.00002709 Remaining 0.00000000
2013-12-29 10:18:32 - HTTP ERROR Connection timed out: connect TRY TO RECALL
2013-12-29 11:17:15 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:01:23 - HTTP ERROR Server returned HTTP response code: 500 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:15:58 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:02 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:05 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:07 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:09 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:10 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:11 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:12 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:13 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:15 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:17 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:19 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:19 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:23 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:23 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:23 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:25 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:26 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:27 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:28 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:16:37 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:27:16 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:29:45 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:29:50 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:29:50 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:29:52 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:29:54 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:29:56 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:29:58 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:29:58 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:05 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:06 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:07 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:09 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:11 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:12 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:14 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:15 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:16 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:18 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:31 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:30:32 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:30:33 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:30:34 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:36 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:30:37 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:39 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:30:39 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:30:45 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:46 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:48 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:30:51 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:30:52 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:52 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:30:55 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:30:57 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:30:59 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:31:13 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:31:14 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:31:15 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:31:17 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:31:20 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:31:20 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:31:26 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:31:31 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:31:32 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:31:33 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:31:36 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:31:38 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:31:41 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:31:55 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:31:55 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:31:56 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:32:30 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:32:45 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:32:51 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:33:00 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:33:02 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:14 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:14 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:14 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:15 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:16 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:16 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:18 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:19 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:19 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:20 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:21 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:22 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:39 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:39 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:41 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:42 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:46 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:40:55 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:40:56 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:40:56 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:40:56 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:43:36 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:43:38 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:43:41 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:43:51 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:50:19 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:53:50 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:54:07 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:54:34 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:58:53 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:58:54 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:58:56 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:58:56 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:58:58 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:00 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:00 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:07 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:08 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:08 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:10 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:10 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:17 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:18 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:18 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:35 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:59:37 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:37 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:39 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:41 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:59:41 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:59:48 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:59:49 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:59:49 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:51 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:51 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 20:59:57 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:59 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 20:59:59 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:00:17 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 21:00:22 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:00:29 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:00:30 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:00:30 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:00:32 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:00:38 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 21:00:40 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:00:40 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:00:58 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 21:01:06 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 21:01:11 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 21:01:14 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:01:15 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:01:22 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 21:01:23 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:01:28 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 21:01:42 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:01:48 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:01:49 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 21:01:51 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 21:01:52 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 21:01:55 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 21:02:04 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:02:04 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 21:02:05 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:02:09 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:02:30 - HTTP ERROR Unexpected end of file from server TRY TO RECALL
2013-12-29 21:02:36 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:15:50 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:16:02 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:16:02 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:16:03 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:16:03 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:16:03 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:16:03 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:16:04 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:16:06 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 21:16:06 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 22:42:01 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 22:46:33 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:17:11 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:17:16 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:17:36 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:17:42 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:22:01 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:32:55 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:32:58 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:32:59 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:33:07 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:33:19 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:42:57 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:57:23 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 23:57:42 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:57:44 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:57:52 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:57:53 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-29 23:58:04 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-29 23:58:22 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-30 00:57:12 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-30 00:57:15 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-30 00:57:17 - HTTP ERROR Server returned HTTP response code: 503 for URL: https://www.cryptsy.com/api TRY TO RECALL
2013-12-30 00:57:54 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-30 00:57:56 - HTTP ERROR Connection reset TRY TO RECALL
2013-12-30 00:57:59 - HTTP ERROR Connection reset TRY TO RECALL
Very Bad Log  What's happens to Cryptsy during that time? I can do something about read/only API but not on all read only API. CAT Is able to recover from HTTP Error, i think the frozen problem is something else and i hope that in the version i'm going to give you, this problem will be resolved. If not, i will resolve in other way, don't worry. |
|
|
|
who can share the best settings for C.A.T. Cryptsy Automatic Trader?
I'm hesitant to get it because the settings looks complex.
C.A.T. is VERY simple (there's a full guide in the main topic). I'm always here (hum........well i sleep && work but i'm always here!) to answer questions. C.A.T. give you a lot of info, but user interaction is very simple. If you are able to create an order on Cryptsy you will be able to use CAT! |
|
|
|
Running last test  |
|
|
|
|
Si ok, è un algoritmo di compattazione che si basa sui blocchi precedenti.
In soldoni tu hai X transazioni che occupano 100 e io te li traduco in 1 Transazione che occupa 1 (detta molto alla cazzo di cane).
Però il fatto degli indirizzi vuoti non c'entra niente, ovviamente, io posso anche generare indirizzi a pc non collegato in rete. Un indirizzo BTC è solo "formalmente" corretto ma non finisce nella chain
|
|
|
|
All my markets are stuck :/ Can't wait for the new release!
New panel looks good.
I Think tomorrow i will give the new release :-) |
|
|
|
This is the New Statistic Panel (it works for single Market and As Sum of all The Markets). There will be a new Statistic Button in the Dashboard  |
|
|
|
vero e' un pericolo che c'e', pero' considera anche che il 90% della blockchain e inutile, in quanto si porta dietro transazioni
ad indirizzi che attualmente sono a saldo 0.
Sicuro? Tecnicamente puoi dire che un indirizzo ha saldo 0 solo dopo aver scorso TUTTA la blockchain e aver recuperato tutte le transazioni inerenti a quell'indirizzo. eh ! hai mai letto il mio thread sul prezzo del bitcoin ? Si, certo. Mi linki il pezzo a cui ti riferisci? Grazie  --------------------------------------------------------------------------------------------------------------------------------------------------- Dati blockchain al 22/12/2013 numero %noOut %dead %su tot %su att diff prec valore %noOut %vdead % su val diff prec --------------------------------------------------------------------------------------------------------------------------------------------------- vuoti (0 BTC) 21859431 0.00% 9.98% 90.4023% 56094 0.00000 0.00% 0.00% 0.0000% 0.00000 al 22 dicembre c'erano il 90,4% di indirizzi a saldo 0 !!!! dato ricavato esattamente come dici tu, parse totale della blockchain dall'inizio a quella data. ultimamente il dato e' abbastanza costante, ci sono poco meno del 10% degli indirizzi con saldo attivo, circa il 90% e' a saldo 0 Infatti io intendevo : cosa rimuovi dalla blockchain? Mica ci sono gli indirizzi vuoti nella blockchain, ci sono le transazioni, che devono rimanere. O mi sto perdendo qualcosa? |
|
|
|
vero e' un pericolo che c'e', pero' considera anche che il 90% della blockchain e inutile, in quanto si porta dietro transazioni
ad indirizzi che attualmente sono a saldo 0.
Sicuro? Tecnicamente puoi dire che un indirizzo ha saldo 0 solo dopo aver scorso TUTTA la blockchain e aver recuperato tutte le transazioni inerenti a quell'indirizzo. eh ! hai mai letto il mio thread sul prezzo del bitcoin ? Si, certo. Mi linki il pezzo a cui ti riferisci? Grazie |
|
|
|
Running 15 markets for 20 hours, 7 markets have been frozen/stuck for a couple of hours.. Red status and nothing in the error log. Do I have to manually close the market and start again? Ofcourse then I have to cancel outstanding orders otherwise I do not have any coins.
Yes. I'm currently work on the % Problems. This is what happens : a Rule occurs (and Win) Before the % -X Rules. In the next version i will remove the first rules. For the Frozen Markets, in the next version there will be a Timer instead of Thread, i think i can resolve the Frozen Error (That actually i don't know the cause). If Timer will not resolve frozen problems, i have another idea (A Super-Timer that check each Markets and identify the Frozen One.) Thanks, Hope next release will fix these problems. Now i'm running CAT to test this. Result seems OK, i have set -0.01 in 5 markets and algo worked! Next release is today o tomorrow |
|
|
|
vero e' un pericolo che c'e', pero' considera anche che il 90% della blockchain e inutile, in quanto si porta dietro transazioni
ad indirizzi che attualmente sono a saldo 0.
Sicuro? Tecnicamente puoi dire che un indirizzo ha saldo 0 solo dopo aver scorso TUTTA la blockchain e aver recuperato tutte le transazioni inerenti a quell'indirizzo. |
|
|
|
Re-launch = Re-start from genesis block?  Never ever! I meant relaunch a re announcement of the coin with a new website, new services and maybe a new client. Welcome to the club of the chocolovers! Thank you! I love the wallet and the logo I'm here to give all the suggestion i have : - Usually all AltCurr site are 1 only site Page with the same Html Text using in the [ANN] Topic. Users usually wants only : Wallet File + Pool - Services comes later, usually when people talks about services before Currency hits an Exchanger or the community knows very well the Coin other users doesn't agreed - Client looks very good like that, really  Point of my discussion is : More Time will pass from the Genesis Block to the Community [ANN] and less users will be interested. Truste me :-) Chococoin, actually have all needed for a good [ANN] Topic (with good html/images). |
|
|
|
Controlla nel topèic ufficiale in cui ho chiesto riguardo il prezzo. la risposta che mi è stat dat è quella che vi ho già esposto,non me la sono inventata io e cmq si può trattare... https://bitcointalk.org/index.php?topic=389238.600 cerca il mio post in questa pagina eil seguente è la risposta alla mia domanda. Ma ti hanno risposto "alla cazzo di cane" |
|
|
|
|
è Scrypt-Jane si mina con CPU se non ricordo male.
|
|
|
|
New function on next version : You can Manage Log FOlder (Logs->Gain + Logs-> Error). There will be a default RootLogs (or you can change after Login Procedure) I will run a test now. If everything goes well i could release Beta3V2 |
|
|
|
Running 15 markets for 20 hours, 7 markets have been frozen/stuck for a couple of hours.. Red status and nothing in the error log. Do I have to manually close the market and start again? Ofcourse then I have to cancel outstanding orders otherwise I do not have any coins.
Yes. I'm currently work on the % Problems. This is what happens : a Rule occurs (and Win) Before the % -X Rules. In the next version i will remove the first rules. For the Frozen Markets, in the next version there will be a Timer instead of Thread, i think i can resolve the Frozen Error (That actually i don't know the cause). If Timer will not resolve frozen problems, i have another idea (A Super-Timer that check each Markets and identify the Frozen One.) |
|
|
|
Hi, can i give a suggestion to the dev of this coin or to Abraxas, author of this topic : https://bitcointalk.org/index.php?topic=384842.0I'm a alternative Miner, and i know something about AltCC and the best Way to have success :-) These are my suggestion (if you create a new topic or edit the current) - Change Title in [ANN] Chococoin Sha256 No Premine. - Bump the topic 5-10 Times/Day - Create a Presentation like the one i have made for Zetacoin : https://bitcointalk.org/index.php?topic=267545.0These 3 Steps will guaranteed : - New Mining Pool. - Many new users - CCC on an Exchanger like Cryptsy CCC is a good coin and the logo is beautiful (probably you don't believe but logo is very important for the success of a coin) but actually is not balanced in difficulty retarget (there's only 1 pool and this is a problem), a single miner with 1 Terrahash can Destroy this coin. Follow my suggestion and you will see....... You are right. These are really nice advices. We must follow that direction, but actually we are gathering resources to do a nice website because the goal of the chococoin are kids and Spanish speakers. That's why didn't do a ANN in the English forum. To have launched the coin without a website could be a mistake, and that is the mistake we are looking to solve right now. But we are in holydays and yet we are looking for a team of people to do that task. When we'll be ready for the re-launch I'll send you a PM to get your help to bump up the thread. Take it for granted. When you use the word "Re-Launch" you mean "New Topic" not restart Chococoin from Block 1 Right? It can be only 1 problems if you delay the [ANN] for more days : people could tell that the launch was made a lot of time, and there are the early adopters who have mined a lot of Chococoin. Actually i'm mining on the Pool, |
|
|
|
|
Currently working on a "System" folder to store all Gain&Errors
And maybe on a way to start CAT without use the BAT File
|
|
|
|
|
Show Posts
