Skip to content
Official source code of Benode Сore
C++ C Python M4 Makefile HTML Other
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
beenode-docs upload new Feb 19, 2020
build-aux/m4
ci upload new Feb 19, 2020
contrib
depends upload new Feb 19, 2020
doc
docker
qa
share
src
.gitattributes fix Feb 18, 2020
.travis.yml fix Feb 18, 2020
CMakeLists.txt upload new Feb 19, 2020
CONTRIBUTING.md upload new Feb 19, 2020
COPYING
INSTALL.md
Jenkinsfile
Jenkinsfile.gitian upload new Feb 19, 2020
Makefile.am upload new Feb 19, 2020
README.md
autogen.sh
configure.ac
libbeenodeconsensus.pc.in

README.md

Beenode Core staging tree 0.9.1

https://www.beenode.org

What is Beenode?

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

What is CryptoShock?

Official Beenode Support and Development Project. See https://cryptoshock.com/

License

Beenode 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 Beenode 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. Further details on running and extending unit tests can be found in /src/test/README.md.

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

Translations

Changes to translations as well as new translations can be submitted to Beenode Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translators should also follow the forum.

You can’t perform that action at this time.