Skip to content

forktest/ecentfinal

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

eCent integration/staging tree

http://ecent.pw

What is eCent?

eCent is internet’s decentralized currency aimed at low cost transactions, an option for merchants to get the payments faster than any other form of currency. Its here to solve the problems of slow transactions between users

  • Uses Proof of work – Scrypt hashing algorithm, best for GPUS like AMD and nVidia.
  • 25,000 coins per block initially
  • halving every 50 days or 720 blocks.
  • total of 3.7B coins approximately.
  • difficulty re-target every 20 block
  • block generation every 2 minutes
  • fastest transactions faster than Litecoin.

For more details and wallet downloads for windows, linux and mac please visit http://ecent.pw

License

eCent 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 eCent 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 eCent.

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
./ecent-qt_test