Current Build State
Download the latest release from github
Install the latest release from the Snap Store
BYTZ Officlal Web Page
BYTZ is a blockchain-based entertainment utility protocol powered by a cryptographically secure multilayered network. Decentralized delivery yields low-cost, high-speed, high-definition media access globally. Consumers will be able to spend BYTZ cryptocurrency (BYTZ) on some of the best entertainment the world has to offer. Tickets will be forgery resistant, virtually eliminating fraud. Service providers holding BYTZ can earn even more by storing and delivering content.
Together with this use case BYTZ also features fast transactions with low transaction fees and a low environmental footprint. It utilizes a custom Proof of Stake protocol for securing its network and uses an innovative token system to bring you network validated, secure fungible and non-fungible tokens.
For more information, as well as an immediately useable, binary version of the Bytz Core software, see https://bytz.gg/getbytz/.
Bytz Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.
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 Bytz Core.
The contribution workflow is described in CONTRIBUTING.md.
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.
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 CircleCI build system makes sure that every pull request is built for Windows, Linux, and OS X, and that unit/sanity tests are run automatically.
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.
Changes to translations as well as new translations can be submitted to Bytz 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.