tychecoin (OP)
Copper Member
Newbie
Offline
Activity: 170
Merit: 0
|
|
February 19, 2018, 03:42:15 PM |
|
below is the error I keep getting - any clues ?
11:09:04.280000 DEBUG Connection timed out 11:09:04.288000 DEBUG Selected peer: 7729768182152365942 24.11.224.98:17000 [whi te=0] last_seen: d0.h6.m23.s36 11:09:04.303000 DEBUG Connecting to 24.11.224.98:17000 (white=0, last_seen: d0.h 6.m23.s36)... 11:09:05.560000 TRACE JSON-RPC request: {"jsonrpc":"2.0","method":"getlastblockh eader","params":{}} 11:09:05.580000 TRACE JSON-RPC response: {"error":{"code":-9,"message":"Core is busy"},"jsonrpc":"2.0"} 11:09:09.319000 DEBUG Connection to 24.11.224.98:17000 timed out, interrupt it 11:09:09.336000 DEBUG Connection timed out 11:09:09.344000 DEBUG Selected peer: 14696100110712559065 178.62.201.231:17000 [ white=0] last_seen: d0.h18.m39.s56 11:09:09.368000 DEBUG Connecting to 178.62.201.231:17000 (white=0, last_seen: d0 .h18.m39.s56)... 11:09:10.598000 TRACE JSON-RPC request: {"jsonrpc":"2.0","method":"getlastblockh eader","params":{}} 11:09:10.628000 TRACE JSON-RPC response: {"error":{"code":-9,"message":"Core is busy"},"jsonrpc":"2.0"} 11:09:14.394000 DEBUG Connection to 178.62.201.231:17000 timed out, interrupt it
11:09:14.412000 DEBUG Connection timed out 11:09:14.429000 DEBUG Selected peer: 190834398259164380 95.16.18.66:17000 [white =0] last_seen: d0.h8.m2.s32 11:09:14.451000 DEBUG Connecting to 95.16.18.66:17000 (white=0, last_seen: d0.h8 .m2.s32)... 11:09:15.645000 TRACE JSON-RPC request: {"jsonrpc":"2.0","method":"getlastblockh eader","params":{}} 11:09:15.665000 TRACE JSON-RPC response: {"error":{"code":-9,"message":"Core is busy"},"jsonrpc":"2.0"} 11:09:18.131000 DEBUG Closing connection from 127.0.0.1:57113 total=1 11:09:19.466000 DEBUG Connection to 95.16.18.66:17000 timed out, interrupt it 11:09:19.480000 DEBUG Connection timed out 11:09:19.488000 DEBUG Selected peer: 11167976135691124703 47.95.116.161:17000 [w hite=0] last_seen: d0.h8.m48.s43 11:09:19.506000 DEBUG Connecting to 47.95.116.161:17000 (white=0, last_seen: d0. h8.m48.s43)... 11:09:24.519000 DEBUG Connection to 47.95.116.161:17000 timed out, interrupt it 11:09:24.544000 DEBUG Connection timed out 11:09:24.549000 DEBUG Selected peer: 3016547443138793611 98.234.36.205:17000 [wh ite=0] last_seen: d0.h10.m58.s53 11:09:24.562000 DEBUG Connecting to 98.234.36.205:17000 (white=0, last_seen: d0. h10.m58.s53)...
You might be running two instance of demon
|
|
|
|
anam08
Newbie
Offline
Activity: 47
Merit: 0
|
|
February 19, 2018, 04:01:12 PM Last edit: February 19, 2018, 04:24:47 PM by anam08 |
|
Blockchain is working fine latest height 7045 , you may delete the blockchain folder and re-sync
thanks, working now edit: to all.miner that has mining using ahka pool, we are got some problem with payment. will send failed payment tomorrow. already 00:24 @my current time. sorry for the trouble.
|
|
|
|
Pitchie
|
|
February 19, 2018, 05:09:40 PM |
|
I'm in the list Hope you'll pay everything out ASAP
|
$XSCP(XyMcLREar5HupAEFjzqfxGvk7FKQN8yirP)
|
|
|
xavieron
Jr. Member
Offline
Activity: 64
Merit: 1
|
|
February 20, 2018, 09:53:33 AM |
|
The compensation is coming from the developer and not from our pool. I've talked to the developer and I've gotten confirmation that he would indeed compensate the miners on our pool since we were the only pool to continuously run. But this is not from me or from LAB Binary Mining. I'll keep in contact with him and relay the information I get from him.
Thank you for understanding,
-Xav
|
http://labbinarymining.com/ MSR - PNKS - CREP - XAO - BZK - SUMO - IPBC - XUN - BKC
|
|
|
bobeeb
Newbie
Offline
Activity: 7
Merit: 0
|
|
February 20, 2018, 02:45:21 PM |
|
The compensation is coming from the developer and not from our pool. I've talked to the developer and I've gotten confirmation that he would indeed compensate the miners on our pool since we were the only pool to continuously run. But this is not from me or from LAB Binary Mining. I'll keep in contact with him and relay the information I get from him.
Thank you for understanding,
-Xav
thank you for the info/update
|
|
|
|
Arashflash44
Newbie
Offline
Activity: 72
Merit: 0
|
|
February 20, 2018, 08:47:12 PM |
|
04:46:07.845093 ERROR Failed to connect to any of seed peers, continuing without seeds 04:46:14.966819 ERROR Failed to connect to any of seed peers, continuing without seeds 04:46:22.029461 ERROR Failed to connect to any of seed peers, continuing without seeds 04:46:28.491993 ERROR Failed to connect to any of seed peers, continuing without seeds 04:46:35.574167 ERROR Failed to connect to any of seed peers, continuing without seeds 04:46:42.123616 ERROR Failed to connect to any of seed peers, continuing without seeds 04:46:49.293194 ERROR Failed to connect to any of seed peers, continuing without seeds 04:46:55.778676 ERROR Failed to connect to any of seed peers, continuing without seeds
|
|
|
|
vorpalspear
Jr. Member
Offline
Activity: 81
Merit: 1
|
|
February 21, 2018, 12:52:50 AM |
|
no windows wallet=shit coin
no Linux wallet = shitcoin no Mac wallet = shitcoin? no paper wallet = shitcoin no block explorer = shitcoin no Windows wallet = yay no windows no fair? linux so scare? much sad. tiny violin. should have at least a paper wallet generator. That should be the gold standard. announcement thread posted to bitcointalk the day after launch? = fail Liniux command line wallet already there, Mac and Windows wallet I am working on and all are welcome to collaborate in making the same. 2nd thing i used boost 1.55 which is creating problem , 1st we need to upgrade the code to use boost 1.62 and later to make our code easily usable in Visual Studio and other linux platforms. I request you all to collaborate instead of calling shit, anyways shit if properly used is great source of energy Sorry for the confusion. I was just talking about coins in general. And it is just my opinion. I celebrate the fact that you have a linux wallet but no windows wallet. Screw windows, damn it all to hell. And the people that use it, let them rot. In fact you are elite if you have no Windows wallet.
|
|
|
|
Soldierblue63
Newbie
Offline
Activity: 1
Merit: 0
|
|
February 22, 2018, 11:25:17 AM |
|
Hi,I'm a newbie and don't know how to create a tychecash wallet and only have a tablet and no pc,bought the coins but can't store so any advice?
|
|
|
|
fbastage2
Newbie
Offline
Activity: 70
Merit: 0
|
|
February 22, 2018, 12:26:29 PM |
|
daemon does not show synchronization progress.
I had to set set_log 3 to see debug statements to confirm it was getting blocks.
please fix.
---
ubuntu 16.04, built from latest source, github
also, like the person above, I also fail to build some of the auxiliary tools. I think it was 'connectivity_tool'.
At least the daemon and simplewallet are built first in the makefile
|
|
|
|
hechengwine
Newbie
Offline
Activity: 9
Merit: 0
|
|
February 22, 2018, 12:57:35 PM |
|
total supply? 10000 billion?
|
|
|
|
tychecoin (OP)
Copper Member
Newbie
Offline
Activity: 170
Merit: 0
|
|
February 22, 2018, 01:28:43 PM |
|
no windows wallet=shit coin
no Linux wallet = shitcoin no Mac wallet = shitcoin? no paper wallet = shitcoin no block explorer = shitcoin no Windows wallet = yay no windows no fair? linux so scare? much sad. tiny violin. should have at least a paper wallet generator. That should be the gold standard. announcement thread posted to bitcointalk the day after launch? = fail Liniux command line wallet already there, Mac and Windows wallet I am working on and all are welcome to collaborate in making the same. 2nd thing i used boost 1.55 which is creating problem , 1st we need to upgrade the code to use boost 1.62 and later to make our code easily usable in Visual Studio and other linux platforms. I request you all to collaborate instead of calling shit, anyways shit if properly used is great source of energy Sorry for the confusion. I was just talking about coins in general. And it is just my opinion. I celebrate the fact that you have a linux wallet but no windows wallet. Screw windows, damn it all to hell. And the people that use it, let them rot. In fact you are elite if you have no Windows wallet. Take that easy , what u said is true for a number of projects who start and vanish . I didn't take it to heart , and till the time projects prove survival of time and technicalities , it can't be taken on face value for sure .
|
|
|
|
tychecoin (OP)
Copper Member
Newbie
Offline
Activity: 170
Merit: 0
|
|
February 22, 2018, 01:44:39 PM |
|
Hi,I'm a newbie and don't know how to create a tychecash wallet and only have a tablet and no pc,bought the coins but can't store so any advice?
You bought it !! From where ??
|
|
|
|
tychecoin (OP)
Copper Member
Newbie
Offline
Activity: 170
Merit: 0
|
|
February 22, 2018, 01:46:58 PM |
|
daemon does not show synchronization progress.
I had to set set_log 3 to see debug statements to confirm it was getting blocks.
please fix.
---
ubuntu 16.04, built from latest source, github
also, like the person above, I also fail to build some of the auxiliary tools. I think it was 'connectivity_tool'.
At least the daemon and simplewallet are built first in the makefile
Will do that.
|
|
|
|
tychecoin (OP)
Copper Member
Newbie
Offline
Activity: 170
Merit: 0
|
|
February 22, 2018, 01:48:45 PM |
|
total supply? 10000 billion?
80 Billion
|
|
|
|
Recer66
Newbie
Offline
Activity: 4
Merit: 0
|
|
February 22, 2018, 04:54:28 PM |
|
Hi help start a wallet No connection and no balance is displayed here
|
|
|
|
Recer66
Newbie
Offline
Activity: 4
Merit: 0
|
|
February 22, 2018, 07:39:39 PM |
|
Microsoft Windows [Version 10.0.16299.248] (c) Кopпopaция Maйкpocoфт (Microsoft Corporation), 2017. Bce пpaвa зaщищeны.
C:\Users\Hacтя>G:\кoшeльки\TycheCash\Tychecash.exe --add-exclusive-node 139.59.139.74:17000 188.166.12.107:17000 20:14:31.134830 INFO TycheCash v1.1.1.1() 20:14:31.152636 INFO Module folder: G:\ъю°xы№ъш\TycheCash\Tychecash.exe 20:14:31.161640 INFO Initializing p2p server... 20:14:31.164639 INFO Binding on 0.0.0.0:17236 20:14:31.167728 INFO Net service binded on 0.0.0.0:17236 20:14:31.167728 INFO Attempting to add IGD port mapping. 20:14:32.330077 INFO Added IGD port mapping. 20:14:32.345688 INFO P2p server initialized OK 20:14:32.345688 INFO Initializing core... 20:14:32.345688 INFO Blockchain not loaded, generating genesis block. 20:14:32.439443 INFO Blockchain initialized. last block: 0, d2059.h14.m14.s32 time ago, current difficulty: 1 20:14:32.439443 INFO Core initialized OK 20:14:32.439443 INFO Starting core rpc server on address 127.0.0.1:18236 20:14:32.455063 INFO Core rpc server started ok 20:14:32.455063 INFO Starting p2p net loop... 20:14:32.455063 INFO Starting node_server 20:14:32.524101 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:14:32.527101 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:14:32.530102 INFO 20:14:32.530102 INFO ********************************************************************** 20:14:32.530102 INFO The daemon will start synchronizing with the network. It may take up to several hours. 20:14:32.530102 INFO 20:14:32.530102 INFO You can set the level of process detailization* through "set_log <level>" command*, where <level> is between 0 (no details) and 4 (very verbose). 20:14:32.530102 INFO 20:14:32.530102 INFO Use "help" command to see the list of available commands. 20:14:32.530102 INFO 20:14:32.530102 INFO Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved. 20:14:32.530102 INFO ********************************************************************** 20:14:34.622995 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:14:34.622995 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:14:36.700764 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:14:36.700764 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:14:38.788998 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:14:38.792992 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:14:40.865496 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:14:40.865496 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:14:42.944944 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:14:42.944944 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:14:45.008679 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:14:45.024301 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:14:47.109510 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:14:47.109510 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:14:49.182122 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:14:49.197741 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:14:51.291639 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:14:51.291639 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:14:53.373542 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:14:53.373542 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:14:55.452476 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:14:55.468087 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:14:57.550540 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:14:57.554537 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:14:59.627903 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:14:59.632900 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:01.700928 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:01.704927 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:03.769977 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:03.773974 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:05.844086 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:05.848087 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:07.925134 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:07.925134 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:10.005156 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:10.005156 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:12.085531 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:12.085531 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:14.166196 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:14.166196 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:16.372900 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:16.372900 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:18.466921 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:18.466921 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:20.530762 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:20.546388 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:22.614020 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:22.629642 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:24.700998 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:24.704987 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:26.778586 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:26.783585 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:28.857347 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:28.872984 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:30.946207 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:30.946207 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:33.040580 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:33.056191 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:35.126426 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:35.130427 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:37.196440 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:37.201440 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:39.267760 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:39.271758 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:41.338672 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:41.344673 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:43.414488 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:43.430107 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:45.503933 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:45.507932 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:47.578104 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:47.582093 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:49.641807 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:49.641807 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:51.728837 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:51.744452 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:53.815387 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:53.830998 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:55.906507 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:55.910520 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:15:57.971765 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:15:57.971765 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:00.044729 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:00.044729 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:02.199125 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:02.199125 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:04.266035 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:04.281660 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:06.351793 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:06.355793 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:08.424805 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:08.428805 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:10.498809 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:10.503809 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:12.575262 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:12.579252 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:14.641978 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:14.641978 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:16.723121 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:16.728113 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:18.792377 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:18.807988 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:20.895346 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:20.900345 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:22.973901 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:22.973901 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:25.060279 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:25.064591 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:27.132170 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:27.138163 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:29.202600 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:29.202600 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:31.282685 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:31.286683 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:33.352243 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:33.352243 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:35.446153 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:35.450153 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:37.508442 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:37.508442 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:39.591879 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:39.595879 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:41.761438 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:41.765435 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:43.830146 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:43.835149 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:45.912273 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:45.916271 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:47.987948 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:47.991948 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:50.062477 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:50.066474 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:52.174574 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection. 20:16:52.179573 WARNING Failed to HANDSHAKE with peer 139.59.139.74:17000 20:16:54.243700 ERROR [139.59.139.74:17000 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
|
|
|
|
visax
Newbie
Offline
Activity: 322
Merit: 0
|
|
February 22, 2018, 11:01:59 PM |
|
please wallet for debian user
|
|
|
|
GoolGaul
Newbie
Offline
Activity: 19
Merit: 0
|
|
February 23, 2018, 12:52:14 AM |
|
Any thoughts on an exchange? I'd love to see this coin start trading...
|
|
|
|
papilyn
Member
Offline
Activity: 210
Merit: 10
|
|
February 23, 2018, 04:51:25 AM |
|
|
|
|
|
tychecoin (OP)
Copper Member
Newbie
Offline
Activity: 170
Merit: 0
|
|
February 23, 2018, 06:58:52 AM |
|
|
|
|
|
|