高度模块化, 遵循 KISS原则的区块链开发框架
官方网站 和 文档: https://chain.33.cn
官方插件库: https://github.com/33cn/plugin
典型案例: https://github.com/bityuan/bityuan
chain33背后故事: chain33诞生记
视频教程: 视频教程
环境要求: Go (version 1.9 or later)
编译:
git clone https://github.com/33cn/chain33.git $GOPATH/src/github.com/33cn/chain33
cd $GOPATH/src/github.com/33cn/chain33
make
测试:
$ make test
通过这个命令可以运行一个单节点到环境,可以用于开发测试
$ chain33 -f chain33.toml
- 不可以使用 master 分支,要使用 发布分支
- vendor 依赖不要重建,未来我们可能会支持自己下载vendor目录,但是目前,我们不支持这样做。
我们先说一下代码贡献的细节流程,这些流程可以不看,用户可以直接看我们贡献代码简化流程
- 如果有什么想法,建立 issues, 和我们来讨论。
- 首先点击 右上角的 fork 图标, 把chain33 fork 到自己的分支 比如我的是 vipwzw/chain33
git clone https://github.com/vipwzw/chain33.git $GOPATH/src/github.com/33cn/chain33
注意:这里要 clone 到 $GOPATH/src/github.com/33cn/chain33, 否则go 包路径会找不到
-
添加
33cn/chain33
远端分支:git remote add upstream https://github.com/33cn/chain33.git
我已经把这个加入了 Makefile 可以直接 运行make addupstream
-
保持
33cn/chain33
和vipwzw/chain33
master 分支的同步,可以直接跑make sync
, 或者执行下面的命令
git fetch upstream
git checkout master
git merge upstream/master
注意:不要去修改 master 分支,这样,master 分支永远和upstream/master 保持同步
- 从最新的33cn/chain33代码建立分支开始开发
git fetch upstream
git checkout master
git merge upstream/master
git branch -a "fixbug_ci"
- 开发完成后, push 到
vipwzw/chain33
git fetch upstream
git checkout master
git merge upstream/master
git checkout fixbug_ci
git merge master
git push origin fixbug_ci
然后在界面上进行pull request
- 首先点击 右上角的 fork 图标, 把chain33 fork 到自己的分支 比如我的是 vipwzw/chain33
git clone https://github.com/vipwzw/chain33.git $GOPATH/src/github.com/33cn/chain33
注意:这里要 clone 到 $GOPATH/src/github.com/33cn/chain33, 否则go 包路径会找不到
make addupstream
make branch b=mydevbranchname
make push b=mydevbranchname m="这个提交的信息"
如果m不设置,那么不会执行 git commit 的命令
比如我要修改 name=libangzhu branch chain33-p2p-listenPort 的pr
make pull name=libangzhu b=chain33-p2p-listenPort
然后修改代码,修改完成后,并且在本地commit
make pullpush name=libangzhu b=chain33-p2p-listenPort
BSD 3-Clause License
Copyright (c) 2018, 33.cn
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
* Neither the name of the copyright holder nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.