<<  >> (p.154)
    Author Topic: [ANN][XCN] Cryptonite | 1st mini-blockchain coin | M7 PoW | No Premine  (Read 578582 times)
    bitfreak! (OP)
    Legendary
    *
    Offline Offline

    Activity: 1536
    Merit: 1000


    electronic [r]evolution


    View Profile WWW
    September 24, 2015, 11:47:07 AM
     #3061

    Quote
    1. Upon start wallet can not find any nodes to sync from and the only way I found to fix that was to addnode=IP at cryptonite.conf file, IPs of other nodes found at XCN blockchain explorer.
    The server which was running the seed node is no longer online, I'll probably try to use the explorer node as the seed node but I'll have to rebuild again. At least I know the correct build process for Windows now so it shouldn't be hard. I also want to set up a dns seeder thing on the same server as the explorer which should make it much easier for new nodes to find peers.

    Quote
    2. Once finaly connected to other nodes wallet drops connections very frequently many times dropping to just 1 connection.
    The networking code is the same as Bitcoin so it's either a problem with your connection or a problem inherited from Bitcoin. I think during the sync process it will only download the blockchain from a single peer because that's how Bitcoin was designed to work when we forked from it. Since then Bitcoin has gained the ability to download the chain in a parallel fashion from multiple peers which is something we really need to carry over to Cryptonite.

    Quote
    3. Once syncing starts "Current number of blocks" goes to maybe 1000 but then "Estimated number of blocks" takes over and leads most of the time, with "Current number of blocks" only occassionaly catching up but maybe for 10 to 100 blocks. It takes very long time (day+) for "Estimated number of blocks" to catch up with latest block and only then "Current number of blocks" starts fully catching up but very slowly. I think it would take at least few days to fully sync wallet from scratch.
    It should take no more than hour to fully sync from my experience. Usually when you have problems syncing it's because you're connected to a peer who either has a bad connection or is giving you bad data. Once again I believe this issue is compounded by relying on a single peer for synchronization. Try adding some different peers to your conf file then do a resync.

    Quote
    4. Upon every wallet restart it checks and loads blockchain but then starts with resync (showing some weird values like -232865374 %) that lasts horribly long time.
    This is probably related to the last issue with bad peers. The negative percent thing is a known issue but it shouldn't take a huge amount of time to catch up.

    XCN: CYsvPpb2YuyAib5ay9GJXU8j3nwohbttTz | BTC: 18MWPVJA9mFLPFT3zht5twuNQmZBDzHoWF
    Cryptonite - 1st mini-blockchain altcoin | BitShop - digital shop script
    Web Developer - PHP, SQL, JS, AJAX, JSON, XML, RSS, HTML, CSS
Page 153
Viewing Page: 154