Conversation:
Notices
-
their mailing list (1) has some more info, e.g. "This is another unintended consequence of yesterday's #attack. Because some registrations were added to the #invalid chain and then discarded, they were already included into the transaction index (txindex was originally used in bitcoin for monetary transactions, here this is the user registration but the name "transaction" was kept)." https://groups.google.com/forum/#!topic/twister-users/gpEaKwH153I
-
#twister's stuck (1), a guy has a fix (2) but you know... a little show stopper right now. (1) "Downloading block chain, please #wait before continuing (block chain is 0.43 days old). number of blocks in block chain: #18969 time of the last block: Sun Jan 12 2014 12:48:18 (2) "For the record, I reverted the following 2 commits, recompiled #twisterd, and now the blockchain…
-
now: 18972 blocks, 7 connections and 768 peers
-
18977 but: DHT network down
-
seems this is the #current block, now #waiting (again) that other peers accept "this new user"
-
Here's an issue (1) which fits to this specific environment in testing: one needs specific access to the #router (didn't retry #miniupnp recompile). I wonder also if the twister option "force connection to peer" is something what #retroshare speaks of as having a #relay buddy ? (1) https://github.com/miguelfreitas/twister-core/issues/44 cc @question
-
4 months later, comparison: known peers: 6929, active DHT nodes: 51, connections: 8, #twister client version: 00.09.20.00
-
4 months later, comparison: 82% more block chains (Number of blocks in block chain: 34548), but: Time of the last block: Tue May 06 2014 10:03:21, so I guess there needs to be still downloaded
-
RT @kseistrup I don't have any suggestions except you can choose other ports (you need 2 open #TCP ports for communicating with other nodes). re: http://oracle.skilledtests.com/conversation/255696#notice-435319