Topic: [ANN][XCN] Cryptonite - NEW Thread | 1st mini-blockchain coin | Bounties! - page 221. (Read 215807 times)

Daily volume 15 BTC :-)
Ready to skyrocket, when the fix is done? ;-)

Thanks pallas! Opened the ports on my router and got conected to 11 peers right away

We will provide a new windows wallet binary when the sync bug is fixed.

Guys any news to post,
Maybe any news on bt38 or maybe other new exchanges,
was wondering if there is already a compiled wallet version out,

beside the price that went to the southpole
because of the northpolo

oops should not have said that,

hope to see it being listed again at more places and back at polo btw,
this one had like 10k average daily volume in the past years, not like some other fake coins,
with devs and their wallet stealers, trojans, botnets etcetera,

so pascal following up on deletable blockchains, and then again the newest xcn will do more then that i guess.

Updated node list (to be put into your cryptonite.conf file):

addnode=106.186.126.57
addnode=118.174.153.195
addnode=137.189.91.64
addnode=137.189.91.71
addnode=158.69.27.82
addnode=178.26.208.109
addnode=180.253.248.218
addnode=182.71.181.102
addnode=188.252.239.235
addnode=193.106.171.8
addnode=24.246.60.145
addnode=46.105.118.15
addnode=68.193.116.54
addnode=77.111.163.71
addnode=77.233.244.74
addnode=82.116.52.170
addnode=85.14.250.2
addnode=86.127.154.22
addnode=89.99.27.94
addnode=91.152.122.132
addnode=92.52.46.192
addnode=93.33.170.142
addnode=96.127.136.18

I've seen that on the headless client on linux as well.


If you open your ports for incoming connections, you will get more that 30 :-)


Well, that is the important thing ;-)

Besides, we are now 3 devs working on the fix, will keep you all posted, on this thread!

I'd also like to describe my Win Wallet behavior. After it stopped crashing a couple of months ago, it's been working pretty flawlessly apart from some minor issues:
1. The wallet regularly micro-freezes for a few seconds.
2. When I open it to sync, the wallet can not establish a stable connection with peers, meaning that it looses connection to them every 20-30 sec (shows 0 connections). Once the wallet is synced, it has a stable 5-8 connected peers (once I've even seen 10 peers )

Sending-receiving works fine.

Unfortunately it doesn't work;


If I delete trie.dat the wallet won't open after the initial loading (CPU usage drops to 0 after a couple of minutes and there's no GUI).

well that older snapshot did in fact sync up fully , just needed to use one older than the 3 day point where it was stuck ... wallet.dat was ok never changed it to get it working again . I really cant make much sense of what happened to be honest . but i did never have this problem till i tried solo mining . so i guess that was the likely cause of it . Thing that rly is wierd , if i did fork why was it still showing payouts from suprnova after that for a while ..... THEN went backwards to 3 days behind and all my transaction where there but not verified ... so damn wierd!!!!!!!!!!! but i am happy its solved and i am a lil more confident that if theres an issue (wierd as it could be) seems to be pretty damn easy to fix , as pallas has mentioned before , keep a backup of your wallet just in case! 

Interesting: trie.dat is part of the blockchain, not of the wallet.
So you replaced that file and it's working fine again?
If that is the issue, we could trigger trie download when such a situation is detected.

My wallet corrupted again. Bit it's not wallet.dat itself but the content of trie.dat now being empty so I just had to use an older backup of it.

good coin to trading

heres last bit of my debug log if that helps at all . can see it stoped on the 3rd which is where my blockcahin was stuck . Im still learning and its hard for me to make complete sense of it but seems somthing wasnt going right .

  here tis - 2017-03-06 12:03:43 ProcessBlock: ACCEPTED 1358160
2017-03-06 12:03:43 ERROR: ReadBlockFromDisk : OpenBlockFile failed
2017-03-06 12:03:43 ReadBlockFromDisk: Could not find block 00000000072e4e2ad210555476a21854aee06ac12f7f54a8fdc4842a0e429734
2017-03-06 12:03:43 receive version message: /Satoshi:0.1.1/: version 10100, blocks=1361599, us=155.143.193.174:8253, them=85.14.250.2:8253, peer=85.14.250.2:37304
2017-03-06 12:03:43 Cannot fastforward chain because of missing data: 00000000016ca234af629b3df816626b6b7e221298fabab3d440c3794ca063a6
2017-03-06 12:03:47 Activate 000000000e156f67e60c2b1168b169adb2236c1782cc0194facc34806b0e9ff2
2017-03-06 12:03:48 Writing file 000000000e156f67e60c2b1168b169adb2236c1782cc0194facc34806b0e9ff2
2017-03-06 12:03:48 Serialized: 238103 bytes
2017-03-06 12:03:48 ProcessBlock: ACCEPTED 1358185
2017-03-06 12:03:48 Cannot fastforward chain because of missing data: 00000000016ca234af629b3df816626b6b7e221298fabab3d440c3794ca063a6
2017-03-06 12:03:51 Activate 000000000e156f67e60c2b1168b169adb2236c1782cc0194facc34806b0e9ff2
2017-03-06 12:03:52 Writing file 000000000e156f67e60c2b1168b169adb2236c1782cc0194facc34806b0e9ff2
2017-03-06 12:03:52 Serialized: 238103 bytes
2017-03-06 12:03:52 ProcessBlock: ACCEPTED 1358145
2017-03-06 12:03:52 Requesting 2 blocks from [2001:0:338c:e558:28d8:9d2:4303:1014]:64041
2017-03-06 12:03:52 Cannot fastforward chain because of missing data: 00000000016ca234af629b3df816626b6b7e221298fabab3d440c3794ca063a6
2017-03-06 12:03:55 Activate 000000000e156f67e60c2b1168b169adb2236c1782cc0194facc34806b0e9ff2
2017-03-06 12:03:56 Writing file 000000000e156f67e60c2b1168b169adb2236c1782cc0194facc34806b0e9ff2
2017-03-06 12:03:56 Serialized: 238103 bytes
2017-03-06 12:03:56 ProcessBlock: ACCEPTED 1358161
2017-03-06 12:03:56 Requesting 4 blocks from 68.193.116.54:63509
2017-03-06 12:03:56 ERROR: ReadBlockFromDisk : OpenBlockFile failed
2017-03-06 12:03:56 ReadBlockFromDisk: Could not find block 0000000016c40a5ce91e747aaa82c850274faf579bd7c9fd3410914a3aca6c85
2017-03-06 12:03:56 receive version message: /Satoshi:0.1.1/: version 10100, blocks=1361599, us=155.143.193.174:54337, them=91.152.122.132:8253, peer=91.152.122.132:8253
2017-03-06 12:03:56 receive version message: /Satoshi:0.1.1/: version 10100, blocks=1361599, us=155.143.193.174:8253, them=0.0.0.0:0, peer=82.116.52.170:55779
2017-03-06 12:03:56 Cannot fastforward chain because of missing data: 00000000016ca234af629b3df816626b6b7e221298fabab3d440c3794ca063a6



like i dunno but those numebrs next to ACCEPTED dont even go in numerical order but they do so in the order on the timeline , seems wierd

You may fork with just one block, but it should reorganize itself automatically, unless you have problems syncing.
Let me know how it goes.

cheers , if this one syncing now doesn't work , will do ^^ . upon further inspection of this situation of mine , i do conclude that i did in fact fork off from the main chain at some point . i could provide a few screenshots of my scrambled transactions in the wallet if it helps , it appears every transaction after 3 blocks i mined solo (payouts from suprnova) was there in the transaction list but the dates were in the wrong order lol and they were not confirmed . The wierdest thing about this whole thing is that i had my wallet open this morning like 6 hours ago , it was synced and everything seemed to be fine ...... for some reason the wallet auto closed itself (it was there open and then it wasnt) ... i was like huh wtf wierd and didnt think much of it , but yeah sincethat moment BAM when i reopen wallet it did this 3 days headers behind thing . im at 4090 blocks behind now on this resync fingers crossed .

     ps. If i did fork from main chain , how the hell does that happen im only mining with 24 megahash .

            cheers .

You may also try the new snapshot I just posted.
Please keep reporting your findings: we are working on fixing the sync bug and every piece of information may be useful.

thanks heaps , it rly was a wierd thing , i tried a few diff blockchain snapshots i backed up myself and BOTH of em would basically sync backwards and end up at 3 days behind on headers (both snapshots were more recent than 3 days tho!) . ive now tried a backup from the 2nd this month (one from longer than 3 days ago) and it seems to be syncing from about 5500 blocks behind now , what i did notice tho is that transactions in my transaction list had weird dates that wernt even in the right order when id sort it by date (everything past a point was not verified by a green tick but was just a blue block in that section that would have the green tick . I think i may have possibly forked on my solo mining attempt the last few days? , it seemed to be working fine and i had been switching from solo to pool....and all working good.... i mined in pool overnight and opened wallet this morning tho and it was broken like this .... i could see my most recent transaction showing was from 6am this morning , but it said 3 days behind on headers . true wigout this one , totally new issue . ill let you know if it finishes its sync successfully or if it wigs again . I have a feeling theres a chasnce it will cause the last snapshot i tried seemed to be syncing at bout 3000 blocks to go then i looked at it 2 mins later and it say 3 days behind on headers lol , ahhhhhh ><

"Cannot fastforward chain because of missing data" means it can't find block data, which is normal for such an old block. Miniblockchain should go ahead and keep the header only. There must be something else.

New blockchain snapshot:

https://mega.nz/#!BVAwgJYY!ZMRKcyzvYijWruSlpJ8BVPMcoAXMv4Bm7ZBaOA6fcRE

the error in debug.log while syncing:

however putting a fully sync'd chain into place, running 'getblockhash 161', we get:
000000044c4e5c82cf3c93a3019f09ecd9005a30f5eeba2ff6952b349c7324ae

james