LBRYCommunity/lbrycrd
1
0
Fork 0
Code Issues 29 Pull requests 1 Projects Releases 32 Packages Wiki Activity
The blockchain that provides the digital content namespace for the LBRY protocol
1857 commits 22 branches 42 tags 99 MiB
C++ 66.5%
Python 15.1%
C 12.7%
M4 2.1%
Makefile 1.2%
Other 2.3%
Find a file
Pieter Wuille a206b0ea12 Do not allow overwriting unspent transactions (BIP 30) 
Introduce the following network rule:
 * a block is not valid if it contains a transaction whose hash
   already exists in the block chain, unless all that transaction's
   outputs were already spent before said block.

Warning: this is effectively a network rule change, with potential
risk for forking the block chain. Leaving this unfixed carries the
same risk however, for attackers that can cause a reorganisation
in part of the network.

Thanks to Russell O'Connor and Ben Reeves.
2012-03-03 18:26:36 +01:00
contrib Make deps build deterministic and upgrade to libpng 1.5.9. 2012-02-22 22:09:06 -05:00
doc Updated Mac build process 2012-02-29 21:04:56 -05:00
scripts/qt move qt-specific scripts to qt-specific directory in scripts/ 2011-09-18 12:44:32 +02:00
share Increase client version to 0.6 2012-02-07 11:22:09 -05:00
src Do not allow overwriting unspent transactions (BIP 30) 2012-03-03 18:26:36 +01:00
.gitignore Output build temp files in build/ instead of current directory. 2011-09-26 13:14:34 -04:00
bitcoin-qt.pro Add mruset and use it for setInventoryKnown 2012-02-27 21:04:32 +01:00
COPYING Update all copyrights to 2012 2012-02-07 11:28:30 -05:00
INSTALL Update build instructions for the new, no-wxwidgets world 2011-09-26 11:40:43 -04:00
README directory re-organization (keeps the old build system) 2011-04-23 12:10:25 +02:00
README.md Updated readme file with timers. 2011-09-26 22:22:19 -04:00

README.md

Bitcoin integration/staging tree

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the bitcoin development team members simply pulls it.

If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list: http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development

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 Bitcoin. If you would like to help test the Bitcoin core, please contact QA@BitcoinTesting.org.

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

Requests to reopen closed pull requests and/or issues can be submitted to QA@BitcoinTesting.org.