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

[billotronic]

hmmm I know I am johhny come lately to this test but can't seem to get past block 32/33? (yes, I remembered the -tesnet flag! lol)

Looking at my log seems like this repeats about twice a minute or so

Code:

2014-07-09 01:27:56 BitcoinMiner:
2014-07-09 01:27:56 proof-of-work found  
  hash: 00000356467094913d5f7a837057e345141a00617ea54fef866a3a1dbbbb251f  
target: 00000507e17a9d4068797d5657d4493bc23133a1cb0b5762c9b2c02fbd184b0e
2014-07-09 01:27:56 CBlock(hash=00000356467094913d5f7a837057e345141a00617ea54fef866a3a1dbbbb251f, ver=1, hashPrevBlock=000000cf8a29e0b5a25e769b1ce78e6b223c68df257e1640a7045cc71da32e7c, hashMerkleRoot=d648b0f484de5a1d3fe3c466ff5ad61f7ba6b4c2a35e920cff82d2052a396b13, nTime=1404869275, nNonce=14453956059621548966, vtx=1)
2014-07-09 01:27:56   CTransaction(hash=c4be0060b80b1aafe79c241cc1a87df7c50fa7596341ccb8b0cb09283742dbf4, ver=1, vin.size=1, vout.size=1, nLockHeight=33)
    CTxIn(, coinbase )
    CTxOut(nValue=24309.89748219, pubKey=7706deef1bbda2b8d816abefac13325780a4ce23)
2014-07-09 01:27:56   vMerkleTree: d648b0f484de5a1d3fe3c466ff5ad61f7ba6b4c2a35e920cff82d2052a396b13 
2014-07-09 01:27:56 generated 24309.89748219
2014-07-09 01:27:56 Activate 000000cf8a29e0b5a25e769b1ce78e6b223c68df257e1640a7045cc71da32e7c
2014-07-09 01:27:56 Writing file 000000cf8a29e0b5a25e769b1ce78e6b223c68df257e1640a7045cc71da32e7c
2014-07-09 01:27:56 Serialized: 128 bytes
2014-07-09 01:27:56 ProcessBlock: ACCEPTED 33
2014-07-09 01:27:56 CreateNewBlock(): total size 1000
2014-07-09 01:27:56 Mining for trie hash: 626db2cfa1628d9d35851d9a22897133f76cfa85a7be34ea437ff65cdebf59fc
2014-07-09 01:27:56 Running BitcoinMiner with 1 transactions in block (195 bytes)
2014-07-09 01:27:56 Target: 00000507e183a753731ee46247716dc0ca326edee912d48643d3899b157fb0e6

Could the issue be the client is trying to mine before its synced?

[edit] Ok, weirder still. So I changed the gen in the conf, retried, still stuck. Deleted everything, retried, still stuck. This time in the log I am seeing this:

Code:

2014-07-09 01:34:02 Misbehaving: 66.45.239.67:18253 (0 -> 10)
2014-07-09 01:34:03 Misbehaving: 66.45.239.67:18253 (10 -> 20)

and now when I try to do getinfo I am getting this:

Code:

r00t@Hoverquarters ~/Downloads $ ./cryptonited -testnet getinfo
error: {"code":-1,"message":"CDB : Error -30974, can't open database wallet.dat"}

I can still run getmininginfo but nothing is being wrote to the log and restarting doesn't change anything

Which in my mind means its now time for a whiskey break

[edit2] log::: http://pastebin.com/ami8G25s shell output::: http://pastebin.com/qbyMuGz6

[1715297909]

1715297909

[1715297909]

1715297909

[1715297909]

1715297909

[catia]

@Billotronic,   
     Try ed1ab115705979424f1d35ba6afe709e  There was a bug in binary from couple days ago that would cause it to get stuck on block 33. Not sure what is up with your wallet.dat error. Maybe it's somehow an artifact of not being synced.

[surfer43]

Lets just say it uses multiple hashing algorithms and it doesn't include any memory-hard qualities like scrypt.

When is this going to be released? cause i havent slept yet and i need to know

Not really sure... a month or two, maybe more, maybe less.

Any updated eta?

[bitfreak!]

Any updated eta?

Well at this point we hope to do a pre-announcement within 1 or 2 weeks. Then it'll be a week after the pre-announcement that we do the actual announcement and release everything. We still have to do some Windows testing and QT testing, but we're aiming for 2 or 3 weeks at this stage.

[cawson]

Any updated eta?

Well at this point we hope to do a pre-announcement within 1 or 2 weeks. Then it'll be a week after the pre-announcement that we do the actual announcement and release everything. We still have to do some Windows testing and QT testing, but we're aiming for 2 or 3 weeks at this stage.

cpu mined or gpu mined?

[catia]

cpu mined or gpu mined?

Release will include a CPU miner inside of the daemon. Someone will probably create GPU at some point. Also, unless someone steps forward to do it, there will probably not be any mining pools at launch.

[billotronic]

how hard would it be to make a stand alone miner for launch?

[catia]

The miner itself is not hard, I can write it, but it's not useful without a pool. Currently we don't support getblocktemplate in the daemon, which is kind of thing you need for stratum. Originally I didn't think it was possible to do getblocktemplate with cryptonite, now i'm pretty sure that was wrong. It's kind of on the list to add that capability but until somebody is looking at making a pool, it's not real high priority.

Assuming coin can support stratum then it seems there are a number of opensource options to start from. I'm not 100% on where the dragons are, some changes likely required. We can probably work with anyone who is willing and able to deal with the pool software.

One of the advantages of cryptonite's reduced footprint is that it isn't such a big deal to be running full nodes on mining machines. In a way this reduces need for pool, of course if difficulty is very high and coin value is very high, then small miners probably are looking for the profit averaging effects of pool. So maybe we can put it off for a little while. If somebody wants to build it, i'm certainly willing to help.

Another thing we can't have is the coin launching with a single pool. This is almost worse than no pool. So if anybody needs our help on pool code, it will probably have to end up having to be open source in at least some usable form.

[billotronic]

ok then silly question, can I have multiple daemons connect to one central daemon and just mine to one wallet?

[catia]

ok then silly question, can I have multiple daemons connect to one central daemon and just mine to one wallet?

You have a couple of options here. One is to take the wallet.dat file from your main machine and copy it over the file on any miners. This will cause all blocks to get mined into your same accounts, but it is risky because if any miner gets compromised the attacker would have all of your keys. Other possibility is that when you first setup a miner, run dumpwallet to export all keys and then import all keys from all miners into your main setup. So a little bit of work, but no master/slave thing is really needed.

[mrvegad]

I have been playing with my computer time settings and now my log has a ton of these messages:
2014-07-11 05:17:10 ERROR: AcceptToMemoryPool: : coinbase as individual tx
and now i can't connect to server.

[catia]

Can I get your log? How much are you moving time around? Stuff should pretty much stop working if you ever approach 2 hours off.

[billotronic]

ok then silly question, can I have multiple daemons connect to one central daemon and just mine to one wallet?

You have a couple of options here. One is to take the wallet.dat file from your main machine and copy it over the file on any miners. This will cause all blocks to get mined into your same accounts, but it is risky because if any miner gets compromised the attacker would have all of your keys. Other possibility is that when you first setup a miner, run dumpwallet to export all keys and then import all keys from all miners into your main setup. So a little bit of work, but no master/slave thing is really needed.

hmmmm interesting. Option A would be a lot more feasible for my situation and a simple added layer of insurance would just to have the mining wallet feed into a separate wallet on a timer. Thank you for the brain candy sir.

I have been playing with my computer time settings and now my log has a ton of these messages:
2014-07-11 05:17:10 ERROR: AcceptToMemoryPool: : coinbase as individual tx
and now i can't connect to server.

Where have you been hiding? Playing with something other than you system clock I presume?

[mrvegad]

ok then silly question, can I have multiple daemons connect to one central daemon and just mine to one wallet?

You have a couple of options here. One is to take the wallet.dat file from your main machine and copy it over the file on any miners. This will cause all blocks to get mined into your same accounts, but it is risky because if any miner gets compromised the attacker would have all of your keys. Other possibility is that when you first setup a miner, run dumpwallet to export all keys and then import all keys from all miners into your main setup. So a little bit of work, but no master/slave thing is really needed.

hmmmm interesting. Option A would be a lot more feasible for my situation and a simple added layer of insurance would just to have the mining wallet feed into a separate wallet on a timer. Thank you for the brain candy sir.

I have been playing with my computer time settings and now my log has a ton of these messages:
2014-07-11 05:17:10 ERROR: AcceptToMemoryPool: : coinbase as individual tx
and now i can't connect to server.

Where have you been hiding? Playing with something other than you system clock I presume?

the last couple of weeks have been crazy busy at work plus hot weather made my old ass very tired at the end of the day 

anything exciting your way?

[catia]

New releases available now. We have a build bot setup and the outputs are here:

http://gpile.it/cryptonite/

The number at the end is sort build date/time, the bigger the newer. These new builds remove hacks used to statically link boost. So even the CLI client may require you to have additional dependencies installed. These builds will have poor compatibility between linux distros so currently we have different bins for debian wheezy and ubuntu 14.04. If you need builds for a different distro, let us know. New builds are also stripped, this will make debugging more difficult but uploading 500MB to the server is a real pain.

Notice that QT builds are available now. These should work, a couple of features are missing, shouldn't cause much trouble. These again will have additional dependency requirements on your end. Namely libprotobuf and qt4.

Windows builds are there, but they don't work. You will need a collection of dll files to run them which will be coming soon.

[billotronic]

ok then silly question, can I have multiple daemons connect to one central daemon and just mine to one wallet?

You have a couple of options here. One is to take the wallet.dat file from your main machine and copy it over the file on any miners. This will cause all blocks to get mined into your same accounts, but it is risky because if any miner gets compromised the attacker would have all of your keys. Other possibility is that when you first setup a miner, run dumpwallet to export all keys and then import all keys from all miners into your main setup. So a little bit of work, but no master/slave thing is really needed.

hmmmm interesting. Option A would be a lot more feasible for my situation and a simple added layer of insurance would just to have the mining wallet feed into a separate wallet on a timer. Thank you for the brain candy sir.

I have been playing with my computer time settings and now my log has a ton of these messages:
2014-07-11 05:17:10 ERROR: AcceptToMemoryPool: : coinbase as individual tx
and now i can't connect to server.

Where have you been hiding? Playing with something other than you system clock I presume?

the last couple of weeks have been crazy busy at work plus hot weather made my old ass very tired at the end of the day 

anything exciting your way?

Just living the dream sir

New releases available now. We have a build bot setup and the outputs are here:

http://gpile.it/cryptonite/

The number at the end is sort build date/time, the bigger the newer. These new builds remove hacks used to statically link boost. So even the CLI client may require you to have additional dependencies installed. These builds will have poor compatibility between linux distros so currently we have different bins for debian wheezy and ubuntu 14.04. If you need builds for a different distro, let us know. New builds are also stripped, this will make debugging more difficult but uploading 500MB to the server is a real pain.

Notice that QT builds are available now. These should work, a couple of features are missing, shouldn't cause much trouble. These again will have additional dependency requirements on your end. Namely libprotobuf and qt4.

Windows builds are there, but they don't work. You will need a collection of dll files to run them which will be coming soon.

Ok, I'm stupid apparently. I can not get this to run. I've tripled check the permissions but the shell keeps telling my I don't have permission to start it.

[catia]

Try running ldd filename

It should print some lines like libQtGui.so.4 => Unavailable
These need to be rectified by installing whatever.

[mrvegad]

Im using pclinuxos,it's rpm based and I can't get it to run (still trying though).


Edit:Im running into this:
libboost_system.so.1.49.0: cannot open shared object file: No such file or directory

I have libboost 1.42.0 and 1.50.0 and 1.55.0 installed

[catia]

Do you know if your pclinuxos is similar to any fedora releases?

[mrvegad]

Do you know if your pclinuxos is similar to any fedora releases?

It is forked from Mandriva which is forked from Red Hat