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 APIHere 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
Show Posts
