最近,須要接觸區塊鏈項目的主鏈開發,在EOS
、BTC
、ethereum
、超級帳本
這幾種區塊鏈技術當中,相互對比後,最終仍是以go-ethereum
爲解決方案。
以ethereum
爲基準去找解決方案,最終找到了2個符合本身要求的方案,分別以下:美圖、gttc。原本是想用gttc
的這個解決方案的,可是它是基於go-ethereum
最新源碼來進行二次開發的,相對不穩定,所以仍是用美圖
的解決方案了,畢竟這公司大一點,沒那麼多坑。javascript
爲了方便測試,咱們須要將節點最大驗證器數修改一下,這樣便於咱們進行簡單測試
修改consensus/dpos/dpos.go
文件的maxValidator
java
// 新值 maxValidatorSize = 21 // 舊值 maxValidatorSize = 3
# 進入源碼根目錄 docker build . -t meitugeth
注意:構建過程當中會用到
build\env.sh
文件,會提示無權限,所以你須要給該文件賦予執行權限。node
sudo chmod 777 build\env.sh
最好事先建立好相應的目錄,不然運行後,動態建立目錄,會有權限的問題,固然也能夠經過命令進行設置目錄的權限。linux
mkdir ~/data mkdir ~/data/meitu mkdir ~/data/meitu/node1 mkdir ~/data/meitu/node2 mkdir ~/data/meitu/node3
version: '3' services: meitu_node_1: image: meitugeth container_name: meitu_node_1 build: context: . command: --ipcpath "/root/.ethereum/geth.ipc" --port 30303 ports: - 15450:8545 - 15460:8546 - 10303:30303 - 10303:30303/udp - 10304:30304/udp volumes: - /etc/localtime:/etc/localtime - ~/data/meitu/node1/:/root/.ethereum/ environment: TZ: Asia/Shanghai meitu_node_2: image: meitugeth container_name: meitu_node_2 build: context: . command: --ipcpath "/root/.ethereum/geth.ipc" --port 30303 depends_on: - meitu_node_1 ports: - 25450:8545 - 25460:8546 - 20303:30303 - 20303:30303/udp - 20304:30304/udp volumes: - /etc/localtime:/etc/localtime - ~/data/meitu/node2/:/root/.ethereum/ environment: TZ: Asia/Shanghai meitu_node_3: image: meitugeth container_name: meitu_node_3 build: context: . command: --ipcpath "/root/.ethereum/geth.ipc" --port 30303 depends_on: - meitu_node_1 ports: - 45450:8545 - 45460:8546 - 40303:30303 - 40303:30303/udp - 40304:30304/udp volumes: - /etc/localtime:/etc/localtime - ~/data/meitu/node3/:/root/.ethereum/ environment: TZ: Asia/Shanghai
在根目錄下啓動3個以太坊節點git
docker-compose up --build -d
美圖以太坊這塊有2種啓動網絡:github
進入容器命令以下:web
# 模板 docker exec -it [容器名|容器ID] /bin/sh # 例子 docker exec -it meitu_node_1 /bin/sh docker exec -it meitu_node_2 /bin/sh docker exec -it meitu_node_3 /bin/sh
# 方式一 geth attach ipc:/root/.ethereum/geth.ipc # 方式二 docker exec -it meitu_node_1 geth attach ipc:/root/.ethereum/geth.ipc # 方式三:使用別名 alias geth="docker exec -it meitu_node_1 geth attach ipc:/root/.ethereum/geth.ipc"
進入geth JavaScript 控制檯後,需喲啊建立帳戶,命令以下;docker
# 模板 personal.newAccount('名稱') # 例子 personal.newAccount('test001') "0x849f9442198282fb21539351edb0378463e4c251" personal.newAccount('test002') "0x2c08f54d5b324c0175ea53b997f5ce1f61a7e4ed" personal.newAccount('test003') "0xc4118320f3d3c37a2ca8dad5c2f2a40f2a23ba02"
建立成功後,須要將返回的地址記錄起來json
loop:重複1-3步驟,在node一、node二、node3分別建立帳戶segmentfault
將上一步操做生成的地址寫入到創世塊文件中,三個節點的地址分別爲:
0x849f9442198282fb21539351edb0378463e4c251 0x2c08f54d5b324c0175ea53b997f5ce1f61a7e4ed 0xc4118320f3d3c37a2ca8dad5c2f2a40f2a23ba02
將3個節點地址列入第一批驗證人列表
{ "config": { "chainId": 7777, "eip155Block": 0, "eip158Block": 0, "byzantiumBlock":0, "dpos":{ "validators":[ "0x849f9442198282fb21539351edb0378463e4c251", "0x2c08f54d5b324c0175ea53b997f5ce1f61a7e4ed", "0xc4118320f3d3c37a2ca8dad5c2f2a40f2a23ba02" ] } }, "nonce": "0x0000000000000042", "difficulty": "0x020000", "mixHash": "0x0000000000000000000000000000000000000000000000000000000000000000", "coinbase": "0x0000000000000000000000000000000000000000", "timestamp": "0x00", "parentHash": "0x0000000000000000000000000000000000000000000000000000000000000000", "extraData": "0x11bbe8db4e347b4e8c937c1c8370e4b5ed33adb3db69cbdb7a38e1e50b1b82fa", "gasLimit": "0x500000", "alloc": {} }
創世配置參數說明:
hash
值,由於是創世塊,因此這個值是0nonce
配合用於挖礦,由上一個區塊的一部分生成hash
GAS
的消耗總量限制,用來限制區塊能包含的交易信息總和geth
目錄,保留keystore
移除geth
目錄,便於移除舊的無效數據,由於節點剛啓動的時候,使用的是默認創世配置,而自定義的又不同,所以須要移除。
sudo rm -rf ~/data/meitu/node1/geth sudo rm -rf ~/data/meitu/node2/geth sudo rm -rf ~/data/meitu/node3/geth
將創世配置拷貝到數據目錄中,便於容器內能訪問,至於這個目錄跟docker-compose.yml
映射的目錄有關。
所以,命令也要相應的變動。
cp genesis.json ~/data/meitu/node1 cp genesis.json ~/data/meitu/node2 cp genesis.json ~/data/meitu/node3
進入容器,並執行初始化命令。
# 節點1 docker exec -it meitu_node_1 /bin/sh geth init /root/.ethereum/genesis.json # 節點2 docker exec -it meitu_node_2 /bin/sh geth init /root/.ethereum/genesis.json # 節點3 docker exec -it meitu_node_3 /bin/sh geth init /root/.ethereum/genesis.json
**loop:重複在node二、node3上分別執行init
如下命令須要在docker-compose.yml
文件的當前目錄方可運行。
# 移除容器 docker-compose down # 啓動容器 docker-compose up -d
docker exec -it meitu_node_3 /bin/sh
geth attach ipc:/root/.ethereum/geth.ipc
dpos.getValidators() ["0x849f9442198282fb21539351edb0378463e4c251", "0x2c08f54d5b324c0175ea53b997f5ce1f61a7e4ed", "0xc4118320f3d3c37a2ca8dad5c2f2a40f2a23ba02"]
admin.peers []
返回的數據爲[]
,說明節點之間沒有互相發現。
admin.nodeInfo
確認:enode都不同,protocols都同樣。
記下三個enode
"enode://7f2f1a5818b4bb7e756036ab08834386534807bbf5c5a305ddcbefa1ff9ea99028feb00cb78322ac39340501d5b7c6147e169aadbb028daf20f8d73dbdfea98e@[::]:30303" "enode://6ab4f74058b9c1e43d2d0c6f55f538ea7f2f366dd9f8f560024f14603333f017d3404b9c9711538289fa76504fecf33cf0e36cce7b0414604f673abe93012413@[::]:30303" "enode://e82fecab04e5e902a9e4ea491527ea958d2cdeb83383dfa36562e32a51eedb204a541e00ef0b497704ec0e91017799a73283e53f6dffdeef492a4230626b10b6@[::]:30303"
# 顯示docker全部網絡信息 docker network ls # 查看具體網絡信息 docker network inspect [網絡名稱] # 例子 docker network inspect docker_default
執行查看網絡信息命令後,會返回一下內容
[ { "Name": "docker_default", "Id": "984fabf7e51b07c1984114720f98f305cc61cc26546cf9da4bcbbbc36a591351", "Created": "2018-12-05T06:06:13.435067024Z", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": null, "Config": [ { "Subnet": "172.20.0.0/16", "Gateway": "172.20.0.1" } ] }, "Internal": false, "Attachable": true, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "263f1553108cc8ea00b76598adb6d66649287943c7d0f50d0be02963863ff45c": { "Name": "meitu_node_2", "EndpointID": "9f4114a81133bd490b501ac45fd50fe512309f9096b5468054bd074bad45a07d", "MacAddress": "02:42:ac:14:00:03", "IPv4Address": "172.20.0.3/16", "IPv6Address": "" }, "3acd943c8e0759dc241d7cc623b1a1ca45096480dcd2fd0daa8b951407eb40bf": { "Name": "meitu_node_3", "EndpointID": "0480296c4e8217862358143a084da2d1563cd4f60105e6020434f222320681a5", "MacAddress": "02:42:ac:14:00:04", "IPv4Address": "172.20.0.4/16", "IPv6Address": "" }, "416fe5eb074c24f032d5bd49a6be68cf293a30af17780133b9fa63663e4b7097": { "Name": "meitu_node_1", "EndpointID": "0dc00e9c6f63f844502525b34e87baf62f4de852ac46907951d4b689dd89635f", "MacAddress": "02:42:ac:14:00:02", "IPv4Address": "172.20.0.2/16", "IPv6Address": "" } }, "Options": {}, "Labels": { "com.docker.compose.network": "default", "com.docker.compose.project": "docker", "com.docker.compose.version": "1.23.1" } } ]
找到不一樣容器中,相應的IP地址。
記錄下每一個節點的IP,也能夠用127.0.0.1
加節點映射到本機的不一樣網絡端口。
meitu_node_1 172.20.0.2 meitu_node_2 172.20.0.3 meitu_node_3 172.20.0.4
進入節點1
geth JavaScript 控制檯後,執行如下命令:
# 添加節點2的監視器 admin.addPeer("enode://6ab4f74058b9c1e43d2d0c6f55f538ea7f2f366dd9f8f560024f14603333f017d3404b9c9711538289fa76504fecf33cf0e36cce7b0414604f673abe93012413@[172.20.0.3]:30303") # 添加節點3的監視器 admin.addPeer("enode://e82fecab04e5e902a9e4ea491527ea958d2cdeb83383dfa36562e32a51eedb204a541e00ef0b497704ec0e91017799a73283e53f6dffdeef492a4230626b10b6@[172.20.0.4]:30303")
在執行完添加監視器後,執行admin.peers
便可看到節點已經互聯起來。
admin.peers [{ caps: ["eth/62", "eth/63"], id: "6ab4f74058b9c1e43d2d0c6f55f538ea7f2f366dd9f8f560024f14603333f017d3404b9c9711538289fa76504fecf33cf0e36cce7b0414604f673abe93012413", name: "Geth/v1.7.4-stable-a487fc95/linux-amd64/go1.9.7", network: { localAddress: "172.20.0.2:60018", remoteAddress: "172.20.0.3:30303" }, protocols: { eth: { difficulty: 131189, head: "0xa00badd4041033da53c0a34cce5aa59885d7f638e00e1e307b04c02ee640df19", version: 63 } } }, { caps: ["eth/62", "eth/63"], id: "e82fecab04e5e902a9e4ea491527ea958d2cdeb83383dfa36562e32a51eedb204a541e00ef0b497704ec0e91017799a73283e53f6dffdeef492a4230626b10b6", name: "Geth/v1.7.4-stable-a487fc95/linux-amd64/go1.9.7", network: { localAddress: "172.20.0.2:36700", remoteAddress: "172.20.0.4:30303" }, protocols: { eth: { difficulty: 131076, head: "0xe30ff3a8d1ae16384369c45d106841ef44e83c12eae2e2c66dce1bdccc9ba4d6", version: 63 } } }]
注意:這一步完成了,僅僅是臨時的,每次重啓docker以後admin.peers會從新爲空。
臨時互聯不方便,能夠將bootnodes
配置到啓動文件中。
修改docker-compose.yml
文件,將節點1
的鏈接配置進去。
version: '3' services: meitu_node_1: image: meitugeth container_name: meitu_node_1 build: context: .. command: --ipcpath "/root/.ethereum/geth.ipc" --port 30303 ports: - 15450:8545 - 15460:8546 - 10303:30303 - 10303:30303/udp - 10304:30304/udp volumes: - /etc/localtime:/etc/localtime - ~/data/meitu/node1/:/root/.ethereum/ environment: TZ: Asia/Shanghai meitu_node_2: image: meitugeth container_name: meitu_node_2 build: context: .. command: --ipcpath "/root/.ethereum/geth.ipc" --port 30303 --bootnodes enode://7f2f1a5818b4bb7e756036ab08834386534807bbf5c5a305ddcbefa1ff9ea99028feb00cb78322ac39340501d5b7c6147e169aadbb028daf20f8d73dbdfea98e@[172.20.0.2]:30303 depends_on: - meitu_node_1 ports: - 25450:8545 - 25460:8546 - 20303:30303 - 20303:30303/udp - 20304:30304/udp volumes: - /etc/localtime:/etc/localtime - ~/data/meitu/node2/:/root/.ethereum/ environment: TZ: Asia/Shanghai meitu_node_3: image: meitugeth container_name: meitu_node_3 build: context: .. command: --ipcpath "/root/.ethereum/geth.ipc" --port 30303 --bootnodes enode://7f2f1a5818b4bb7e756036ab08834386534807bbf5c5a305ddcbefa1ff9ea99028feb00cb78322ac39340501d5b7c6147e169aadbb028daf20f8d73dbdfea98e@[172.20.0.2]:30303 depends_on: - meitu_node_1 ports: - 45450:8545 - 45460:8546 - 40303:30303 - 40303:30303/udp - 40304:30304/udp volumes: - /etc/localtime:/etc/localtime - ~/data/meitu/node3/:/root/.ethereum/ environment: TZ: Asia/Shanghai
這個時候,「主網」啓動成功了!!!
分別在3個節點上把validator
無限期解鎖,誰不解鎖誰別出塊、跳過你。
這裏源碼默認10秒1塊。
進入geth JavaScript
控制檯後,執行如下命令:
# 模板 personal.unlockAccount(eth.validator,'名稱',0) # 例子 personal.unlockAccount(eth.validator,'jce001',0) personal.unlockAccount(eth.validator,'jce002',0) personal.unlockAccount(eth.validator,'jce003',0)
根據美圖解釋,這裏
validator
和coinbase
的區別:
進入geth JavaScript
控制檯後,執行如下命令:
miner.start()
進入geth JavaScript
控制檯後,執行如下命令:
# 模板 eth.getBlock(區塊編號) # 例子 eth.getBlock(1) # 結果 { coinbase: "0x849f9442198282fb21539351edb0378463e4c251", difficulty: 1, extraData: "0xd783010704846765746887676f312e392e37856c696e7578000000000000000084c3b20f15eb99c19bb8567d3a27a52947efb816f647cbc4491540ee5de685d54f4126d236f031d33312dfab1a5d7a895bbd4d154afd366b30918a9af6868ab300", gasLimit: 5237761, gasUsed: 0, hash: "0x30964585add8b4ef65529f38ebe00bb6581fc9ae7323327f7dfd666754de883b", logsBloom: "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000", mixHash: "0x0000000000000000000000000000000000000000000000000000000000000000", nonce: "0x0000000000000000", number: 1, parentHash: "0x9390ffeae9812417704193667a0e106c8cd9e701217deb054737dab0325191d3", receiptsRoot: "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421", sha3Uncles: "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347", size: 794, stateRoot: "0xc5a87ecb7262f6c507f488f5f93efa27df81550f1e7691c1ab2093a4218d2ca0", timestamp: 1543990290, totalDifficulty: 131073, transactions: [], transactionsRoot: "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421", uncles: [], validator: "0x849f9442198282fb21539351edb0378463e4c251" }
# 獲取帳戶 eth.accounts # 獲取餘額 eth.getBalance(帳戶地址) # 格式化長度 web3.fromWei(數值) # 獲取格式化後的餘額,默認取第一個帳戶 web3.fromWei(eth.getBalacne(eth.accounts[0])) # 獲取指定帳戶餘額 web3.fromWei(eth.getBalance("0x849f9442198282fb21539351edb0378463e4c251"))
# 模板 eth.sendTransaction({from: "發送者", to: "接受者", value: 數量}) # 例子 eth.sendTransaction({from: "0x849f9442198282fb21539351edb0378463e4c251", to: "0xc4118320f3d3c37a2ca8dad5c2f2a40f2a23ba02", value: 1000000000000000000})
經過獲取餘額判斷是否轉帳成功,也可經過返回的交易編號查詢狀況。
web3.eth.getTransactionReceipt('0x8a4104da45c736c7a671ff7974b9b9a1848ff4c001f3cbcd4eb427aab50d604f')