Halving at 210,000
Blocks Initial Coins per Block = 100 ECC
Target Spacing = 3 Minutes
Target Timespan = 100 Hours
Coinbase Maturity = 99 Blocks
Premine = 0 %
Max coinbase = 42000000 + 0 Pre-Mine = 42000000 Coins
P2P Port = 11075
RPC Port = 21075
apt-get update
apt-get upgrade
apt-get install build-essential
apt-get install libssl-dev
apt-get update
apt-get install libdb4.8++
apt-get install libboost-all-dev
apt-get install libdb++-dev libminiupnpc-dev
apt-get install git-core
apt-get install ntp
cd ~
mkdir eCurrency
cd /usr/local/
git clone https://github.com/eCurrency-ECC/eCurrency-v1.0.git
cd eCurrency-v1.0
cd /src
make -f makefile.unix USE_UPNP=
strip ecurrencyd
cp ecurrencyd ~/eCurrency/ecurrencyd
(If it fails to compile, be sure that the entire folder is chmod 777 recursively to all folders and directories.)
./ecurrencyd
./ecurrencyd getinfo
./ecurrencyd help
./ecurrencyd getaccountaddresses ""
Copyright (c) 2009-2013 Bitcoin Developers
Bitcoin is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin is also the name of the open source software which enables the use of this currency.
For more information, as well as an immediately useable, binary version of the Bitcoin client software, see http://www.bitcoin.org.
Bitcoin is released under the terms of the MIT license. See COPYING for more
information or see http://opensource.org/licenses/MIT.
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 Bitcoin 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.md) 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 Bitcoin.
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.
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
./bitcoin-qt_test
Every pull request is built for both Windows and Linux on a dedicated server, and unit and sanity tests are automatically run. The binaries produced may be used for manual QA testing — a link to them will appear in a comment on the pull request posted by BitcoinPullTester. See https://github.com/TheBlueMatt/test-scripts for the build/test scripts.
Large changes should have a test plan, and should be tested by somebody other than the developer who wrote the code.
See https://github.com/bitcoin/QA/ for how to create a test plan.