[TEST RELEASE] Cryptonite binary for linux (NEW: Qt and Windows builds)

[mrvegad]

I am having problems with blocks. Will post log and more info when i get off work.

[mrvegad]

Output error:Warning: saved state too old. Fast forward sync may not be possible. Run Resync!

log file https://mega.co.nz/#!Vpc21baJ!JO71UzypRkpNf2ikAgqk_ejWyVisNnoy4s6yttdlHLk

[cawson]

the coin will ipo or not？

[catia]

@mrvegad don't worry about that. just a warning that doesn't print out at the right time yet.

@cawson no IPO's or anything. trying for a fair launch

[billotronic]

my client seems stuck @ block 14022.

Log looks clean but I noticed this in the console output:

Code:

Warning: saved state too old. Fast forward sync may not be possible. Run Resync!!!

Does this mean I need to delete the blockchain and start over?

[mrvegad]

my client seems stuck @ block 14022.

Log looks clean but I noticed this in the console output:

Code:

Warning: saved state too old. Fast forward sync may not be possible. Run Resync!!!

Does this mean I need to delete the blockchain and start over?

Billo, look above and you will find the answer (to life the universe and everything). Peace my brother

[billotronic]

except my block count is not increasing in my getinfo... im getting headers, but not processing blocks.

[edit] and ffs have I done anything but embarrass myself in this thread? lol

[mrvegad]

ok Billo is right, there is something wrong:

getmininginfo:

"blocks" : 13957,
    "currentblocksize" : 143520,
    "currentblocktx" : 999,
    "difficulty" : 1.00000000,
    "errors" : "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications",
    "genproclimit" : 1,
    "networkhashps" : 59634,
    "pooledtx" : 1002,
    "testnet" : true,
    "generate" : true,
    "hashespersec" : 30957


then i am also seeing this:
Accept block header
Update: 17725 17725 16725 17725 1
Update: 16725 16725 16725 17725 0
Update: 13958 17725 16725 17725 1
Update: 17725 17725 16725 17725 1
Update: 16725 16725 16725 17725 0
Update: 13958 17725 16725 17725 1
Update: 14086 16725 16725 17725 0
OS 13958 NS 13958
Update: 13958 17725 16725 17725 1
Accepted block 13958
Accept block header
Update: 17725 17725 16725 17725 1
Update: 16725 16725 16725 17725 0
Update: 13958 17725 16725 17725 1
Update: 17725 17725 16725 17725 1
Update: 16725 16725 16725 17725 0
Update: 13958 17725 16725 17725 1
Update: 14086 16725 16725 17725 0
OS 13958 NS 13958
Update: 13958 17725 16725 17725 1
Accepted block 13958
Accept block header
Update: 17726 16726 16726 17726 0
Update: 16726 16726 16726 17726 0
Update: 17726 16726 16726 17726 0
Warning: saved state too old. Fast forward sync may not be possible. Run Resync!!!
Accept block header
Update: 17726 16726 16726 17726 0
Update: 16726 16726 16726 17726 0
Update: 13958 17726 16726 17726 1
Update: 14086 16726 16726 17726 0
OS 13958 NS 13958
Update: 17726 17726 16726 17726 1
Accepted block 17726
Accept block header
Update: 17727 16727 16727 17727 0
Update: 16727 16727 16727 17727 0
Update: 17727 16727 16727 17727 0
Warning: saved state too old. Fast forward sync may not be possible. Run Resync!!!
Accept block header
Update: 17727 16727 16727 17727 0
Update: 16727 16727 16727 17727 0
Update: 13958 17727 16727 17727 1
Update: 14086 16727 16727 17727 0
OS 13958 NS 13958
Update: 17727 17727 16727 17727 1
Accepted block 17727

[mrvegad]

except my block count is not increasing in my getinfo... im getting headers, but not processing blocks.

[edit] and ffs have I done anything but embarrass myself in this thread? lol

you call it embarrassment i call it opportunity to poke fun at you 

[catia]

So the deal is. If your block count is ever more than 1000 away from the header count it won't be able to sync. Partly because of a bug where it won't even try, partly because other nodes may not even have the missing data. However the warning goes off if the point you originally synced is more than 1000 from the current tip which is almost always true. Currently we don't have an option to do the resyncing without deleting the folder. Bitfreak thinks it should even be done automatically. I think resync is kind of a drastic thing to do without at least talking to the user about it.

If this is the worst problem you are having we are probably doing pretty well. It's mostly a matter of developing better UI for when it is synced etc.

[billotronic]

Ok, so if I understand you correctly, I can delete my data dir and restart and it will sort itself out?

except my block count is not increasing in my getinfo... im getting headers, but not processing blocks.

[edit] and ffs have I done anything but embarrass myself in this thread? lol

you call it embarrassment i call it opportunity to poke fun at you 

Like you need the help sir.

[mrvegad]

I have been busy the last couple of days but will have time this weekend to do more testing.

[bitfreak!]

Sorry we've been so quiet the last few days, we're taking a short break from development but we should get back to it in a few days. Still a bit of work to be done but we're much closer to our goal now.

[billotronic]

boooo!

no wait,
yea! Been out of town on a much needed vacation... now its almost kill the English day so works out well.

[mrvegad]

boooo!

no wait,
yea! Been out of town on a much needed vacation... now its almost kill the English day so works out well.

Good for you billo! hope you and your family had a great time

kill the English day? I thought it was kill the Aliens day? 

[bitfreak!]

Well we're back to work but it might be another few days before we have anything new and worth testing.

[catia]

Hey Folks,

   Sorry for the hiatus there, I needed a little bit of rest. Things are back on track, I think this testing phase may be winding up. I had to reset the testnet blockchain so we are back to ~1522 right now. This was caused by changes needed for a new withdrawal limit feature. This allows you to prove that an address can only spend XXX per block for the next 100 blocks at least. So vendors can in theory be more confident in smaller number of confirmations because even a double spend attack wouldn't really work. Anyways, that makes the coin feature complete now. Everything slated is now included and hopefully working. I really got down and hammered on all those bugs, so unless new ones crop up there shouldn't be any problems.

The startup stuff is still weird, lots of spam. You can tell if it is synced by running getinfo. If getinfo works, and headers and blocks are the same number, you are good to go. I'm currently working on the QT client, so test builds of that will be coming soon. QT will require code with a greater understanding of if it is synced/not. Those utilities should trickle down into the CLI and we can get rid of spam. After QT is out we will be releasing windows builds, so really I think this is the home stretch.

http://gpile.it/files/cryptonited MD5 4924fa31a1e3c2dfe7876ce0b5508b0d

[mrvegad]

nice work

c51wpVLw9TFJmQpRoVcTd2QUNiifffN4ft my new address

Where can we send coins to? None of the address I have work.

I am trying to send to myself but i am getting "Insufficient funds" even though I have 122524.42444559ep

I deleted my old Cryptonite dir and started with a new one for this release.

[catia]

Yeah we changed the first letter to 'c' for testnet and 'C' for main net, so old addresses fail.

Mine are
[
    "cD5BZ9VBKKGabjLvKYeJXbYQAND6h6hA4n",
    "c27RVy6rSoNQD6vuyfJyQiGWm6pjHZ2vVG",
    "cP4xcmyGkSedZahK3fQb24SUSNu9YfDWr1",
    "cKcEKXv56hdNeHKHLUYRJ49fVgPUYsMGhr"
]

Sending to yourself doesn't necessarily work. Your not allowed to create a tx with the source and destination addresses the same. You can send to a different address with money, but in case where listaddressgroupings shows all your money in 1 address, sending to that same address won't work. At least i hope it won't, because tx's with source and destination the same are actually how we encode withdrawal limit setting.

[mrvegad]

Yeah we changed the first letter to 'c' for testnet and 'C' for main net, so old addresses fail.

Mine are
[
    "cD5BZ9VBKKGabjLvKYeJXbYQAND6h6hA4n",
    "c27RVy6rSoNQD6vuyfJyQiGWm6pjHZ2vVG",
    "cP4xcmyGkSedZahK3fQb24SUSNu9YfDWr1",
    "cKcEKXv56hdNeHKHLUYRJ49fVgPUYsMGhr"
]

Sending to yourself doesn't necessarily work. Your not allowed to create a tx with the source and destination addresses the same. You can send to a different address with money, but in case where listaddressgroupings shows all your money in 1 address, sending to that same address won't work. At least i hope it won't, because tx's with source and destination the same are actually how we encode withdrawal limit setting.

working as planned then, i can send to your address but it fails when sending to same address but I am able to send to another address I made.