Emerald Crypto scrypt-based cryptocurrency
C++ Python C Other QMake NSIS Other
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
contrib
doc
share
src
.gitattributes
.gitignore
COPYING
INSTALL
Info.plist
README.md
emerald-qt.pro

README.md

Download windows wallet http://www.emeraldcrypto.org

Emerald - a fork of Litecoin. Like Litecoin it uses scrypt as a proof of work scheme.

- Total coins will be 31,499,000.
- 20 seconds block target
- Difficulty retargets every hour* (see hardfork info below)
- 5 emerald per block, halves every 2 block years (3,110,400 blocks)
- transaction 3 confirmations, which average 1 min.
- Start 0 emeralds for the first 400 blocks (except 1st block which is used for bounty etc), then 300 blocks each for 1, 2, 3 and 4 emeralds. Starting block 1601 will be 5 emeralds per block. This is to ensure fair start.
- The default ports are 12127(connect) and 12128(json rpc).

===================

Hardfork at block 1600000 to implement Dark Gravity Wave 3. Difficulty will retarget every block instead of 180.

New checkpoint added.

===================

Future changes include updating to Bitcoin 9.x core for improved security and improved client functionality.

Development process

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

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 they don't match the project's coding conventions (see coding.txt) or are controversial.

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

Feature branches are created when there are major new features being worked on by several people.

From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure. The pull will be closed 15 days after the warning if action is not taken by the author. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'.

Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled 'stale'.