Neobytes - Reinventing Cryptocurrency https://neobytes.network/
Go to file
Suhas Daftuar 46898e7e94
Version 2 transactions remain non-standard until CSV activates
Before activation, such transactions might not be mined, so don't
allow into the mempool.

- Tests: move get_bip9_status to util.py

- Test relay of version 2 transactions

Github-Pull: #7835
Rebased-From: e4ba9f6b0402cf7a2ad0d74f617c434a26c6e124 5cb1d8a2071d05beb9907a423178895fd8a5c359 da5fdbb3a2778523cce70d635c1aa2b31a693bc6
2016-04-08 14:22:04 +02:00
.tx qt: translation update prior to opening 0.12 translations 2015-11-01 16:11:50 +01:00
build-aux/m4 build: Use fPIC rather than fPIE for qt objects. 2015-11-09 22:50:31 -05:00
contrib build: Remove unnecessary executables from gitian release 2016-04-05 15:45:38 +02:00
depends [depends] builders: No need to set -L and --location for curl 2016-03-01 15:03:54 +01:00
doc Fill in rest of release notes 2016-04-07 14:00:30 +02:00
qa Version 2 transactions remain non-standard until CSV activates 2016-04-08 14:22:04 +02:00
share [doc/log] Fix markdown syntax and line terminate LogPrint 2016-03-11 09:44:17 +01:00
src Version 2 transactions remain non-standard until CSV activates 2016-04-08 14:22:04 +02: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 Workaround Travis-side CI issues 2016-03-01 15:03:44 +01:00
autogen.sh
configure.ac build: Remove unnecessary executables from gitian release 2016-04-05 15:45:38 +02: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 license year range to 2016 2016-01-18 10:31:30 +01:00
INSTALL
libbitcoinconsensus.pc.in libbitcoinconsensus: Add pkg-config support 2014-11-20 21:23:34 +00:00
Makefile.am release: Add security/export checks to gitian and fix current failures 2016-01-27 11:33:33 +01:00
README.md [doc/log] Fix markdown syntax and line terminate LogPrint 2016-03-11 09:44:17 +01:00

Bitcoin Core integration/staging tree

Build Status

https://bitcoincore.org

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. Bitcoin Core is the name of open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Bitcoin Core software, see https://bitcoin.org/en/download, or read the original whitepaper.

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

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

Translators should also subscribe to the mailing list.