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

[watuba]

Yes, I was trying what you and catia described below.  Is that the wrong way to do it?

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.

[1715456651]

1715456651

[billotronic]

damn thats not what I wanted to hear... was fixing to set that up tonight myself.

[watuba]

Well please do try it yourself.  I've been known to do things the wrong way   Maybe catia put strict ban requirements for now or something.

[billotronic]

mayhaps... I was banned last night for reasons unknown so we shall see

[watuba]

Everytime I get banned, I feel a little guilty, like I did something wrong

[watuba]

Tried it again on a new instance, and didn't get banned!  So, it appears I have two clients running with the same wallet now.

[catia]

The bans are happening from coinbase transactions being submitted to the network.

Presumably this happens when wallet tries to replay transactions not found in the blockchain, perhaps a mined block that got orphaned. But there is code to prevent this, so I'm not exactly sure how it is happening. Will look into it.

Edit: also no bans have happened since 7pm EST on 7/22. So if you are having some problem, ban is not the cause.

@Watuba, your log there indicates that your node banned someone else, not other way around. Would be interesting to see your debug.log. Were you running latest code? Stuff of the 7/22/18 vintage has code to stop bans in an incorrect case.

[watuba]

Ah, thanks for the explanation catia.  That seems right as I ran it twice, and both times it got to the Ban at the same point.  However, I'm not sure if it worked properly after that.  I don't think I could use the daemon.  The second time I ran the client, the output repeated:
Getting size for height : 16816
Update: 16817 16818 16817 16820 1
Update: 16945 16818 16817 16820 0
Getting size for height : 16817
Update: 16818 16819 16818 16820 1
Update: 16946 16819 16818 16820 0
Getting size for height : 16818
Update: 16819 16820 16819 16820 1
Update: 16947 16820 16819 16820 0
Getting size for height : 16819
Update: 16820 16820 16820 16820 1
Update: 16948 16820 16820 16820 0
OS 16821 NS 16821
Accept block header
Ban
Finalize Node
Accept block header
Ban
Finalize Node
Accept block header
Ban
Finalize Node
Accept block header
Ban
Finalize Node
...


I was using the second to latest build, the one right before you said "Updated source, only because I couldn't sync, so this won't do much for you otherwise".

Unfortunately, it seems I can't get the debug.log because my instance got terminated, sorry.  If it happens again, I'll be sure to grab it.

Thanks for the great work!

[catia]

Uh, we're only on block ~4000. Maybe you did not delete data folder since we reset the testnet chain?

[ajeef]

test  c9hSsMbggivBDAZETgKYAEQwH9vE1uBsda





..\roaming\Cryptonite
4000blocks  27M

[mrvegad]

test  c9hSsMbggivBDAZETgKYAEQwH9vE1uBsda





..\roaming\Cryptonite
4000blocks  27M

Incoming!

[watuba]

Uh, we're only on block ~4000. Maybe you did not delete data folder since we reset the testnet chain?

Right, I'm pretty confused.  I think I used a different computer instead.  Sorry to get in the way!

[uvt9]

i downloaded lastest binary for 14.04 Trusty from http://gpile.it/cryptonite/, i got following error:

Code:

terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid
Aborted

What i did:

Code:

sudo add-apt-repository ppa:bitcoin/bitcoin
sudo apt-get update
sudo apt-get install libboost-all-dev libdb4.8-dev libdb4.8++-dev libminiupnpc-dev libqt4-dev libprotobuf-dev protobuf-compiler libgmp-dev

My Ubuntu version arcording to /etc/issue is Ubuntu 14.04 LTS, an Amazon instance.

[catia]

i downloaded lastest binary for 14.04 Trusty from http://gpile.it/cryptonite/, i got following error:

Code:

terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid
Aborted

It may be that you do not have locales setup. In which case:

sudo locale-gen en_US en_US.UTF-8
sudo dpkg-reconfigure locales

May also have to apt-get install locales if it is not installed. We do not have non-en_US locale support due to lack translations. So even if locales are installed, you may have to generate en_US.UTF-8 anyways and then run

LC_ALL="en_US.UTF-8" ./cryptonited -testnet

[watuba]

I cannot get the windows-qt wallet to sync for the life of me.  I tried downloading both of the most recent qt files(16 and 18) and deleting everything in the data directory a bunch of times.  Once it got stuck on the trie.dat file at 50% downloaded.  The other times it got stuck syncing the blocks, always at block 32.

[catia]

New releases up. We reset the chain again. This time we are back to 10 year half life on the rewards, and only 1.85B total coins.

[mrvegad]

H: 1 dT 9318, target 60, 1
Accept block header
H: 1 dT 9318, target 60, 1
OS 1 NS 1
Accepted block 1
Getting size for height : 0
H: 0 dT 9318, target 60, 1
Getting size for height : 0
H: 1 dT 9318, target 60, 1
H: 1 dT 9320, target 60, 1
H: 1 dT 9320, target 60, 1
H: 1 dT 9322, target 60, 1
H: 1 dT 9323, target 60, 1

[uvt9]

It may be that you do not have locales setup. In which case:

sudo locale-gen en_US en_US.UTF-8
sudo dpkg-reconfigure locales

May also have to apt-get install locales if it is not installed. We do not have non-en_US locale support due to lack translations. So even if locales are installed, you may have to generate en_US.UTF-8 anyways and then run

LC_ALL="en_US.UTF-8" ./cryptonited -testnet

Now my binary finally running and syncing (i guess). But could you shed some lights on how to use this command line version ?

I'm running binary with -testnet param but i can't figure how to do other tasks: view my wallet addresses, send coins, list transaction history, mining coin ... ??

[idev]

It may be that you do not have locales setup. In which case:

sudo locale-gen en_US en_US.UTF-8
sudo dpkg-reconfigure locales

May also have to apt-get install locales if it is not installed. We do not have non-en_US locale support due to lack translations. So even if locales are installed, you may have to generate en_US.UTF-8 anyways and then run

LC_ALL="en_US.UTF-8" ./cryptonited -testnet

Now my binary finally running and syncing (i guess). But could you shed some lights on how to use this command line version ?

I'm running binary with -testnet param but i can't figure how to do other tasks: view my wallet addresses, send coins, list transaction history, mining coin ... ??

Just run

Code:

./cryptonited -testnet help

To get a list of the commands you can use to view wallet addresses, send coins, list transaction history, mining coin etc.

[billotronic]

and to see if you are in sync run

Code:

./trusty_amd64_cryptonited_14072502 -testnet getinfo

and it should look like this::

Code:

{
"version" : 10100,
"protocolversion" : 10000,
"walletversion" : 10000,
"balance" : "9964.5720661766ep",
"blocks" : 1971,
"headers" : 1971,
"timeoffset" : 0,
"connections" : 2,
"proxy" : "",
"difficulty" : 6.73014431,
"testnet" : true,
"keypoololdest" : 1406298298,
"keypoolsize" : 101,
"paytxfee" : "0.0000001000ep",
"relayfee" : "0.0000001000ep",
"errors" : "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications"
}

If blocks and headers are showing the same number you are good to go