8.7 KiB

Raw Permalink Blame History

Introduction

Welcome to the chia-blockchain project! We are happy that you are taking a look at the code for Chia, a proof of space and time cryptocurrency.

A lot of fascinating new cryptography and blockchain concepts are used and implemented here. This repo includes the code for the Chia full node, farmer, and timelord (in chia folder), which are all written in python. It also includes a verifiable delay function implementation that it imports from the chiavdf repo (in c/c++), and a proof of space implementation that it imports from the chiapos repo. BLS signatures are imported from the bls-signatures repo as blspy. There is an additional dependency on the chiabip158 repo. For major platforms, binary and source wheels are shipped to PyPI from each dependent repo. Then chia-blockchain can pip install those from PyPI or they can be prepackaged as is done for the Windows installer. On unsupported platforms, pip will fall back to the source distributions, to be compiled locally.

If you want to learn more about this project, read the wiki, or check out the green paper.

Contributions

Please review this diagram, to better understand the git workflow.

We would be pleased to accept code contributions to this project. As we have now released, the main priority is improving the mainnet blockchain. You can view our Product Roadmap to see what we are working on.

If you are interested in cryptography, math, or just like hacking in python, there are many interesting problems to work on. Contact any of the team members on Discord, which we use as the main communication method.

We ask that external contributors create a fork of the main branch for any feature work they wish to take on.

Members of the Chia organization may create feature branches from the main branch.

In the event an emergency fix is required for the release version of Chia, members of the Chia organization will create a feature branch from the current release branch latest.

Creating Signed Commits

Our branch protection rules require that all commits be signed. If you haven't signed your commits before, you can read about commit signing here: https://docs.github.com/en/authentication/managing-commit-signature-verification

There are detailed, per-OS steps for setting up commit signing with either GPG keys, SSH keys, or X.509 keys.

Branching Strategy

Branching Strategy Diagram

All changes go into the main branch.
Main is stable at all times, all tests pass.
Features (with tests) are developed and fully tested on feature branches, and reviewed before landing in main.
Chia Network's nodes on the public testnet are running the latest version x.y.z.
The main branch will have a long running beta testnet to allow previewing of changes.
Pull Request events may require a beta testnet review environment. At the moment this is at the discretion of the reviewer.
Hotfixes land in the release branch they fix, and all later versions. (This will be achieved by regularly merging from 1.3.x to main).
Hotfixes that are emergency fixes for a specific version will be merged into (???), and removed from down-stream branches. This allows future merges without issues.
Whoever develops a hotfix is also responsible for merging it into all later branches.
A release branch (e.g. 1.3.x) will be cut prior to a release, in order to separate work that should go into the release from work going into the next major release (main branch). (This pre-release branch will also have a beta testnet spun up for preview).
All Merge events will be squash merged.

Run tests and linting

The first time the tests are run, BlockTools will create and persist many plots. These are used for creating proofs of space during testing. The next time tests are run, this will not be necessary. Look at the pytest.ini file to configure how the tests are run. For example, for more logging: change the log level from WARNING to INFO, change -n auto to -n 0 and set log_cli = True.

sh install.sh -d
. ./activate
black . && isort benchmarks build_scripts chia tests tools *.py && mypy && flake8 benchmarks build_scripts chia tests tools *.py && pylint benchmarks build_scripts chia tests tools *.py
py.test tests -v --durations 0

The black library is used as an automatic style formatter to make things easier. The flake8 library helps ensure consistent style. The Mypy library is very useful for ensuring objects are of the correct type, so try to always add the type of the return value, and the type of local variables. The isort library is used to sort, group and validate imports in all python files. The pylint library is used to further lint all python files.

If you want verbose logging for tests, edit the tests/pytest.ini file.

Pre-Commit

We provide a pre-commit configuration which triggers several useful hooks (including linters/formatter) before each commit you make if you installed and set up pre-commit. This will help to reduce the time you spend on failed CI jobs.

To install pre-commit on your system see https://pre-commit.com/#installation. After installation, you can either use it manually with pre-commit run or let it trigger the hooks automatically before each commit by installing the provided configuration with pre-commit install.

Configure VS code

Install python extension
Set the environment to ./venv/bin/python
Install mypy plugin
Preferences > Settings > Python > Linting > flake8 enabled
Preferences > Settings > Python > Linting > mypy enabled
Preferences > Settings > Formatting > Python > Provider > black
Preferences > Settings > mypy > Targets: set to ./chia and ./tests

Configure Pycharm

Pycharm is an amazing and beautiful python IDE that some of us use to work on this project. If you combine it with python black and formatting on save, you will get a very efficient workflow. It's also especially efficient for git branching, cherry-picking, committing and pushing.

Run blackd in a terminal
Install BlackConnect plugin
Set to run python black on save
Set line length to 120
Install the linters in the root directory

Testnets and review environments

The current official testnet is testnet10. Look at chia/util/initial_config.yaml to see the configuration parameters for each testnet. Information on how to use the testnet can be found in the wiki.

Prior to proposing changes to main, proposers should consider if running a beta testnet review environment will make the reviewer more effective when evaluating a change. Changes that impact the blockchain could require a review environment before acceptance into main. This is at the discretion of the reviewer. Chia organization members have been granted CI access to deploy beta testnets. If you are not a Chia organization member, you can enquire about deploying a beta testnet in the public dev Keybase channel.

Submit changes

To propose changes, please make a pull request to the main branch. See Branching Strategy above.

To propose changes for the production releases of Chia, please make a pull request to the latest release branch.

Copyright

By contributing to this repository, you agree to license your work under the Apache License Version 2.0, or the MIT License, or release your work to the public domain. Any work contributed where you are not the original author must contain its license header with the original author(s) and be in the public domain, or licensed under the Apache License Version 2.0 or the MIT License.

8.7 KiB Raw Permalink Blame History