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
963 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
Luke Dashjr a880b29cab Bugfix: fForRelay should be false when deciding required fee to include in blocks 
During the rushed transition from 0.01 BTC to 0.0005 BTC fees, we took the
approach of dropping the relay and block-inclusion fee to 0.0005 BTC
immediately, and only delayed adjusting the sending fee for the next release.
Afterward, the relay fee was lowered to 0.0001 BTC to avoid having the same
problem in the future. However, the block inclusion code was left setting
fForRelay to true! This fixes that, so the lower 0.0001 BTC allowance is (as
intended) only permitted for real relaying.
2011-12-14 01:06:21 -05:00
contrib Restructure gitian files and add download config files. 2011-09-22 16:52:49 -04:00
doc wxWidgets needs to be at least version 2.9.1 because wallet crypto uses ToStdString() which is not in 2.9.0 2011-09-08 20:50:00 -04:00
locale Updated dutch translation 2011-09-22 19:22:17 +02:00
share Update bitcoin icon to make nsis setup exe deterministic. 2011-09-14 10:59:54 -04:00
src Bugfix: fForRelay should be false when deciding required fee to include in blocks 2011-12-14 01:06:21 -05:00
.gitignore ignore stuff 2011-09-06 13:53:04 -04:00
COPYING directory re-organization (keeps the old build system) 2011-04-23 12:10:25 +02:00
README directory re-organization (keeps the old build system) 2011-04-23 12:10:25 +02:00
README.md Fix QA email address 2011-09-22 16:50:32 -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.