Website — Block Explorer — Blog — Forum — Discord — Twitter
The master branch is regularly built and tested, but is not guaranteed to be
completely stable. Tags are created
regularly to indicate new official, stable release versions of Zyrk.
The contribution workflow is described in CONTRIBUTING.md.
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.
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 of the RPC interface, written
in Python, that are run automatically on the build server.
These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py
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.
We try to prompt our users for the basic information We always need for new issues. Please fill out the issue template below and submit an issue on the zyrk-core github page.
- Copyright (c) 2019 Bitcoin Core
- Copyright (c) 2019 Dash Core
- Copyright (c) 2019 Verge Currency
- Copyright (c) 2019 NIX Platform
- Copyright (c) 2019 Particl Project