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

[Primitive]

im making some progress!

Keep in mind you're using cryptonited, you should download cryptonite-qt if you want to use the GUI.

im unable to get QT running, but at least i have cryptonited up

appears that mining is also working. 

however, currently i am getting Bans

[1714643380]

1714643380

[1714643380]

1714643380

[1714643380]

1714643380

[bitfreak!]

Qt probably wasn't working for you because you forgot the -testnet flag or didn't download the dll's.

[watuba]

@Primitive whenever you download a new version, you need to delete the entire data folder, which to find in Windows, Click Start, type "run" hit enter, then type in 'explorer %APPDATA%\Cryptonite' enter.  Go up a directory and delete the entire Cryptonite folder(in the Roaming folder), then run the new client with -testnet.

If you use an old data directory for a new version, you will get banned.

Hope that helps!

[Primitive]

i think im just going to have to buy on an exchange lol.  as much as i'd like to help support the network.

[watuba]

I'm on windows qt, and Downloading Blocks for a while now, seems like it's steadily getting farther and farther behind.  I guess the blocks are being generated too fast to sync?

[canonsburg]

Network is acting wonky:



20:25:45

{
"blocks" : 9739,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.00000000,
"errors" : "Warning: Unreachable blocks are being mined. Possible secret chain attack.",
"genproclimit" : 4,
"networkhashps" : 326828,
"pooledtx" : 0,
"testnet" : true,
"generate" : true,
"hashespersec" : 438096
}

[watuba]

In getinfo:

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

EDIT: Ran with -resync and now it appears I'm on a brand new chain.

[mrvegad]

I started with clean install and when downloading chain i am getting: 2014-07-27 03:31:51 Cannot fastforward chain because of missing data: 0000050e541d00f6d9928d4bf8e080da5cfa66767d4502eb40fec8dd6d21cdea

[bitfreak!]

Let me quote what catia posted on the last page:

NOTICE - Please read!!!

There appears to be a very serious bug that is causing individual nodes to go off on their own little forks. Debugging this has been a total nightmare and not very fruitful thus far. After somebody started mining with 100 nodes, it became apparent that the bug is very easy to reproduce and study during very high block rate periods. As such we are switching the testnet to a fixed difficulty of 1.0 for now. The existing chain will still be valid, just new blocks will be mined under the lower difficulty.

We have about 23 hours until launch and this needs to get fixed. Please download the latest binaries and mine if you can. Achieving a network rate of about 1 block/sec would be ideal. 

Latest is 14072620

[Primitive]

can mining be started via the QT GUI?

[watuba]

@bitfreak! just posting errors in case they are of any help

@Primitive  Go Help, Debug, type 'setgenerate true -1'

[Primitive]

@Primitive  Go Help, Debug, type 'setgenerate true -1'

thanks!  that seems to be working (no errors).  is there a way to monitor to see if there is actually anything happening?  also do i need to have created an address first or any other steps?

[watuba]

'getmininginfo' will tell you some stuff
'getinfo' will tell you other stuff
'setgenerate false' to stop mining

[catia]

Thanks everybody. All the mining really helped. New builds are up and they should be able to maintain synced all to the same chain now. In cases where you end up connected to an unresponsive node, there can be up to a minute delay while that node times out. This is more likely during initial download than anywhere else.

There is another critical bug we're working on, but you shouldn't notice it and hopefully it will get all hammered out in time.

Latest 14072700

[Primitive]

has anyone running WINdows QT successfully mined a block?

[restless]

Just noticed this thread... can someone point me where in the thread setting up client is explained?
For testnet of course

10x


PS:
o, using -testnet works ... now...

It would be great if at launch, when will it be btw? There will be small how-to - how to start mining, how to start mining with more than 1 PC ...

[bitfreak!]

has anyone running WINdows QT successfully mined a block?

Yes I've mined plenty of blocks on win64 with qt.

[aaaxn]

Code:

Accepted block 13064
Accept block header
Cannot fastforward chain because of missing data: 0000050e541d00f6d9928d4bf8e080da5cfa66767d4502eb40fec8dd6d21cdea 2
OS 1 NS 1
Accepted block 15001
Accept block header
Cannot fastforward chain because of missing data: 0000050e541d00f6d9928d4bf8e080da5cfa66767d4502eb40fec8dd6d21cdea 2
OS 1 NS 1
(...)
Getting size for height : 21237
OS 21238 NS 21239
Accepted block 21238
Accept block header
Accept block header
Cannot fastforward chain because of missing data: 00000bb228da2a56202ef57b60f7c403dd9bd683278b8fbdd184c048e869dee4 2
OS 21239 NS 21239
Accepted block 21238
Accept block header
Hrm
Accept block header
Getting size for height : 21238
OS 21239 NS 21240
Accepted block 21239

I run 14072703. It synced on 3rd attempt (deleting data every time). First and second run segfaulted, but I don't have log. Maybe it has something to do with unnatural block rate.

[catia]

@aaaxn you are running linux/windows? 14072704 has a fix for one of the segfaults i found. Working on trying to reproduce others but it's very difficult to even get a stack trace because of ASLR. Pretty much have to build from source and run it inside of gdb.

Also we have some situations where the trie download stalls, and once we got a corrupted trie. Stall is being fixed now.

The abnormal block rate is bringing out all kinds of problems. Expect that at normal speeds things will be 60x more reliable.

Edit: 14072707 is up. Seems to be having no problems. On target at T-12 hours.

[Primitive]

has anyone running WINdows QT successfully mined a block?

Yes I've mined plenty of blocks on win64 with qt.

how does the network know my wallet address? (qt)