No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Latest commit ed33eae Nov 20, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx Initial Commit Aug 9, 2018
build-aux/m4 Initial Commit Aug 9, 2018
contrib 2018/08/24 UI Source Upload Aug 24, 2018
depends fix static build error Nov 20, 2018
doc fixed option restore Aug 24, 2018
qa modify prefix dash to soom Aug 14, 2018
share Initial Commit Aug 9, 2018
soom-docs chg version Aug 9, 2018
src mnemonic fix Aug 26, 2018
.travis.yml Initial Commit Aug 9, 2018
CONTRIBUTING.md Initial Commit Aug 9, 2018
COPYING Initial Commit Aug 9, 2018
INSTALL Initial Commit Aug 9, 2018
Makefile.am Initial Commit Aug 9, 2018
README.md chg version Aug 9, 2018
autogen.sh Initial Commit Aug 9, 2018
configure.ac chg version Aug 9, 2018
libsoomconsensus.pc.in Initial Commit Aug 9, 2018

README.md

Soom Core staging tree 1.0.1

http://foutrhblockchain.org

What is Soom?

Soom is an experimental new digital currency that enables anonymous, instant payments to anyone, anywhere in the world. Soom uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Soom 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 Soom Core software, see http://foutrhblockchain.org/.

License

Soom 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 Soom 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.