Ninjastic
PostEdited versionsQuotes to this post
Post
Topic
Board Announcements (Altcoins)
Re: [XCR] Crypti | DPoS | 100% own code | Dapp Store
by
Litoshi
on 13/05/2015, 11:22:45 UTC
Quote from: patmast3r on May 13, 2015, 11:00:01 AM
Quote from: Litoshi on May 13, 2015, 10:57:32 AM
Quote from: patmast3r on May 13, 2015, 10:48:04 AM
Quote from: Litoshi on May 13, 2015, 09:53:15 AM
With Windows, it is not a good idea to use the full node.  Use the Crypti Lite wallet instead.

There is an issue with the time sync within Windows that causes forks and the inability to sync the block chain.  In future releases, Boris is not going to release Windows versions of the full wallet because of this issue.  Windows versions will be Lite wallets only.  Full wallets will be Linux based.

You can try deleting the blockchain.db file and restarting the node.  This usually works.

What kind of issue is that ? Like what does it cause ?

With a 10 minute block time, or even a one minute per block time, the time on your windows computer can be off a few seconds from the official NIST time and still forge or sync.  But with the XCR 10 second block times, a difference of a few seconds in the time on your windows machine and the network time, as synced with NIST, has caused failures to forge blocks and forking of the block chain for that machine.  

It is a problem with Windows, not with Crypti.  

I'm guessing because the network is rejecting blocks that are outside of a certain time threshold (like too far in the future or past) ?


If a block sent to a Windows machine, or any delegate, is not returned in sufficient time, the block is sent to the next delegate in line to forge. The only affect on the network is a 10 second or so lengthening of the present 101 block cycle.  The delegate that forged that block too late is now on a possible fork.  At the end of the 101 block cycle, the network self corrects all delegates that may have forked, as well as updating the votes cast during that cycle, and moving delegates in or out of the standby mode to the 101 club.


If the delegate that missed forging in time is on a fork, and it is 80 blocks down, it can take awhile to resync.  Meanwhile, forging of blocks continues on the network as that delegate attempts to catch up.  Now, what if that delegate is sent another block to forge before completing the block chain sync?  Further forking?  I dont know for sure, but it is not helping to secure the network.