SikkieNL
6f99c9375a
All checks were successful
Gitea Actions Demo / Explore-Gitea-Actions (push) Successful in 16s
|
||
|---|---|---|
| .github | ||
| .tx | ||
| build-aux/m4 | ||
| ci | ||
| contrib | ||
| depends | ||
| doc | ||
| docker | ||
| share | ||
| src | ||
| test | ||
| .gitattributes | ||
| .gitignore | ||
| autogen.sh | ||
| CMakeLists.txt | ||
| configure.ac | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| gitlab-ci.yml | ||
| INSTALL.md | ||
| Jenkinsfile | ||
| Jenkinsfile.gitian | ||
| libneobytesconsensus.pc.in | ||
| Makefile.am | ||
| README.md | ||
Neobytes Core integration/staging tree
Further information about Neobytes Core is available in doc folder.
What is Neobytes?
Neobytes is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Neobytes uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Neobytes 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 Neobytes Core software, see https://www.neobytes.network.
Neobytes FAQ
Launch Date: June 1, 2021
Blockchain Type: Decentralized
Ticker Symbol: NBY
Genesis Block Hash: "Neobytes Genesis born on June 1, 2021"
Mining Algorithm: NeoScrypt
License
Neobytes 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 Neobytes 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, 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
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.