KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#developer-tools #codex #typescript #ai-agents #ai-agent #cli #claude-code #open-source #deepseek-harness #dsh-plugin #python #mcp

axe

★ 270 Open GitHub ↗

decentralized cryptocurrency

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

`M`: [![Build Status](https://gitlab.com/axerunners/axe/badges/master/pipeline.svg)](https://gitlab.com/axerunners/axe/pipelines)

`D`: [![Build Status](https://gitlab.com/axerunners/axe/badges/development/pipeline.svg)](https://gitlab.com/axerunners/axe/pipelines)

`t`: [![Version tag](https://img.shields.io/github/tag/axerunners/axe.svg)](https://github.com/axerunners/axe/tags)

What is Axe?
-------------

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

License
-------

Axe Core is released under the terms of the MIT license. See [COPYING](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](https://github.com/axerunners/axe/tags) are created to indicate new official,
stable release versions of Axe Core.

The contribution workflow is described in [CONTRIBUTING.md](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](src/test/README.md) 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](/src/test/README.md).

There are also [regression and integration tests](/test), written
in Python, that are run automatically on the build server.
These tests can be run (if the [test dependencies](/test) 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.

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

axe

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README