mirrors/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2025-02-22 15:04:44 +01:00
Code Issues Projects Releases Wiki Activity
Bitcoin Core integration/staging tree
9938 commits 6 branches 321 tags 5.8 GiB
C++ 56.4%
C 22.6%
Python 17.7%
CMake 1%
Shell 0.8%
Other 1.3%
Find a file
Gavin Andresen 1c06a9b03c
Make CreateNewBlock more robust to coding errors 
If a coding bug of some sort let a bad transaction enter the memory pool,
CreateNewBlock would throw a runtime_error which would cause bitcoind to
crash.

It is better for miners if CreateNewBlock is robust against programming errors,
and this pull request makes it more robust. If an invalid block is created,
all of the transactions that went into the block are removed from the memory pool
and then CreateNewBlock is tried again.
2016-03-01 13:23:56 -05:00
.tx Fix translation path 2016-02-15 11:28:55 +00:00
build-aux/m4 Rename Core to Classic 2016-02-15 13:01:18 +00:00
contrib migrate gitian-debian apt builder from bitcoinxt project 2016-02-28 15:09:06 -08:00
depends Make travis happy 2016-02-15 11:28:55 +00:00
doc Update README.md 2016-02-25 14:20:47 -05:00
qa Make the rpc tests work when src!=builddir 2016-02-29 21:08:35 +00:00
share Rename Core to Classic 2016-02-15 13:01:18 +00:00
src Make CreateNewBlock more robust to coding errors 2016-03-01 13:23:56 -05:00
.gitattributes Separate protocol versioning from clientversion 2014-10-29 00:24:40 -04:00
.gitignore Merge pull request #6813 2015-10-26 09:09:33 +01:00
.travis.yml pass the travis-ci build 2016-02-15 11:28:55 +00:00
autogen.sh Bugfix: Replace bashisms with standard sh to fix build on non-BASH systems 2014-10-03 23:45:26 +00:00
configure.ac Make the rpc tests work when src!=builddir 2016-02-29 21:08:35 +00:00
CONTRIBUTING.md Note that reviewers should mention the commit hash of the commits they reviewed. 2016-01-13 21:25:35 +00:00
COPYING Update COPYING 2016-02-15 11:28:55 +00:00
INSTALL Prettify some /Contrib READMEs 2013-10-21 20:07:31 -04:00
libbitcoinconsensus.pc.in Rename Core to Classic 2016-02-15 13:01:18 +00:00
Makefile.am Rename Core to Classic 2016-02-15 13:01:18 +00:00
README.md Rename Core to Classic 2016-02-15 13:01:18 +00:00

README.md

Bitcoin Classic integration/staging tree

Build Status

https://bitcoinclassic.com

What is Bitcoin?

Bitcoin is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network.

For more information, as well as an immediately useable, binary version of the Bitcoin Classic software, see https://bitcoinclassic.com.

What is Bitcoin Classic?

Bitcoin Classic is currently a one-time increase in total amount of transaction data permitted in a block from 1MB to 2MB, with limits on signature operations and hashing. We will have ports for master and 0.11.2, so that miners and businesses can upgrade to 2 MB blocks from any recent bitcoin software version they run.

Read the block size increase BIP for more information.

In the future Bitcoin Classic will continue to release updates that are in line with Satoshi’s whitepaper & vision, and are agreed upon by the community.

License

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

The contribution workflow is described in CONTRIBUTING.md.

Complicated or controversial changes should be discussed within the communtiy before working on a patch set.

Community

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

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run with: qa/pull-tester/rpc-tests.py

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

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.

Translations

Changes to translations as well as new translations can be submitted to Bitcoin Classic's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.