P2P Digital Currency
TypeScript C++ C Python Prolog Objective-C
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
data
doc
share
src
COPYING
INSTALL
Info.plist
README.md
eaglecoin-qt.pro

README.md

EagleCoin (EGC) - a lite version of Litecoin using scrypt as a proof of work scheme.

  • 3 minute block targets
  • subsidy halves in 4380k blocks (~25 years)
  • ~4380 million total coins
  • 500 coins per block
  • 1440 blocks to retarget difficulty (~3 days)
  • 56883 RPC port
  • 56884 P2P port
  • 51883 Testnet port

Download

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

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