No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Latest commit 4b0e1fc Sep 27, 2018
Permalink
Failed to load latest commit information.
.github Launch Commit Sep 26, 2018
build-aux/m4 Launch Commit Sep 26, 2018
contrib Fix macOS Permission Sep 26, 2018
depends Fix Permissions Sep 26, 2018
doc Update TravisCI Sep 26, 2018
injex-docs Launch Commit Sep 26, 2018
qa Launch Commit Sep 26, 2018
share Fix Permissions Sep 26, 2018
src Fix Permissions Sep 26, 2018
.gitattributes Launch Commit Sep 26, 2018
.gitignore Fix Permissions Sep 26, 2018
.travis.yml Update TravisCI Sep 26, 2018
CONTRIBUTING.md Launch Commit Sep 26, 2018
COPYING Launch Commit Sep 26, 2018
INSTALL Update TravisCI Sep 26, 2018
Makefile.am Launch Commit Sep 26, 2018
README.md Update TravisCI Sep 26, 2018
autogen.sh Fix Permissions Sep 26, 2018
configure.ac Update TravisCI Sep 26, 2018
libinjexconsensus.pc.in Launch Commit Sep 26, 2018

README.md

GitHub Logo

Injex Core v0.12.2.4 (INJ)

master: Build Status

https://injex.io

What is Injex?

Specification Value
Total Injex 32,000,000
Block Size 2MB
Block Time 60s
PoW Reward 10 INJ
Masternode Requirement 5,000 INJ
Masternode Reward 25% upto 50%
Port 18499
RPC Port 18500
Masternode Port 18499

License

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