No description, website, or topics provided.
Clone or download
Pull request Compare This branch is 14933 commits ahead, 3 commits behind zeroonecoin:master.
Evydder Merge pull request #14 from zocteam/0.12.3.2
changed version number in README.md
Latest commit f176feb Aug 30, 2018
Permalink
Failed to load latest commit information.
.github Use "Dash Core" instead of "dash-core" in some places and Dashify Jan 16, 2018
.tx rebase Apr 30, 2018
build-aux/m4 merged Dash v0.12.3.2 Jul 26, 2018
contrib forgot to add some files to the previous commit Jul 26, 2018
depends merged Dash v0.12.3.2 Jul 26, 2018
doc forgot to add some files to the previous commit Jul 26, 2018
docker Automatically build and push docker image to docker.io/dashpay/dashd-… Jan 10, 2018
qa forgot to add some files to the previous commit Jul 26, 2018
share merged Dash v0.12.3.2 Jul 26, 2018
src preparing 0.12.3.2 Aug 29, 2018
zeroone-docs merged Dash v0.12.3.2 Jul 26, 2018
.dockerignore rebase Apr 30, 2018
.gitignore merged Dash v0.12.3.2 Jul 26, 2018
.travis.yml merged Dash v0.12.3.2 Jul 26, 2018
CMakeLists.txt forgot to add some files to the previous commit Jul 26, 2018
CONTRIBUTING.md merged Dash v0.12.3.2 Jul 26, 2018
COPYING merged Dash v0.12.3.2 Jul 26, 2018
Dockerfile rebase Apr 30, 2018
INSTALL.md Dashify INSTALL.md and build-unix.md Jan 12, 2018
Makefile.am forgot to add some files to the previous commit Jul 26, 2018
README.md changed version number in README.md Aug 30, 2018
autogen.sh Merge #8784: Copyright headers for build scripts Jan 12, 2018
configure.ac preparing 0.12.3.2 Aug 29, 2018
docker-compose.yml rebase Apr 30, 2018
dockerentry.sh updated to dash 0.12.2.3, WIP, needs a lot of testing May 12, 2018
libzerooneconsensus.pc preparing 0.12.3.2 Aug 29, 2018
libzerooneconsensus.pc.in forgot to add some files to the previous commit Jul 26, 2018

README.md

ZeroOne

01coin Community v0.12.3.2

Bitcointalk ANN thread

Discord Community

What is the 01coin Community?

01coin is an innovative, cryptographically-secured digital asset ledger based on blockchain technology. Developed in part from the core code behind Dash, 01coin includes many innovative enhancements. 01coin aims to become the most community-centric project in all of crypto. Born out of its own ashes when the original development team mysteriously disappeared one month after the coin launched, it is now completely managed and operated by the community. This includes a large and dedicated team of community moderators always ready and willing to help new users. It also includes a strong principle of community governance: no decision will be made unilaterally by a single individual or by an oligarchy of the few. Every step forward for 01coin will be determined by community votes and masternode governance. As such, we don’t know yet exactly what 01coin will look like a year from now, but we do know it will look exactly like the coin you want it to be.

License

The 01coin 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 the 01coin 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.