Dash - Reinventing Cryptocurrency
Go to file
Oleg Girko bcf5455bfd Backport Bitcoin PR#8822: net: Consistent checksum handling (#1565)
* net: Consistent checksum handling

In principle, the checksums of P2P packets are simply 4-byte blobs which
are the first four bytes of SHA256(SHA256(payload)).

Currently they are handled as little-endian 32-bit integers half of the
time, as blobs the other half, sometimes copying the one to the other,
resulting in somewhat confused code.

This PR changes the handling to be consistent both at packet creation
and receiving, making it (I think) easier to understand.

* net: Hardcode protocol sizes and use fixed-size types

The P2P network uses a fixed protocol, these sizes shouldn't change
based on what happens to be the architecture.
2017-08-08 20:57:36 +03:00
.tx
build-aux/m4 Force to use C++11 mode for compilation (#1463) 2017-05-05 14:27:27 +03:00
contrib typo in date (#1241) 2017-01-01 15:45:51 +04:00
dash-docs Documentation: Add spork message / details to protocol-documentation.md (#1493) 2017-06-26 16:56:52 +03:00
depends Boost 1.63.0 2017-05-12 00:58:36 +03:00
doc Backport Bitcoin PR#7349: Build against system UniValue when available (#1503) 2017-07-04 06:20:19 +03:00
qa Backport Bitcoin PR#7917: Optimize reindex (#1515) 2017-07-10 17:41:14 +03:00
share Fix windows installer script, should handle dash: uri correctly now (#1550) 2017-07-25 13:58:08 +03:00
src Backport Bitcoin PR#8822: net: Consistent checksum handling (#1565) 2017-08-08 20:57:36 +03:00
.gitattributes
.gitignore Rename bitcoinconsensus library to dashconsensus. (#1432) 2017-04-15 09:29:09 +02:00
.travis.yml workaround for travis (#1526) 2017-07-14 17:19:07 +03:00
autogen.sh
configure.ac Backport Bitcoin PR#7349: Build against system UniValue when available (#1503) 2017-07-04 06:20:19 +03:00
CONTRIBUTING.md Doc: fix broken formatting in markdown #headers (#1462) 2017-05-05 14:28:08 +03:00
COPYING
INSTALL Added clarifications in INSTALL readme for newcomers (#1481) 2017-05-31 06:50:03 +03:00
libdashconsensus.pc.in Rename bitcoinconsensus library to dashconsensus. (#1432) 2017-04-15 09:29:09 +02:00
Makefile.am Rename bitcoinconsensus library to dashconsensus. (#1432) 2017-04-15 09:29:09 +02:00
README.md Fix: Broken download link (#1335) 2017-02-15 19:18:43 +04:00

Dash Core staging tree 0.12.1

master: Build Status v0.12.0.x: Build Status v0.12.1.x: Build Status

https://www.dash.org

What is Dash?

Dash is an experimental new digital currency that enables anonymous, instant payments to anyone, anywhere in the world. Dash uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Dash Core is the name of the open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Dash Core software, see https://www.dash.org/get-dash/.

License

Dash 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 meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of Dash Core.

The contribution workflow is described in CONTRIBUTING.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

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

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

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 Dash 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 follow the forum.