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

[bitfreak!]

WARNING: this is a test release, it runs in testnet mode, do not place any value on the coins because you will lose them!

It has been over a year since I first proposed the mini-blockchain scheme, and a few months ago I finally found some developers capable of building it. In a very small amount of time an incredible amount of work has been done. We started with the Bitcoin code base and so far we have altered tens of thousands of lines of code, and lots still needs to be done. But at last we have reached the point where we can release some binaries for testing to help us weed out some of the bugs and figure out what needs to be done next. We need all the testers we can get and we appreciate your help during this testing phase.

First it should be mentioned that the binaries will only work on 64bit systems right now, we plan to add 32bit support in the future and we also have a binary for Windows systems which will be released at a future point for testing (the Windows binaries have now been released, see the link below for a list of available binaries). We encourage you to test out all the features and try to break the system, if you do find any bugs could you please report them in this thread along with as much detail about the problem as you're able to provide (we may also request log files in some cases).

The binary can be downloaded from here:
http://gpile.it/cryptonite/

The dependencies are the same as Bitcoin with one extra requirement: libgmp-dev

You must start cryptonited in testnet mode using the following command:

./cryptonited -testnet

All API commands should include -testnet flag or they wont work.

See the wiki for more info: Cryptonite API

Here is a message from our lead developer which contains more details about this release:

Cryptonite is significantly different from bitcoin and it's
derivatives. Large swaths of code have been changed and entire
algorithms rethought. In a way this puts us kind of back in the stone
age. Much like the early days of bitcoin, the security and reliability
of Cryptonite is questionable regardless of it's theoretical
underpinnings. As coins are now generally expected to work without
problems at the time of launch, we must find a way to test this
codebase to the requisite level. We propose vast testing on the
testnet, and that's where you come in.

Keep in mind that while we encourage you to make use of the testnet
network and all it's capabilities. It is possible, and in fact likely
that we will completely reset the blockchain periodically as changes
become necessary. Slated changes to the client will make it difficult
to maintain wallets across certain versions as well. Cryptonite is not
complete. While it is currently believed that no changes will need to
be made to the blockchain, this is far from certain as huge sections
of code have not been implemented. Bugs are also likely, some may
cause crashes, others may force us to reset the chain. No effort will
be made to maintain the testnet chain via forks.

After all that down talk, you might wonder why we need testers at this
point. The answer is that much code has actually been written and many
things have changed. The program in it's current state, and the
program with all future changes should remain functionally identical
from the users perspective, plus a few minor features. Testing will
give an opportunity for users and service providers to interact with
the new model and provide testing and feedback. As an example of the
kind of changes in thinking, Cryptonite does not support scripts, and
does not require change when sending transactions. Cryptonite also
does not necessarily know the origin of coins. Common utilities such a
blockchain explorer may be practically impossible. Changes like these
could have a profound impact on the way people use the program.

The current binary release is made available only for x86-64 linux.
The binary should run on all debian derivatives such as ubuntu/mint
etc.

~Catia

[1714111289]

1714111289

[1714111289]

1714111289

[1714111289]

1714111289

[TwinWinNerD]

Nice concept. Is there another announcement thread on this forum?

[pork pie]

Can you give us a rough idea when the windows alpha will be released?

[bitfreak!]

Nice concept. Is there another announcement thread on this forum?

No this is the only thread besides the logo bounty thread (which is already closed). We will make a proper announcement thread when we release the finished binary along with the source, but for now this is the only thread we need.

Can you give us a rough idea when the windows alpha will be released?

Well if we don't get enough linux testers we may release a Windows binary within a few days, but otherwise we want to wait until we've eliminated as many bugs as possible during this testing phase and once that is done we probably want to implement some rather large changes on top of that. So probably at least a few weeks before Windows users will get a turn to try it out.

[pork pie]

What type of design and testing methodology are you using?

Is it somewhere between classic waterfall and extreme programming?

[catia]

What type of testing methodology are you using?

Is it somewhere between classic waterfall and extreme programming?

I don't ascribe to any particular methodology. In this project we have quite clear requirements for what the final product should do, and eventually it was figured out how exactly it should do it. I try to move towards the path of least resistance. Changing code in an order that brings about the functionality while still allowing testing. This is much like parts of extreme programming. In many ways the coin is done. Everything is calculated using the new algorithms and old portions of the block chain are not used/required. Legacy database code prevents us from actually deleting this superfluous information so this is being overhauled. But since this data is not used, deleting it does not have widespread effects on the code, nor should it have any effect on the user interface. This is why I think now is a good time to start wide spread testing. Also it is difficult to trim the chain when there is no chain to trim. Getting some people mining the coin and generating noise will make my life a lot easier.

[mrvegad]

This is what I get:


xxx@localhost:~/coin$ ./cryptonited -testnet
./cryptonited: /usr/lib64/libcrypto.so.1.0.0: no version information available (required by ./cryptonited)
./cryptonited: /usr/lib64/libssl.so.1.0.0: no version information available (required by ./cryptonited)
Error: To use the "-server" option, you must set a rpcpassword in the configuration file:
/home/xxx/.cryptonite/cryptonite.conf
It is recommended you use the following random password:
rpcuser=cryptoniterpc
rpcpassword=B7J6ouBvQksGScUcEKoeoMyCuVRR1UV9pZKe8xExiQwK
(you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions.
It is also recommended to set alertnotify so you are notified of problems;
for example: alertnotify=echo %s | mail -s "Cryptonite Alert" admin@foo.com

Then it goes back to command prompt. I am using pclinuxos 64 lxde edition.

[catia]

@mrvegad

./cryptonited: /usr/lib64/libcrypto.so.1.0.0: no version information available (required by ./cryptonited)
./cryptonited: /usr/lib64/libssl.so.1.0.0: no version information available (required by ./cryptonited)

are just warnings because your libsll is older than 1.0.0. Perhaps see if there is a way to upgrade these on your distro. It may work without upgrading but you will receive those warnings whenever starting the client or even executing an rpc command.

The rest of it you need to do. Create the file /home/bl/.cryptonite/cryptonite.conf and put the user and password lines in it. Just like bitcoind.

[mrvegad]

I have lib64openssl1.0.1 installed or do i need something else?

I have made the file as requested.

[bitfreak!]

I have lib64openssl1.0.1 installed or do i need something else?

It appears that you might have a version of OpenSSL older than 1.0.1e so the heartbleed fix isn't applied to your version. That will work, but as mentioned you will continue to get those warnings.

[mrvegad]

i have openssl 1.0.1g

I can run the bitcoin bitcoind fine with no errors. I cannot get yours to run.

[bitfreak!]

i have openssl 1.0.1g

I can run the bitcoin bitcoind fine with no errors. I cannot get yours to run.

Ok well that's a bit weird. We aren't sure why it's giving you warnings but it should work.

EDIT: removed irrelevant text.

[mrvegad]

it seems to be working now, here is my address muXpk6wmutEiKYJf7hH6gtr26gQvQUgR3u

[bitfreak!]

it seems to be working now, here is my address muXpk6wmutEiKYJf7hH6gtr26gQvQUgR3u

Cool. I just sent you 100 coins, you should get them when the next block is solved.

[mrvegad]

received them but how do i send them back? i am not to familiar with bitcoin api calls

[bitfreak!]

received them but how do i send them back? i am not to familiar with bitcoin api calls

There is an example of how to send coins in the opening post:

./cryptonited -testnet sendtoaddress mvqH4czVQg2HdGpkV7PWVZJpRXVwLnMXpN "0.01000000ep"

Just replace the address and the amount with what ever you want. The address in that example is mine.

You can also view a full list of API commands on the following page:
https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list

[AlexGR]

Interesting...

[mrvegad]

i wasn't sure if that was the right address to use, i sent 100 back

[bitfreak!]

i wasn't sure if that was the right address to use, i sent 100 back

Ok, if you like I can send you 1000 coins to mess around with or you can try mining your own coins using the following command:

./cryptonited -testnet setgenerate true 1

You replace the 1 with the number of cores you wish to use for mining.

And you can stop mining with this command:

./cryptonited -testnet setgenerate false

[mrvegad]

i still have 999 coins and i started to mine so I will see how it goes, TY for your help