crypto-official/crypto

The official crypto release

Crypto integration/staging tree

http://http://tailflick.wix.com/official-crypto

Copyright (c) 2009-2013 Bitcoin Developers Copyright (c) 2011-2013 Litecoin Developers Copyright (c) 2014 Vertcoin Developers Copyright (c) 2014-2015 Darkcoin Developers Copyright (c) 2015 Crypto Developers

What is Crypto?

Crypto is a lite version of Bitcoin using Lyra2RE as a proof-of-work algorithm.

• 30 second block targets
• The subsidy never halves, but every 10 days the subsidy is reduced with 0.00547945 CTO.
• ~65789100 total coins
• 5 coins per block initially (changes every 10 days for 25 years)
• Every block to retarget difficulty with Dark Gravity wave v3 algorithm

For more information, as well as an immediately useable, binary version of the Crypto client sofware, see http://tailflick.wix.com/official-crypto

License

Crypto is released under the terms of the MIT license. See COPYING for more information or see http://opensource.org/licenses/MIT.

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the Crypto development team members simply pulls it.

If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see doc/coding.txt) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Crypto.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test. Please be patient and help out, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code.

Unit tests for the core code are in src/test/. To compile and run them:

cd src; make -f makefile.unix test

Unit tests for the GUI code are in src/qt/test/. To compile and run them:

qmake BITCOIN_QT_TEST=1 -o Makefile.test bitcoin-qt.pro
make -f Makefile.test
./crypto-qt_test

crypto's Issues

Not compilable under linux debian 7 x64

Followed instructions for secp256. secp libs compiled fine and are in place. Other secp256 coins compiling fine on same server. Tried also export LD_RUN_PATH=/usr/local/lib

errors coming at the end of compilation (usually message with libmemenv.a is the last message before deamon created).

..../sources/crypto/src/leveldb/libmemenv.a
obj/wallet.o: In function init_singleton::~init_singleton()': /sources/crypto/src/stealth.h:150: undefined reference to secp256k1_stop'
obj/stealth.o: In function init_singleton::init()': /sources/crypto/src/stealth.h:156: undefined reference to secp256k1_start'
/sources/crypto/src/stealth.h:156: undefined reference to secp256k1_start' /sources/crypto/src/stealth.h:156: undefined reference to secp256k1_start'
/sources/crypto/src/stealth.h:156: undefined reference to `secp256k1_start'
collect2: error: ld returned 1 exit status
makefile.unix:217: recipe for target 'cryptod' failed
make: *** [cryptod] Error 1

error in rpcrawtransaction.cpp...

all time give me this error:

$ ./cryptod

./cryptod: error while loading shared libraries: libsecp256k1.so.0: cannot open shared object file: No such file or directory

i try in 2 linux 16.0.4 lts server, alrely installed libsecp256k1...