Topic: [ANN] ADT Androids Tokens repair thread ( new client UPDATE NOW ) - page 15. (Read 46534 times)
January 06, 2014, 10:08:59 PM
might load up on some HBN now that I know a good dev is behind it.
January 06, 2014, 10:08:30 PM
Now for my HBN plug.
You guys should check it out. Version 1.3 will be out this week. It will be very slick, lots of very cool features.
Great PoW mining coin, AWESOME PoS coin. Very smooth, low orphans. and it has me!
So watch for the announcement for version 1.3 later this week, buy or mine a bunch and enjoy one a nice smooth ride
You guys should check it out. Version 1.3 will be out this week. It will be very slick, lots of very cool features.
Great PoW mining coin, AWESOME PoS coin. Very smooth, low orphans. and it has me!
So watch for the announcement for version 1.3 later this week, buy or mine a bunch and enjoy one a nice smooth ride
Thanks for your hard working, I also support your HBN
January 06, 2014, 09:52:40 PM
Now for my HBN plug.
You guys should check it out. Version 1.3 will be out this week. It will be very slick, lots of very cool features.
Great PoW mining coin, AWESOME PoS coin. Very smooth, low orphans. and it has me!
So watch for the announcement for version 1.3 later this week, buy or mine a bunch and enjoy one a nice smooth ride
You guys should check it out. Version 1.3 will be out this week. It will be very slick, lots of very cool features.
Great PoW mining coin, AWESOME PoS coin. Very smooth, low orphans. and it has me!
So watch for the announcement for version 1.3 later this week, buy or mine a bunch and enjoy one a nice smooth ride
January 06, 2014, 09:49:45 PM
block 211096 checkpointed.
I mentioned to Zackclark70 that they should use premine funds to pay for a checkpointing server. Can we have more than one as a fail safe and also a perm node?
No must only have 1. The CP server is good, but if used improperly it can really really foul things up.
A perm node is good idea. A few actually. Each with some coins, separated over a time frame to keep PoS forever moving.
January 06, 2014, 09:48:10 PM
ERROR: mempool transaction missing input
ProcessSyncCheckpoint: sync-checkpoint at f31ab52385e89c1e4bd8f384519245d803c8b6503af9c338022a4b75141886ef
received getdata for: block 598d7a8a90cf73b5442c
getblocks -1 to 00000000000000000000 limit 500
getblocks 210834 to f31ab52385e89c1e4bd8 limit 500
getblocks stopping at 211092 f31ab52385e89c1e4bd8
ERROR: mempool transaction missing input
ProcessSyncCheckpoint: sync-checkpoint at f31ab52385e89c1e4bd8f384519245d803c8b6503af9c338022a4b75141886ef
received getdata for: block 598d7a8a90cf73b5442c
getblocks -1 to 00000000000000000000 limit 500
getblocks 210834 to f31ab52385e89c1e4bd8 limit 500
getblocks stopping at 211092 f31ab52385e89c1e4bd8
ERROR: mempool transaction missing input
These are orpphans. Stop client, restart with -salvagewallet . You will lose address book so export if you need it.
January 06, 2014, 09:45:19 PM
block 211096 checkpointed.
I mentioned to Zackclark70 that they should use premine funds to pay for a checkpointing server. Can we have more than one as a fail safe and also a perm node?
January 06, 2014, 09:44:50 PM
ERROR: mempool transaction missing input
ProcessSyncCheckpoint: sync-checkpoint at f31ab52385e89c1e4bd8f384519245d803c8b6503af9c338022a4b75141886ef
received getdata for: block 598d7a8a90cf73b5442c
getblocks -1 to 00000000000000000000 limit 500
getblocks 210834 to f31ab52385e89c1e4bd8 limit 500
getblocks stopping at 211092 f31ab52385e89c1e4bd8
ERROR: mempool transaction missing input
ProcessSyncCheckpoint: sync-checkpoint at f31ab52385e89c1e4bd8f384519245d803c8b6503af9c338022a4b75141886ef
received getdata for: block 598d7a8a90cf73b5442c
getblocks -1 to 00000000000000000000 limit 500
getblocks 210834 to f31ab52385e89c1e4bd8 limit 500
getblocks stopping at 211092 f31ab52385e89c1e4bd8
ERROR: mempool transaction missing input
January 06, 2014, 09:43:42 PM
block 211096 checkpointed.
January 06, 2014, 09:42:36 PM
I'm pretty sure I'm still on the wrong blockchain. Anyone have any nodes for me connect to?
Stop client delete goto %appdata%/AndroidsToken
delete blk0001.dat, blkindex.dat, peers.dat, and database dir.
Restart..
January 06, 2014, 09:41:22 PM
If ADT is totally fixed this is great work, tranz really does need to be rewarded well for this, a lot of people have mined and bought adt and were really looking forward to this fix.
ALso , Let's start getting moved over to a new coin design before this pos coin goes wrong again. Let's decide on the new coin design and perhaps tranz could be the official coin designer for it.
Zack do you have any idea which coin design the updated ADT should be based upon?
ALso , Let's start getting moved over to a new coin design before this pos coin goes wrong again. Let's decide on the new coin design and perhaps tranz could be the official coin designer for it.
Zack do you have any idea which coin design the updated ADT should be based upon?
Thanks.
FYI you should be good on ADT now I think. No need to move chains. That is not ideal at all IMO.
January 06, 2014, 09:40:56 PM
I'm pretty sure I'm still on the wrong blockchain. Anyone have any nodes for me connect to?
January 06, 2014, 09:40:53 PM
The checkpoint server is alive and running. You should see this message in your client logs.
ProcessSyncCheckpoint: sync-checkpoint at cf645b7bdddda07fedfd134810cc655fbdf72561582a241434b651067a5ab38a
received block 0a68ea8d8acc5666128c
If you don't you are not on right chain...
ProcessSyncCheckpoint: sync-checkpoint at cf645b7bdddda07fedfd134810cc655fbdf72561582a241434b651067a5ab38a
received block 0a68ea8d8acc5666128c
If you don't you are not on right chain...
So with the CP server even just a few connections is ok and relatively safe. Just make sure you are getting sync checkpoints.
January 06, 2014, 09:40:00 PM
If ADT is totally fixed this is great work, tranz really does need to be rewarded well for this, a lot of people have mined and bought adt and were really looking forward to this fix.
ALso , Let's start getting moved over to a new coin design before this pos coin goes wrong again. Let's decide on the new coin design and perhaps tranz could be the official coin designer for it.
Zack do you have any idea which coin design the updated ADT should be based upon?
ALso , Let's start getting moved over to a new coin design before this pos coin goes wrong again. Let's decide on the new coin design and perhaps tranz could be the official coin designer for it.
Zack do you have any idea which coin design the updated ADT should be based upon?
January 06, 2014, 09:39:48 PM
January 06, 2014, 09:39:37 PM
The checkpoint server is alive and running. You should see this message in your client logs.
ProcessSyncCheckpoint: sync-checkpoint at cf645b7bdddda07fedfd134810cc655fbdf72561582a241434b651067a5ab38a
received block 0a68ea8d8acc5666128c
If you don't you are not on right chain...
ProcessSyncCheckpoint: sync-checkpoint at cf645b7bdddda07fedfd134810cc655fbdf72561582a241434b651067a5ab38a
received block 0a68ea8d8acc5666128c
If you don't you are not on right chain...
January 06, 2014, 09:38:12 PM
block 211082
January 06, 2014, 09:37:21 PM
i'm only connected to 2 nodes :/
ya I am only getting 1 -3
Not sure why.. January 06, 2014, 09:37:09 PM
"version" : "v1.5.2.0-adt",
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 62105781.38200200,
"blocks" : 210850,
"moneysupply" : 66792054762.64350128,
"connections" : 0,
"proxy" : "",
"ip" : *.*.*.*",
"difficulty" : 0.30769628,
"testnet" : false,
"keypoololdest" : 1386120848,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
when the new client kicked off all the bad nodes it generated two blockchains. you must have been on the losing blockchain. its ok though restarting the client should connect you to the correct blockchain. As long as you didn't make any transactions on the losing blockchain, you should be fine.
Now intermittent between 0 and 1 peers.
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 62105781.38200200,
"blocks" : 210850,
"moneysupply" : 66792054762.64350128,
"connections" : 0,
"proxy" : "",
"ip" : *.*.*.*",
"difficulty" : 0.30769628,
"testnet" : false,
"keypoololdest" : 1386120848,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
when the new client kicked off all the bad nodes it generated two blockchains. you must have been on the losing blockchain. its ok though restarting the client should connect you to the correct blockchain. As long as you didn't make any transactions on the losing blockchain, you should be fine.
Now intermittent between 0 and 1 peers.
restart your client so you can hop on the correct blockchain.
What would be the reason for it connecting to the wrong one when I did what everyone else did?
So why would it do that, why would it split? Just trying to understand the technology better, that's all.
January 06, 2014, 09:36:42 PM
i'm only connected to 2 nodes 
January 06, 2014, 09:36:22 PM
40 million? damn...I thought my missing 40,000 was a lot
that's a drop in the bucket to my total amount...lets just say that ADT is my retirement money. I have been a big supporter of ADT for a long time and I put my money where my mouth is.
Jump to: