maxmustermann/dogecoin
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
25873 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
Wladimir J. van der Laan de4b7f25ac
Merge #20015: doc: Added default signet config for linearize script 
8a4dcda414 doc: Added default signet config for linearize script (gr0kchain)

Pull request description:

  Updated the example-linearize.cfg file to include support for the signet chain network config which is used by the ./linearize-data.py

  Problem:
  Without the signet magic, genesis hash and path config, the linearize-data.py script cannot generate a bootstrap.dat file.

  Example:

  ```
  ./linearize-data.py ./linearize.cfg
  Read 4776 hashes
  Genesis block not found in hashlist
  ```

  Solution:

  Added netmagic, genesis and input example parameters to file. Netmagic in terms of signet is derived from the signet-challenge and not static as with other networks. The provided signet magic is based on the default public signet.

  Resolution

  ```
  ./linearize-hashes.py ./linearize.cfg > ./hashlist.txt
  ./linearize-data.py ./linearize.cfg
  $ ./linearize-data.py ./linearize.cfg
  Read 4776 hashes
  Input file /Users/gr0kchain/.bitcoin/signet/blocks/blk00000.dat
  Output file /Users/gr0kchain/Downloads/bootstrap.dat
  1000 blocks scanned, 1000 blocks written (of 4776, 20.9% complete)
  2000 blocks scanned, 2000 blocks written (of 4776, 41.9% complete)
  3011 blocks scanned, 3000 blocks written (of 4776, 62.8% complete)
  4010 blocks scanned, 4000 blocks written (of 4776, 83.8% complete)
  Done (4776 blocks written)
  ```

ACKs for top commit:
  laanwj:
    Tested ACK 8a4dcda414

Tree-SHA512: ad4d330358cf67e7424fb1d97ca828c28ca2758102e45747f4059c11a8acce801162da024a20cfb892f997fd4c3f4d5af988d1ca67c74efa78bf7d4ed27dd421
2020-09-29 16:38:22 +02:00
.github doc: Remove label from good first issue template 2020-08-24 09:31:24 +02:00
.tx tx: Bump transifex slug to 020x 2020-03-16 10:52:55 +01:00
build-aux/m4 build: AX_PTHREAD serial 27 2020-09-14 16:35:09 +08:00
build_msvc Move Win32 defines to configure.ac to ensure they are globally defined 2020-08-20 17:55:06 +00:00
ci util: Hard code previous release tarball checksums 2020-08-29 11:28:53 +03:00
contrib doc: Added default signet config for linearize script 2020-09-25 14:37:22 +02:00
depends Merge #19868: build: Fix target name 2020-09-23 20:29:52 +02:00
doc Merge #19969: Send RPC bug fix and touch-ups 2020-09-29 15:14:08 +08:00
share doc: Use precise permission flags where possible 2020-07-10 15:37:42 +02:00
src Merge #19984: log: Remove static log message "Initializing chainstate Chainstate [ibd] @ height -1 (null)" 2020-09-29 15:24:43 +02:00
test Merge #20003: net: Exit with error message if -proxy is specified without arguments (instead of continuing without proxy server) 2020-09-29 15:17:28 +02:00
.appveyor.yml Update the vcpkg checkout commit ID in appveyor config. 2020-08-31 08:10:02 +01:00
.cirrus.yml ci: Double tsan CPU and Memory to avoid global timeout 2020-09-05 14:02:55 +02:00
.fuzzbuzz.yml ci: Add fuzzbuzz integration 2020-04-14 16:38:26 +00:00
.gitattributes Separate protocol versioning from clientversion 2014-10-29 00:24:40 -04:00
.gitignore Squashed 'src/secp256k1/' changes from 2ed54da18a..8ab24e8dad 2020-09-11 12:44:08 -07:00
.python-version .python-version: Specify full version 3.5.6 2019-03-02 12:06:26 -05:00
.style.yapf test: .style.yapf: Set column_limit=160 2019-03-04 18:28:13 -05:00
.travis.yml Squashed 'src/secp256k1/' changes from 2ed54da18a..8ab24e8dad 2020-09-11 12:44:08 -07:00
autogen.sh scripted-diff: Bump copyright of files changed in 2019 2019-12-30 10:42:20 +13:00
CODEOWNERS doc: Add comments and additional reviewers to CODEOWNERS file 2020-09-01 11:23:58 -04:00
configure.ac build: add PTHREAD_LIBS to LDFLAGS configure output 2020-09-14 16:12:36 +08:00
CONTRIBUTING.md Replace hidden service with onion service 2020-08-07 14:55:02 +02:00
COPYING doc: Update license year range to 2020 2019-12-26 23:11:21 +01:00
INSTALL.md Update INSTALL landing redirection notice for build instructions. 2016-10-06 12:27:23 +13:00
libbitcoinconsensus.pc.in build: remove libcrypto as internal dependency in libbitcoinconsensus.pc 2019-11-19 15:03:44 +01:00
Makefile.am Squashed 'src/secp256k1/' changes from 2ed54da18a..8ab24e8dad 2020-09-11 12:44:08 -07:00
README.md doc: Mention repo split in the READMEs 2020-06-08 10:06:14 -04:00
SECURITY.md doc: Remove explicit mention of version from SECURITY.md 2019-06-14 06:39:17 -04:00

README.md

Bitcoin Core integration/staging tree

https://bitcoincore.org

What is Bitcoin?

Bitcoin is an experimental 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 usable, binary version of the Bitcoin Core software, see https://bitcoincore.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 (see doc/build-*.md for instructions) and tested, but it is not guaranteed to be completely stable. Tags are created regularly from release branches to indicate new official, stable release versions of Bitcoin Core.

The https://github.com/bitcoin-core/gui repository is used exclusively for the development of the GUI. Its master branch is identical in all monotree repositories. Release branches and tags do not exist, so please do not fork that repository unless it is for development reasons.

The contribution workflow is described in CONTRIBUTING.md and useful hints for developers can be found in doc/developer-notes.md.

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. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.

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.