neobytes-project/neobytes
neobytes-project/neobytes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update readme

Browse Source
This commit is contained in:
SikkieNL 2024-12-15 22:44:06 +01:00
parent d651890bdc
commit 9e6fef6df0
1 changed files with 32 additions and 41 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

73
README.md
View File

@ -1,36 +1,47 @@
Dash Core staging tree 0.15
===========================
Neobytes Core integration/staging tree
======================================
`master:` [![Build Status](https://travis-ci.org/dashpay/dash.svg?branch=master)](https://travis-ci.org/dashpay/dash) `develop:` [![Build Status](https://travis-ci.org/dashpay/dash.svg?branch=develop)](https://travis-ci.org/dashpay/dash/branches)
https://www.neobytes.network
https://www.dash.org
Further information about Neobytes Core is available in [doc folder](/doc).
What is Neobytes?
-----------------
What is Dash?
-------------
Dash is an experimental digital currency that enables instant, private
payments to anyone, anywhere in the world. Dash uses peer-to-peer technology
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. Dash Core is the name of the open
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 Dash Core software, see https://www.dash.org/get-dash/.
the Neobytes Core software, see [https://www.neobytes.network](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
-------
Dash Core is released under the terms of the MIT license. See [COPYING](COPYING) for more
information or see https://opensource.org/licenses/MIT.
Neobytes 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/dashpay/dash/tags) are created to indicate new official,
stable release versions of Dash Core.
[Tags](https://github.com/neobytes-project/neobytes/tags) are created to indicate new official,
stable release versions of Neobytes Core.
The contribution workflow is described in [CONTRIBUTING.md](CONTRIBUTING.md).
@ -44,34 +55,14 @@ 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).
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.
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.
Translations
------------
Changes to translations as well as new translations can be submitted to
[Dash Core's Transifex page](https://www.transifex.com/projects/p/dash/).
Translations are periodically pulled from Transifex and merged into the git repository. See the
[translation process](doc/translation_process.md) 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](https://www.dash.org/forum/topic/dash-worldwide-collaboration.88/).
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.