[ANN][66] ★ Coin 66 ★

[cgt99]

For all people who are passing this, please resync your wallet with the official NODES of 66coins .....
1 more time here official 66coin NODE

seed.66coins.com:36666
66.altcoinsexplorer.cf:36666
seed.flowpool.cf:36666

Unortunately they are all offline... 

And at Cryptopia:
66 / BTC market is paused
Unable to sync 66 wallet

[mycoinsstore]

Unortunately they are all offline... 

And at Cryptopia:
66 / BTC market is paused
Unable to sync 66 wallet

I raised a ticket on Cryptopia about 66 coin syncing problem. This is my ticket and answer from Cryptopia's stuff:

#8826 - 66 coin wallet
Category:    Exchange
Status:    Closed
Opened:    12/28/2016 12:57:23 AM
Last Update:    12/28/2016 3:57:25 AM
Ticket description:

Hello!

As I can see you have 66 coin wallet sync problem.
I think this is because your wallet is outdated. accordind to logs, Cryptopia's wallet version is 0.7 and the last 66 coin wallet is 0.8.2.0.
Also, your wallet stuck at block 580364 - this is a second hardfork checkpoint (look at line #61 in last wallet "main.cpp" file).
Here is an official thread: https://bitcointalk.org/index.php?topic=647324.720
Latest 66 wallet sources: https://github.com/mrflow27/66coins
Feel free to contact me if you have questions or need my help.

So, please, upgrade your wallet.
Thanks.

And their answer:

    Sender: sa_ddam21312/28/2016 3:56:56 AM

                   Hi mycoinsstore,

    We did update the wallet and we cant get past block 32004, have tried 6 times, stops at that block every time.

    ./66 getinfo
    {
        "version" : 80200,
        "protocolversion" : 60001,
        "walletversion" : 60000,
        "balance" : 0.00000000,
        "blocks" : 32004,
        "moneysupply" : 5.06874690,
        "connections" : 2,
        "proxy" : "",
        "difficulty" : 0.84721989,
        "testnet" : false,
        "keypoololdest" : 1445978068,
        "keypoolsize" : 101,
        "paytxfee" : 0.00000001,
        "mininput" : 0.00000001,
        "errors" : "WARNING: Displayed transactions may not be correct!  You may need to upgrade, or other nodes may need to upgrade."
    }

    66coin has had constant problems with forks since it was listed, so once resynced I do believe delisting is the only option for Cryptopia as the support cost for this coin is astronomical.

    Until we can sync the wallet all markets will remain paused and the wallet will remain in maintenance.

    Thanks
    Cryptopia Support                

I did some investigation and he is totally right!
If you try to delete 66 blockchain and start from scratch - you will not be able sync past block 32004!
This is because 66 coin was badly forked 2 years ago (FIRST_HARDFORK_BLOCK_HEGHT=32000 in main.cpp file) and after that, original blockchain was broken. So, what does it mean?
This means that no one can start from scratch with new wallet and sync current blockchain. Cryptopia will never sync their wallet, 66 coin will be delisted.

[Jonesd]

Didn't the reward of 66 coin run out anyway? I remember it dropping to 0. Nobody is willing to mine it.

[mrflow27]

For all people who are passing this, please resync your wallet with the official NODES of 66coins .....
1 more time here official 66coin NODE

seed.66coins.com:36666
66.altcoinsexplorer.cf:36666
seed.flowpool.cf:36666

Unortunately they are all offline...  

And at Cryptopia:
66 / BTC market is paused
Unable to sync 66 wallet

Offline?

For me it`s working perfect!!!

[mrflow27]

If people interested in this coin took 3 minutes of their time, and read calmly the whole process this was not happening.

At the end of 2014 I took charge of this coin after the original dev turned off its servers 66coin, and decided to continue giving it maintenance

When the original dev turned off the 66coin server that happened?
Wallet 7.0 only synchronized to block 580364, which I did?

Create a new version 8.2 which is working perfectly that I did with the new version here the fixes that I made correcting

1. Fix 2 bad blocks

2. Fix synchronization

3. Add more Checkpoint

4. Cosmetics Missing

5. added more checkpoints

6. Modified the reward system to the next version of wallet delete the OLD SUPER BLOCK REWARD and create a different formula for SUPER BLOCK REWARD

7. Added 2 more Nodes for backup In case the primary server fails

If they read as I said above I understand that the problem of synchronization with the wallet, was a thing of the past.

Once again and for the last time here the instructions on how everything works !!!!!

READ THIS POST AND ALL RESOLVED!!!

http://Https://bitcointalk.org/index.php?topic=647324.msg12428046#msg12428046


Here is a clear example of a person who does not read and who is honestly using an old version of 66coin

Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.265361
Before: 1d52cd90  00000052cd900000000000000000000000000000000000000000000000000000
After:  1d53165c  00000053165c807d0dd558c40cdb43f6ca5f07832c84d720cbdd81ae0aac4250
FOUND BONUS BLOCK!
ERROR: AcceptBlock() : missing bonus block reward tx
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 2.38.64.73:52746
Disconnected 2.38.64.73:52746 for misbehavior (score=100)

[barrysty1e]

If people interested in this coin took 3 minutes of their time, and read calmly the whole process this was not happening.

At the end of 2014 I took charge of this coin after the original dev turned off its servers 66coin, and decided to continue giving it maintenance

When the original dev turned off the 66coin server that happened?
Wallet 7.0 only synchronized to block 580364, which I did?

Create a new version 8.2 which is working perfectly that I did with the new version here the fixes that I made correcting

1. Fix 2 bad blocks

2. Fix synchronization

3. Add more Checkpoint

4. Cosmetics Missing

5. added more checkpoints

6. Modified the reward system to the next version of wallet delete the OLD SUPER BLOCK REWARD and create a different formula for SUPER BLOCK REWARD

7. Added 2 more Nodes for backup In case the primary server fails

If they read as I said above I understand that the problem of synchronization with the wallet, was a thing of the past.

Once again and for the last time here the instructions on how everything works !!!!!

READ THIS POST AND ALL RESOLVED!!!

http://Https://bitcointalk.org/index.php?topic=647324.msg12428046#msg12428046


Here is a clear example of a person who does not read and who is honestly using an old version of 66coin

Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.265361
Before: 1d52cd90  00000052cd900000000000000000000000000000000000000000000000000000
After:  1d53165c  00000053165c807d0dd558c40cdb43f6ca5f07832c84d720cbdd81ae0aac4250
FOUND BONUS BLOCK!
ERROR: AcceptBlock() : missing bonus block reward tx
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 2.38.64.73:52746
Disconnected 2.38.64.73:52746 for misbehavior (score=100)

Hi mrflow27,

I'd just like to clarify that the issue still does exist; i've just tested using the latest source from https://github.com/mrflow27/66coins.

Code:

After:  1d012e29  000000012e2964d2c50adc50adc50adc50adc50adc50adc50adc50adc50adc5c
SetBestChain: new best=f65cf5e96766f3f44a9c  height=32004  work=178320990108971  date=03/03/14 13:13:24
ProcessBlock: ACCEPTED
received block 90d76fba35db706855e5
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.7993
Before: 1d012e29  000000012e290000000000000000000000000000000000000000000000000000
After:  1d0138e7  0000000138e702caadaf777f4ff660745639d6c5971a2d326d18aeb8423a875f
InvalidChainFound: invalid block=90d76fba35db706855e5  height=32005  work=178324504022016  date=03/03/14 13:33:52
InvalidChainFound:  current best=f65cf5e96766f3f44a9c  height=32004  work=178320990108971  date=03/03/14 13:13:24
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED

I agree with the comment by mycoinsstore, however Cryptopia is well-aware of the fix and is choosing to be difficult.



If i get some time later this evening, I will look into coding a patch that gets around this problem.

james

[vinylfever]

Hello mrflow27,

Maybe you could update the OP or create a new ANN, because the information regarding this coin is not in any case clear.
I am now going sync the wallet again from scratch with the node info you provided in post #721 (https://bitcointalk.org/index.php?topic=647324.msg17302952#msg17302952) and the bootstrap file.
The node you're providing in post #489 https://bitcointalk.org/index.php?topic=647324.msg12428046#msg12428046 is obsolete, since the only node (which you apparently repeated over 80 times) in this post does not match the node in post #721
Which in term gets people to ask for nodes which are then provided but could be obsolete or find nodes on cryptopia which are also obsolete. So If people according to your post #726 use the info you provided (post #489) they will end up asking for nodes....

I connected to the node in post #712 https://bitcointalk.org/index.php?topic=647324.msg16875868#msg16875868 somewhere in november.
In your post #713 you did not mention this node being incorrect as well as for all the other nodes posted on that same page but instead thanked him for his support, which lead me to believe that the node provided in #712 was correct.
So please dev, create a new ANN with in the OP all updated and relevant info so users and/or miners don't work with incorrect wallet versions or obsolete nodes. Simply telling users to go to page 25 to find new source and node info (in which the node info apparently doesn't work) does not prevent users from connecting to obsolete nodes or working with obsolete versions of the wallet, neither does reading 37 pages of this thread.

So it's not:
"Post #726 If people interested in this coin took 3 minutes of their time, and read calmly the whole process this was not happening.
Post #721 As I have said more than 80 times,
There are always desperate people,
That open nodes without doing a connect with the original that in this case would be my server.
Thanks to these people this happens that the blockchain stays stock ..."
And.... having people read 37 pages of this thread just to find the correct information.

But:
0: Understanding why people are using older versions/nodes to older versions instead of name calling..... sigh
1: Create a new ANN with all the right info in one place.
2: Update this post to point the discussion to the new thread and ask if you could have this post removed.
3: Keep the OP in the new thread updated with relevant info regarding the project.
4: Provide exchanges with the new and correct wallet info and nodes.

Which in term will lead to:
1: No more/Less "desperate people" who use incorrect versions or connect to obsolete nodes
2: No more/Less miners generating invalid coins.
3: Exchanges with properly updated wallets and node lists (cryptopia also has a list of nodes on their site)
4: Maybe some users would then create pools and other services like a (working) block explorer because I cannot connect to the current one at the time of writing.

Also there are a some people (me being one of them, post #690) that were asking for nodes because the wallet did not sync and since this is (now) YOUR coin maybe YOU should reply with the correct info or as I stated create a new thread.
Last but not least I want to clear that I am NOT attacking you or this coin/project in anyway. I just wanted to point out the there is something you as dev can do to prevent stuff that a) gets people to use obsolete versions and/or nodes and b) gets the coin delisted.


 
   

[mrflow27]

Hello mrflow27,

Maybe you could update the OP or create a new ANN, because the information regarding this coin is not in any case clear.
I am now going sync the wallet again from scratch with the node info you provided in post #721 (https://bitcointalk.org/index.php?topic=647324.msg17302952#msg17302952) and the bootstrap file.
The node you're providing in post #489 https://bitcointalk.org/index.php?topic=647324.msg12428046#msg12428046 is obsolete, since the only node (which you apparently repeated over 80 times) in this post does not match the node in post #721
Which in term gets people to ask for nodes which are then provided but could be obsolete or find nodes on cryptopia which are also obsolete. So If people according to your post #726 use the info you provided (post #489) they will end up asking for nodes....

I connected to the node in post #712 https://bitcointalk.org/index.php?topic=647324.msg16875868#msg16875868 somewhere in november.
In your post #713 you did not mention this node being incorrect as well as for all the other nodes posted on that same page but instead thanked him for his support, which lead me to believe that the node provided in #712 was correct.
So please dev, create a new ANN with in the OP all updated and relevant info so users and/or miners don't work with incorrect wallet versions or obsolete nodes. Simply telling users to go to page 25 to find new source and node info (in which the node info apparently doesn't work) does not prevent users from connecting to obsolete nodes or working with obsolete versions of the wallet, neither does reading 37 pages of this thread.

So it's not:
"Post #726 If people interested in this coin took 3 minutes of their time, and read calmly the whole process this was not happening.
Post #721 As I have said more than 80 times,
There are always desperate people,
That open nodes without doing a connect with the original that in this case would be my server.
Thanks to these people this happens that the blockchain stays stock ..."
And.... having people read 37 pages of this thread just to find the correct information.

But:
0: Understanding why people are using older versions/nodes to older versions instead of name calling..... sigh
1: Create a new ANN with all the right info in one place.
2: Update this post to point the discussion to the new thread and ask if you could have this post removed.
3: Keep the OP in the new thread updated with relevant info regarding the project.
4: Provide exchanges with the new and correct wallet info and nodes.

Which in term will lead to:
1: No more/Less "desperate people" who use incorrect versions or connect to obsolete nodes
2: No more/Less miners generating invalid coins.
3: Exchanges with properly updated wallets and node lists (cryptopia also has a list of nodes on their site)
4: Maybe some users would then create pools and other services like a (working) block explorer because I cannot connect to the current one at the time of writing.

Also there are a some people (me being one of them, post #690) that were asking for nodes because the wallet did not sync and since this is (now) YOUR coin maybe YOU should reply with the correct info or as I stated create a new thread.
Last but not least I want to clear that I am NOT attacking you or this coin/project in anyway. I just wanted to point out the there is something you as dev can do to prevent stuff that a) gets people to use obsolete versions and/or nodes and b) gets the coin delisted.


 
   

Ok vinylfever
You're right on some things

Thanks for your point of view, I'll be writing a new ANN with all the recent info from 66coin,
I will also be compiling the blockexplorer that we had before so to have a little more control

On the other hand
I just realized that it is true what you say there is a source that is not correct
addnode = 66coins.com: 36691

This is the right one
addnode=66coins.com:36666

Second node
addnode=flowpool.ddns.net:36691

On the other hand, understands that obviously at this time, at some point the ip of the nodes change and for such reason do not coincide sometimes, but today I take the trouble to hire 1 ip static for the server !!

At the moment I have been doing tests since 5 PM puerto rico time,
and now are 5:10 a.m.
And so far everything running normal on my server.

Today in the afternoon I will be writing a new ANN so that everything is clear and thanks for some of your suggestions!!

[vinylfever]

Thanks for your reply mrflow27 and your welcome.
I'll try to mine a block when my wallet is synced (will probably be in the new year) and check with you (PM) if I'm on the correct chain.
I wish you happy new year (in advance).

-v-

[cgt99]

Fully synced blockchain up to block 1050535.

Use wallet version 0.8.2

The zip is 503MB and file contains:
\database\log.0000000149
blk0001.dat
blkindex.dat

download and extract it to your datadir.

always make a backup of wallet.dat first

Link:  https://ufile.io/3fdbf

getblockhash 1050535
08151bbc5c9d7dfa8a43d584c01e832313fbee4db8c5cb4fb735a8bd93a424f8

http://66.altcoinsexplorer.cf/index.php?block_hash=08151bbc5c9d7dfa8a43d584c01e832313fbee4db8c5cb4fb735a8bd93a424f8

[mycoinsstore]

cgt99, do you realize that Cryptopia or any other exchange won't accept blockchain from you or someone else stranger?
If wallet can't be synced from scratch from official blockchain - then coin is dead.

Btw, "official 66 coin nodes" (for example 24.139.103.209) generating ORPHAN blocks, that "official 66 coin wallet v.0.8.2" refuses to accept 

received block f5a3ff472cb5d98c3afc
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.556936
Before: 1d08f674  00000008f6740000000000000000000000000000000000000000000000000000
After:  1d08f58b  00000008f58b5572a3c5631fe46ae1d4e700dca8f158c7f91ab87539c0372b4b
FOUND BONUS BLOCK!
ERROR: AcceptBlock() : missing bonus block reward tx
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 24.139.103.209:64216
Disconnected 24.139.103.209:64216 for misbehavior (score=100)

[cgt99]

cgt99, do you realize that Cryptopia or any other exchange won't accept blockchain from you or someone else stranger?
If wallet can't be synced from scratch from official blockchain - then coin is dead.

Btw, "official 66 coin nodes" (for example 24.139.103.209) generating ORPHAN blocks, that "official 66 coin wallet v.0.8.2" refuses to accept 

received block f5a3ff472cb5d98c3afc
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.556936
Before: 1d08f674  00000008f6740000000000000000000000000000000000000000000000000000
After:  1d08f58b  00000008f58b5572a3c5631fe46ae1d4e700dca8f158c7f91ab87539c0372b4b
FOUND BONUS BLOCK!
ERROR: AcceptBlock() : missing bonus block reward tx
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 24.139.103.209:64216
Disconnected 24.139.103.209:64216 for misbehavior (score=100)

Yes i know exchanges need to sync from scratch.
I think they can do it by using V.0.7.0 up to block 580364 and then switch to V.0.8.2 .
This is retarded and needs to be fixed.

I was just offering a way  for anyone else to sync fast to the "correct" chain as it appears to be forks.

I thought it was finally time to get some action with this coin but it seems to be the same old song... 

[mycoinsstore]

cgt99, do you realize that Cryptopia or any other exchange won't accept blockchain from you or someone else stranger?
If wallet can't be synced from scratch from official blockchain - then coin is dead.

Btw, "official 66 coin nodes" (for example 24.139.103.209) generating ORPHAN blocks, that "official 66 coin wallet v.0.8.2" refuses to accept 

received block f5a3ff472cb5d98c3afc
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.556936
Before: 1d08f674  00000008f6740000000000000000000000000000000000000000000000000000
After:  1d08f58b  00000008f58b5572a3c5631fe46ae1d4e700dca8f158c7f91ab87539c0372b4b
FOUND BONUS BLOCK!
ERROR: AcceptBlock() : missing bonus block reward tx
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 24.139.103.209:64216
Disconnected 24.139.103.209:64216 for misbehavior (score=100)

Yes i know exchanges need to sync from scratch.
I think they can do it by using V.0.7.0 up to block 580364 and then switch to V.0.8.2 .
This is retarded and needs to be fixed.

I was just offering a way  for anyone else to sync fast to the "correct" chain as it appears to be forks.

I thought it was finally time to get some action with this coin but it seems to be the same old song... 

Exchanges won't play with "version changing magic". Definitely.

Sad, but truth - current wallet version 0.8.2 - is a bad fork of original 66 coin, because original blockchain can't be synced from scratch.

Look at this and you'll see that current blockchain have multiple forks:

Code:

getpeerinfo
[
{
"addr" : "216.186.159.185:62956",
"services" : "00000001",
"lastsend" : 1483397776,
"lastrecv" : 1483397776,
"conntime" : 1483366258,
"version" : 60001,
"subver" : "/66:0.8.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 930237,
"banscore" : 0
},
{
"addr" : "162.255.117.105:63678",
"services" : "00000001",
"lastsend" : 1483397776,
"lastrecv" : 1483397776,
"conntime" : 1483366470,
"version" : 60001,
"subver" : "/66:0.8.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 32004,
"banscore" : 0
},
{
"addr" : "98.115.147.74:37178",
"services" : "00000001",
"lastsend" : 1483397776,
"lastrecv" : 1483397776,
"conntime" : 1483373313,
"version" : 60001,
"subver" : "/66:0.8.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1010775,
"banscore" : 0
},
{
"addr" : "46.59.60.179:65473",
"services" : "00000001",
"lastsend" : 1483397828,
"lastrecv" : 1483397829,
"conntime" : 1483397272,
"version" : 60001,
"subver" : "/66:0.7.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 262192,
"banscore" : 0
},
{
"addr" : "27.252.186.131:50202",
"services" : "00000001",
"lastsend" : 1483397999,
"lastrecv" : 1483397938,
"conntime" : 1483397936,
"version" : 60001,
"subver" : "/66:0.8.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1047786,
"banscore" : 0
},
{
"addr" : "84.140.141.102:54162",
"services" : "00000001",
"lastsend" : 1483398495,
"lastrecv" : 1483398495,
"conntime" : 1483398303,
"version" : 60001,
"subver" : "/66:0.8.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1064065,
"banscore" : 0
}
]

P.S. Why do you think that your blockchain version is "correct" ?

[barrysty1e]

hey guys,

cheers for repeating what i've basically just said in one post (up there).
i can confirm the chain cgt99 has posted is correct, as it matches the chain running on mrflow27's node, up to block 1051847 as i write this.

ive posted several times in this thread regarding not being able to sync from scratch.
first you have to use 0.7 source to get to block 580xxx, then to latest to sync full chain.

i'd offered a few days back to provide a fix/patch for mrflow27's sources so it corrects the problem and we all just move on (as i had in the past).
honestly cant be stuffed now see how i go for time later this week

james

[mrflow27]

cgt99, do you realize that Cryptopia or any other exchange won't accept blockchain from you or someone else stranger?
If wallet can't be synced from scratch from official blockchain - then coin is dead.

Btw, "official 66 coin nodes" (for example 24.139.103.209) generating ORPHAN blocks, that "official 66 coin wallet v.0.8.2" refuses to accept 

received block f5a3ff472cb5d98c3afc
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.556936
Before: 1d08f674  00000008f6740000000000000000000000000000000000000000000000000000
After:  1d08f58b  00000008f58b5572a3c5631fe46ae1d4e700dca8f158c7f91ab87539c0372b4b
FOUND BONUS BLOCK!
ERROR: AcceptBlock() : missing bonus block reward tx
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 24.139.103.209:64216
Disconnected 24.139.103.209:64216 for misbehavior (score=100)

Obviously rejecting, if there are still people trying to mine and synchronize with old wallets

[mrflow27]

hey guys,

cheers for repeating what i've basically just said in one post (up there).
i can confirm the chain cgt99 has posted is correct, as it matches the chain running on mrflow27's node, up to block 1051847 as i write this.

ive posted several times in this thread regarding not being able to sync from scratch.
first you have to use 0.7 source to get to block 580xxx, then to latest to sync full chain.

i'd offered a few days back to provide a fix/patch for mrflow27's sources so it corrects the problem and we all just move on (as i had in the past).
honestly cant be stuffed now see how i go for time later this week

james

100% correct

[mrflow27]

cgt99, do you realize that Cryptopia or any other exchange won't accept blockchain from you or someone else stranger?
If wallet can't be synced from scratch from official blockchain - then coin is dead.

Btw, "official 66 coin nodes" (for example 24.139.103.209) generating ORPHAN blocks, that "official 66 coin wallet v.0.8.2" refuses to accept  

received block f5a3ff472cb5d98c3afc
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.556936
Before: 1d08f674  00000008f6740000000000000000000000000000000000000000000000000000
After:  1d08f58b  00000008f58b5572a3c5631fe46ae1d4e700dca8f158c7f91ab87539c0372b4b
FOUND BONUS BLOCK!
ERROR: AcceptBlock() : missing bonus block reward tx
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 24.139.103.209:64216
Disconnected 24.139.103.209:64216 for misbehavior (score=100)

Yes i know exchanges need to sync from scratch.
I think they can do it by using V.0.7.0 up to block 580364 and then switch to V.0.8.2 .
This is retarded and needs to be fixed.

I was just offering a way  for anyone else to sync fast to the "correct" chain as it appears to be forks.

I thought it was finally time to get some action with this coin but it seems to be the same old song...  

Exchanges won't play with "version changing magic". Definitely.

Sad, but truth - current wallet version 0.8.2 - is a bad fork of original 66 coin, because original blockchain can't be synced from scratch.

Look at this and you'll see that current blockchain have multiple forks:

Code:

getpeerinfo
[
{
"addr" : "216.186.159.185:62956",
"services" : "00000001",
"lastsend" : 1483397776,
"lastrecv" : 1483397776,
"conntime" : 1483366258,
"version" : 60001,
"subver" : "/66:0.8.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 930237,
"banscore" : 0
},
{
"addr" : "162.255.117.105:63678",
"services" : "00000001",
"lastsend" : 1483397776,
"lastrecv" : 1483397776,
"conntime" : 1483366470,
"version" : 60001,
"subver" : "/66:0.8.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 32004,
"banscore" : 0
},
{
"addr" : "98.115.147.74:37178",
"services" : "00000001",
"lastsend" : 1483397776,
"lastrecv" : 1483397776,
"conntime" : 1483373313,
"version" : 60001,
"subver" : "/66:0.8.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1010775,
"banscore" : 0
},
{
"addr" : "46.59.60.179:65473",
"services" : "00000001",
"lastsend" : 1483397828,
"lastrecv" : 1483397829,
"conntime" : 1483397272,
"version" : 60001,
"subver" : "/66:0.7.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 262192,
"banscore" : 0
},
{
"addr" : "27.252.186.131:50202",
"services" : "00000001",
"lastsend" : 1483397999,
"lastrecv" : 1483397938,
"conntime" : 1483397936,
"version" : 60001,
"subver" : "/66:0.8.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1047786,
"banscore" : 0
},
{
"addr" : "84.140.141.102:54162",
"services" : "00000001",
"lastsend" : 1483398495,
"lastrecv" : 1483398495,
"conntime" : 1483398303,
"version" : 60001,
"subver" : "/66:0.8.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1064065,
"banscore" : 0
}
]

P.S. Why do you think that your blockchain version is "correct" ?

I'm already working
Creating version 8.3 to try to synchronize with it without needing to use old versions or bootstrap.
So that exchanges can synchronize without problems and all people.

I will be reporting the process here, as soon as I see the process to be successful then I create the ANN with all relevant information

Happy new year to all

[mycoinsstore]

cgt99, do you realize that Cryptopia or any other exchange won't accept blockchain from you or someone else stranger?
If wallet can't be synced from scratch from official blockchain - then coin is dead.

Btw, "official 66 coin nodes" (for example 24.139.103.209) generating ORPHAN blocks, that "official 66 coin wallet v.0.8.2" refuses to accept 

received block f5a3ff472cb5d98c3afc
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.556936
Before: 1d08f674  00000008f6740000000000000000000000000000000000000000000000000000
After:  1d08f58b  00000008f58b5572a3c5631fe46ae1d4e700dca8f158c7f91ab87539c0372b4b
FOUND BONUS BLOCK!
ERROR: AcceptBlock() : missing bonus block reward tx
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 24.139.103.209:64216
Disconnected 24.139.103.209:64216 for misbehavior (score=100)

Obviously rejecting, if there are still people trying to mine and synchronize with old wallets

Really? Look closely, all these wallets have your last official version 0.8.2!

[wahyusakti60@yahoo.com]

66 to the moon!

[mrflow27]

cgt99, do you realize that Cryptopia or any other exchange won't accept blockchain from you or someone else stranger?
If wallet can't be synced from scratch from official blockchain - then coin is dead.

Btw, "official 66 coin nodes" (for example 24.139.103.209) generating ORPHAN blocks, that "official 66 coin wallet v.0.8.2" refuses to accept  

received block f5a3ff472cb5d98c3afc
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.556936
Before: 1d08f674  00000008f6740000000000000000000000000000000000000000000000000000
After:  1d08f58b  00000008f58b5572a3c5631fe46ae1d4e700dca8f158c7f91ab87539c0372b4b
FOUND BONUS BLOCK!
ERROR: AcceptBlock() : missing bonus block reward tx
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 24.139.103.209:64216
Disconnected 24.139.103.209:64216 for misbehavior (score=100)

Obviously rejecting, if there are still people trying to mine and synchronize with old wallets

Really? Look closely, all these wallets have your last official version 0.8.2!

Ok good no problem...........


    },
    {
        "addr" : "2.38.64.73:56206",
        "services" : "00000001",
        "lastsend" : 1483441644,
        "lastrecv" : 1483441660,
        "conntime" : 1483441610,
        "version" : 60001,
        "subver" : "/66:7.0.0/",  <<<<<<----------------------------- boom
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 927133,
        "banscore" : 0
    }
]



getblocks 927133 to 00000000000000000000 limit 500
  getblocks stopping at limit 927632 70f3bb4e5d2e59bcdb36
received block da225243da01239ea221
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.265361
Before: 1d52cd90  00000052cd900000000000000000000000000000000000000000000000000000
After:  1d53165c  00000053165c807d0dd558c40cdb43f6ca5f07832c84d720cbdd81ae0aac4250
FOUND BONUS BLOCK!
ERROR: AcceptBlock() : missing bonus block reward tx
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 2.38.64.73:36666
Disconnected 2.38.64.73:36666 for misbehavior (score=100)