Skip to content

Latest commit

 

History

History
75 lines (54 loc) · 2.82 KB

README.md

File metadata and controls

75 lines (54 loc) · 2.82 KB
Raw

BitcoinSpread integration/staging tree

https://bitcoinspread.org/

Copyright (c)

  • 2009-2014, The developers;
  • 2017 - �‡, The BitcoinSpread developers

What is BitcoinSpread?

BitcoinSpread is the official fork of SpreadCoin (SPR). We're continuing where the previous developers have left, and we'll forge our own roadmap along.

  • Algorithm: SpreadX11
  • Block generation: 1 minute
  • Difficulty retargets: every block based on last 360 blocks
  • Reward starts at approx. 6.66 coins per block
  • Block reward is smoothly halved every 4 years
  • Total supply: 20 mln coins
  • No year 2106 problem

Proposed feature:

  • Masternodes
  • Move to Proof-Of-Stake (POS)
  • Segwit

License

Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

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 Bitcoin Core.

The contribution workflow is described in CONTRIBUTING.md.

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer IRC can be found on Freenode at #bitcoin-core-dev.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, 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 can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.