Skip to content
BeeCoinV2 Bees Back to Flying! X11 POW/POS!
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
contrib
doc
share
src
COPYING
INSTALL
README
README.md
beecoinv2-qt.pro

README.md

BeecoinV2 (BEE2)

BeecoinV2 (Bee) - Second Generation CryptoCurrency of BeeCoin , USES X11 POW/POS.

  • X11 POW/POS
  • 30 second block target
  • Difficulty retargets every block
  • 20,000 BeeCoin Reward every block
  • Total coins will be only 27 Billion
  • The default ports are 66644 (connect) and 44466 (json rpc).
  • Stake Interest 1% per Year, First year - 10%, second year - 5%, third year - 2%
  • Min Age 7 Days
  • Max Age 14 Days
  • 120 Confirmations for Mined Blocks
  • Fast Transaction Confirmations (7 Confirmations)
  • Exact amount of coins in circulation on the BeeCoin Version 1 chain was mined for swapping them at 1:1 ratio for the New coins.
  • 10% Block Tax per block goes to the BeeCoin Foundation - To sustain BeeCoin Projects , Faucets , Future Developments , Games Bounties , Giveaways and Honey Bee Conservation Projects
  • Foundation Address (3644s9FdFwfSn6vNYzhiWm8KGcVFBr1tHX) and PubKey (0265183235726fb1a38df2902d16a1f1f982c6a706698e3b610610ebdb2ab5e508)

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

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

You can’t perform that action at this time.