neobytes-project/neobytes
neobytes-project/neobytes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Neobytes - Reinventing Cryptocurrency https://neobytes.network/
3,216 Commits 3 Branches 0 Tags 185 MiB
C++ 62.3%
C 19.5%
Python 8.4%
Assembly 5%
M4 1.8%
Other 2.8%
5382bcf8cd
Go to file
Pieter Wuille 5382bcf8cd Multiple blocks per file 
Change the block storage layer again, this time with multiple files
per block, but tracked by txindex.dat database entries. The file
format is exactly the same as the earlier blk00001.dat, but with
smaller files (128 MiB for now).

The database entries track how many bytes each block file already
uses, how many blocks are in it, which range of heights is present
and which range of dates.
2012-10-20 23:08:57 +02:00
contrib Merge branch '2012_09_base58tests' of github.com:laanwj/bitcoin 2012-10-01 11:22:38 -04:00
doc Revert "Merge pull request #1931 from laanwj/2012_10_newicons" 2012-10-14 20:49:06 +02:00
share Revert "Merge pull request #1931 from laanwj/2012_10_newicons" 2012-10-14 20:49:06 +02:00
src Multiple blocks per file 2012-10-20 23:08:57 +02:00
.gitattributes Build identification strings 2012-04-10 18:16:53 +02:00
.gitignore Import LevelDB 1.5, it will be used for the transaction database. 2012-10-20 23:08:56 +02:00
bitcoin-qt.pro LevelDB glue 2012-10-20 23:08:56 +02:00
COPYING Update all copyrights to 2012 2012-02-07 11:28:30 -05:00
INSTALL Update master 2012-06-21 09:36:20 +08: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.