LanaCoin personalized cryptocurrency
Switch branches/tags
Nothing to show
Clone or download
Pull request Compare This branch is 16 commits ahead, 34 commits behind JohnDolittle:master.
Latest commit 5c53bce Nov 3, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
contrib lanacoin, take 2 May 12, 2016
doc lanacoin, take 2 May 12, 2016
share lanacoin, take 2 May 12, 2016
src Build: C++11 Mar 12, 2017
.gitattributes Build identification strings Apr 10, 2012
.gitignore lanacoin, take 2 May 12, 2016
COPYING lanacoin, take 2 May 12, 2016
INSTALL lanacoin, take 2 May 12, 2016
README directory re-organization (keeps the old build system) Apr 23, 2011
README.md Update README.md Nov 3, 2018
_config.yml Set theme jekyll-theme-cayman Jul 23, 2018
lanacoin-qt.pro lanacoin, take 2 May 12, 2016

README.md

Lanacoin is a Pow/PoS personalized cryptocurrency

  • Ticker: LANA

  • Type: PoW/PoS hybrid

  • PoW algorithm: sha256d

  • PoS block hashing: sha256d

  • Max Coins: 7.506.000.000 (7.5+ bilion)

  • PoW reward: 10000 LANA (no halving)

  • Last PoW block: 750000 (approx 7 years)

  • PoS reward: fixed 1000 LANA + 7% (yearly)

  • PoS reward halving: 525600 (approx 5 years, halving only for fixed reward, 7% stays the same)

  • Minimum PoS age: 7 hours

  • Maximum PoS age: unlimited

  • Block time target: 5 minutes

  • Difficulty retarget: every block

  • Coinbase maturity: 100 blocks

  • Transaction recommended minimum confirmations: 5

  • Minimal TX fee: 100 Lanoshis (0.00000100 LANA)

P2P port: 7506

RPC port: 5706

Testnet P2P port: 17506

Testnet RPC port: 15706

Estimated coins in existence after end of pow 4.068.900.000 (very very rough estimate, depends on how many people will be staking...etc)

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 stable release versions of Lanacoin.

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

Get in touch or stay updated: