Verium is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Verium uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Verium is the name of open source software which enables the use of this currency.
For more information, as well as an immediately useable, binary version of the Verium software, see https://www.vericonomy.com.
Each release come along with a Release Notes.
For previous release you can find them in the Release-Notes Directory
All the documentation can be found in the Doc Directory.
You will find information such as:
- How to build Verium Vault
- Release Notes
- Development Process
- ...
Verium is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.
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 Verium.
Current official Verium release is on branch 1.3.2.
The contribution workflow is described in CONTRIBUTING.md.
The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.
Developer IRC can be found on Freenode at #verium-core-dev.
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, 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 OS X, and that unit/sanity tests are run automatically.
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.