maxmustermann/dogecoin
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
1328 commits 12 branches 161 tags 1.2 GiB
C++ 65.7%
Python 15%
C 12.5%
M4 2.7%
Makefile 1.5%
Other 2.5%
Go to file
Pieter Wuille 3a570dc80a Use key recovery for message signatures 
Instead of encoding the public key inside the signature string, use
key recovery to do verification. This allows 88-character base64-encoded
signature strings instead of 188-character ones.
2011-09-27 19:48:22 +02:00
contrib Bump version to 0.4.1 2011-09-26 09:16:56 -04:00
doc Update build instructions for the new, no-wxwidgets world 2011-09-26 11:40:43 -04:00
locale Updated dutch translation 2011-09-22 19:22:17 +02:00
scripts/qt move qt-specific scripts to qt-specific directory in scripts/ 2011-09-18 12:44:32 +02:00
share Remove wxWidgets 2011-09-26 10:04:04 -04:00
src Use key recovery for message signatures 2011-09-27 19:48:22 +02:00
.gitignore Output build temp files in build/ instead of current directory. 2011-09-26 13:14:34 -04:00
bitcoin-qt.pro Output build temp files in build/ instead of current directory. 2011-09-26 13:14:34 -04:00
COPYING directory re-organization (keeps the old build system) 2011-04-23 12:10:25 +02: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 Merge pull request #521 from laanwj/qt 2011-09-26 06:05:11 -07: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.