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
Topic: [TEST RELEASE] Cryptonite binary for linux (NEW: Qt and Windows builds) - page 4. (Read 19296 times)
July 26, 2014, 11:52:12 PM
July 26, 2014, 10:47:16 PM
'getmininginfo' will tell you some stuff
'getinfo' will tell you other stuff
'setgenerate false' to stop mining
'getinfo' will tell you other stuff
'setgenerate false' to stop mining
July 26, 2014, 10:45:46 PM
@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?
July 26, 2014, 10:43:41 PM
@bitfreak! just posting errors in case they are of any help
@Primitive Go Help, Debug, type 'setgenerate true -1'
@Primitive Go Help, Debug, type 'setgenerate true -1'
July 26, 2014, 10:41:11 PM
can mining be started via the QT GUI?
July 26, 2014, 10:37:55 PM
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
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
July 26, 2014, 10:34:00 PM
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
July 26, 2014, 10:30:28 PM
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.
"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.
July 26, 2014, 10:27:10 PM
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
}
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
}
July 26, 2014, 10:02:55 PM
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?
July 26, 2014, 09:20:59 PM
i think im just going to have to buy on an exchange lol. as much as i'd like to help support the network.
July 26, 2014, 09:16:23 PM
@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!
If you use an old data directory for a new version, you will get banned.
Hope that helps!
July 26, 2014, 09:04:01 PM
Qt probably wasn't working for you because you forgot the -testnet flag or didn't download the dll's.
July 26, 2014, 08:16:49 PM
Quote
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
July 26, 2014, 07:39:05 PM
Quote
im making some progress!
Keep in mind you're using cryptonited, you should download cryptonite-qt if you want to use the GUI. July 26, 2014, 07:36:42 PM
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
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
July 26, 2014, 07:26:13 PM
im making some progress!
July 26, 2014, 07:23:13 PM
wherever you put it. probably downloads folder or something
what is downloaded is called win64_cryptonited_14072614.exe. its on my desktop.
I also have some content that was created in /Roaming/Cryptonite (presumably when i ran the .exe?)
July 26, 2014, 05:25:00 PM
wherever you put it. probably downloads folder or something
what is downloaded is called win64_cryptonited_14072614.exe. its on my desktop.
I also have some content that was created in /Roaming/Cryptonite (presumably when i ran the .exe?)
July 26, 2014, 05:19:17 PM
wherever you put it. probably downloads folder or something
Jump to: