Yenten; cryptocurrency of the cpu, by the cpu, for the cpu
Clone or download
Permalink
Failed to load latest commit information.
.tx first commit Oct 28, 2017
build-aux/m4 2.0.1 May 31, 2018
contrib 2.0.1 May 31, 2018
depends 2.0.1 May 31, 2018
doc 2.0.1 May 31, 2018
docs 2.0.1 May 31, 2018
share 2.0.1 May 31, 2018
src add chkpoint. fix wallet mining error. Jun 6, 2018
test 2.0.1 May 31, 2018
.gitattributes 2.0.1 May 31, 2018
.gitignore 2.0.1 May 31, 2018
.travis.yml 2.0.1 May 31, 2018
CONTRIBUTING.md 2.0.1 May 31, 2018
COPYING 2.0.1 May 31, 2018
INSTALL.md 2.0.1 May 31, 2018
Makefile.am 2.0.1 May 31, 2018
README.md 2.0.1 May 31, 2018
autogen.sh 2.0.1 May 31, 2018
configure.ac 2.0.1 May 31, 2018
libbitcoinconsensus.pc.in 2.0.1 May 31, 2018

README.md

Yenten Core integration/staging tree

original site

http://conan-equal-newone.github.io/yenten/

Developer GitHub

https://github.com/conan-equal-newone/

Discussion forum

https://bitcointalk.org/

What is Yenten?

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

For more information, as well as an immediately useable, binary version of the Yenten Core software, see https://github.com/conan-equal-newone/yenten/releases.

License

Yenten 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 regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Yenten Core.

The contribution workflow is described in CONTRIBUTING.md.

The developer Discussion forum should be used to discuss complicated or controversial changes before working on a patch set.

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

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