Skip to content
Genix Core Wallet
Branch: master
Clone or download
farsider350 Merge pull request #4 from Twinky-kms/patch-1
Fix BerkeleyDB4.8 install lines.
Latest commit e9ed7f3 May 3, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
autom4te.cache Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
build-aux Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
contrib Update nodes_main.txt Apr 29, 2019
depends Fix for Depends Build issues on OSX Apr 29, 2019
doc Fix BerkeleyDB4.8 install lines. May 2, 2019
genix-docs Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
qa Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
share Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
src Fix payment bug Apr 5, 2019
.gitattributes Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
.gitignore Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
CONTRIBUTING.md Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
COPYING Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
INSTALL Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
LICENSE Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
Makefile.am Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
Makefile.in Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
README.md Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
Thumbs.db Depends Source Mar 30, 2019
aclocal.m4 Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
autogen.sh Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
configure Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
configure.ac Update configure.ac Apr 5, 2019
deploy_rsa.enc Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
libgenixconsensus.pc.in Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
orchid222.png Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
radio_checked.png Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019
static.png Initial commit of source code ready for new Blockchain release. (#1) Mar 29, 2019

README.md

Genix Core

What is Genix?

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

License

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

You can’t perform that action at this time.