四、Fabric2.4.6 智能合约(java)（ubuntu

作者: 一介书生独醉江湖 | 来源:发表于2023-11-22 15:03 被阅读0次

2019-06-26 eos合约编写
智能合约 hello world
教你用Java开发一个简单的JVM
优得学员第九课笔记 Ulord原链及技术优势（下）
投票合约
基于星云链的智能合约与Dapp（四）——编写并运行智能合约
火箭入门GXChain开发系列第一篇|简介与运行原理
读《区块链社会--解码区块链全球应用与投资案例》第二章-----
以太坊智能合约---工作原理
智能合约-让区块链能做更多的事情

一、maven打包项目

mvn clean package
生成 target/chaincode.jar,之所以没有直接用源码，是因为安装链码的时候，需要构建maven，拉取依赖等，时间太长；

dongsheng@dongsheng-virtual-machine:~/raft-test/chaincode/java/fabric-smart-contract$ sudo cp -r /home/dongsheng/下载/chaincode.jar /home/dongsheng/raft-test/chaincode/java/fabric-smart-contract
dongsheng@dongsheng-virtual-machine:~/raft-test/chaincode/java/fabric-smart-contract$ cd /home/dongsheng/raft-test/chaincode/java/fabric-smart-contract
dongsheng@dongsheng-virtual-machine:~/raft-test/chaincode/java/fabric-smart-contract$ ls
chaincode.jar

二、cli1创建并安装链码包

dongsheng@dongsheng-virtual-machine:~/raft-test/chaincode/java$ sudo docker cp fabric-smart-contract/ cli1:/opt/gopath/src/github.com/hyperledger/fabric-cluster/chaincode/java
Successfully copied 32.2MB to cli1:/opt/gopath/src/github.com/hyperledger/fabric-cluster/chaincode/java

# 创建链码包
bash-5.1# peer lifecycle chaincode package fabric-smart-contract.tar.gz --path /opt/gopath/src/github.com/hyperledger/fabric-cluster/chaincode/java/fabric-smart-contract/ --lang java --label fabric-smart-contract_1
bash-5.1# ls
fabric-smart-contract         fabric-smart-contract.tar.gz

# 安装链码包
bash-5.1# peer lifecycle chaincode install fabric-smart-contract.tar.gz
2023-11-11 10:08:12.747 UTC 0001 INFO [cli.lifecycle.chaincode] submitInstallProposal -> Installed remotely: response:<status:200 payload:"\nXfabric-smart-contract_1:478df03c7d1ff61d6b738a0af1e77d364b92f9a0820b7bc17824c3d27dbe4c25\022\027fabric-smart-contract_1" > 
2023-11-11 10:08:12.862 UTC 0002 INFO [cli.lifecycle.chaincode] submitInstallProposal -> Chaincode code package identifier: fabric-smart-contract_1:478df03c7d1ff61d6b738a0af1e77d364b92f9a0820b7bc17824c3d27dbe4c25

# 查询安装结果 （fabric-smart-contract_1 已经安装成功）
bash-5.1# peer lifecycle chaincode queryinstalled
Installed chaincodes on peer:
Package ID: fabric-smart-contract_1:478df03c7d1ff61d6b738a0af1e77d364b92f9a0820b7bc17824c3d27dbe4c25, Label: fabric-smart-contract_1
Package ID: sacc_1:84ca9adc1a80b0964ac0b8bad50042a75dbd8aa25bb4df8f4073e9818d17f1e6, Label: sacc_1

三、cli2、cli3、cli4创建并安装链码包

# 拷贝fabric-smart-contract.tar.gz到本地；
bash-5.1# cp /opt/gopath/src/github.com/hyperledger/fabric-cluster/chaincode/java/fabric-smart-contract.tar.gz /opt/gopath/src/github.com/hyperledger/fabric/peer/

bash-5.1# exit
# 将fabric-smart-contract.tar.gz分别拷贝到cli2、cli3、cli4容器；
dongsheng@dongsheng-virtual-machine:~/raft-test$ docker cp cli1:/opt/gopath/src/github.com/hyperledger/fabric/peer/fabric-smart-contract.tar.gz ./

dongsheng@dongsheng-virtual-machine:~/raft-test$ docker cp fabric-smart-contract.tar.gz cli2:/opt/gopath/src/github.com/hyperledger/fabric/peer/
Successfully copied 28.9MB to cli2:/opt/gopath/src/github.com/hyperledger/fabric/peer/

dongsheng@dongsheng-virtual-machine:~/raft-test$ docker cp fabric-smart-contract.tar.gz cli3:/opt/gopath/src/github.com/hyperledger/fabric/peer/
Successfully copied 28.9MB to cli3:/opt/gopath/src/github.com/hyperledger/fabric/peer/
 
dongsheng@dongsheng-virtual-machine:~/raft-test$ docker cp fabric-smart-contract.tar.gz cli4:/opt/gopath/src/github.com/hyperledger/fabric/peer/
Successfully copied 28.9MB to cli4:/opt/gopath/src/github.com/hyperledger/fabric/peer/

# cli2 安装链码包
dongsheng@dongsheng-virtual-machine:~/raft-test$ docker exec -it cli2 bash

bash-5.1# peer lifecycle chaincode install fabric-smart-contract.tar.gz
2023-11-11 10:29:09.428 UTC 0001 INFO [cli.lifecycle.chaincode] submitInstallProposal -> Installed remotely: response:<status:200 payload:"\nXfabric-smart-contract_1:478df03c7d1ff61d6b738a0af1e77d364b92f9a0820b7bc17824c3d27dbe4c25\022\027fabric-smart-contract_1" > 
2023-11-11 10:29:10.309 UTC 0002 INFO [cli.lifecycle.chaincode] submitInstallProposal -> Chaincode code package identifier: fabric-smart-contract_1:478df03c7d1ff61d6b738a0af1e77d364b92f9a0820b7bc17824c3d27dbe4c25

# cli3 安装链码包
dongsheng@dongsheng-virtual-machine:~/raft-test$ docker exec -it cli3 bash

bash-5.1# peer lifecycle chaincode install fabric-smart-contract.tar.gz
2023-11-11 10:32:54.067 UTC 0001 INFO [cli.lifecycle.chaincode] submitInstallProposal -> Installed remotely: response:<status:200 payload:"\nXfabric-smart-contract_1:478df03c7d1ff61d6b738a0af1e77d364b92f9a0820b7bc17824c3d27dbe4c25\022\027fabric-smart-contract_1" > 
2023-11-11 10:32:54.100 UTC 0002 INFO [cli.lifecycle.chaincode] submitInstallProposal -> Chaincode code package identifier: fabric-smart-contract_1:478df03c7d1ff61d6b738a0af1e77d364b92f9a0820b7bc17824c3d27dbe4c25

# cli4 安装链码包
dongsheng@dongsheng-virtual-machine:~/raft-test$ docker exec -it cli4 bash

bash-5.1# peer lifecycle chaincode install fabric-smart-contract.tar.gz
2023-11-11 10:35:34.752 UTC 0001 INFO [cli.lifecycle.chaincode] submitInstallProposal -> Installed remotely: response:<status:200 payload:"\nXfabric-smart-contract_1:478df03c7d1ff61d6b738a0af1e77d364b92f9a0820b7bc17824c3d27dbe4c25\022\027fabric-smart-contract_1" > 
2023-11-11 10:35:35.174 UTC 0002 INFO [cli.lifecycle.chaincode] submitInstallProposal -> Chaincode code package identifier: fabric-smart-contract_1:478df03c7d1ff61d6b738a0af1e77d364b92f9a0820b7bc17824c3d27dbe4c25

四、通过链码定义

dongsheng@dongsheng-virtual-machine:~/raft-test/chaincode/java$ docker exec -it cli1 bash

bash-5.1# peer lifecycle chaincode approveformyorg --channelID mychannel --name fabric-smart-contract --version 1.0 --init-required --package-id fabric-smart-contract_1:478df03c7d1ff61d6b738a0af1e77d364b92f9a0820b7bc17824c3d27dbe4c25 --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
2023-11-11 10:52:49.529 UTC 0001 INFO [cli.lifecycle.chaincode] setOrdererClient -> Retrieved channel (mychannel) orderer endpoint: orderer0.example.com:7050
2023-11-11 10:52:56.585 UTC 0002 INFO [chaincodeCmd] ClientWait -> txid [772c837d2123ef457a95700391c662cedd006525ea2a4f39af35c8ce7bc25b39] committed with status (VALID) at peer0.org1.supervisor.com:7051

bash-5.1# exit

dongsheng@dongsheng-virtual-machine:~/raft-test/chaincode/java$ docker exec -it cli2 bash
bash-5.1# peer lifecycle chaincode approveformyorg --channelID mychannel --name fabric-smart-contract --version 1.0 --init-required --package-id fabric-smart-contract_1:478df03c7d1ff61d6b738a0af1e77d364b92f9a0820b7bc17824c3d27dbe4c25 --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
2023-11-11 10:53:58.457 UTC 0001 INFO [cli.lifecycle.chaincode] setOrdererClient -> Retrieved channel (mychannel) orderer endpoint: orderer0.example.com:7050
2023-11-11 10:54:00.792 UTC 0002 INFO [chaincodeCmd] ClientWait -> txid [eafa06ed223d7ef33108e53367885229c96b581086f4ee4ffba443b0fe31898f] committed with status (VALID) at peer0.org2.build.com:9051

bash-5.1# exit

dongsheng@dongsheng-virtual-machine:~/raft-test/chaincode/java$ docker exec -it cli3 bash
bash-5.1# peer lifecycle chaincode approveformyorg --channelID mychannel --name fabric-smart-contract --version 1.0 --init-required --package-id fabric-smart-contract_1:478df03c7d1ff61d6b738a0af1e77d364b92f9a0820b7bc17824c3d27dbe4c25 --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
2023-11-11 10:54:59.517 UTC 0001 INFO [cli.lifecycle.chaincode] setOrdererClient -> Retrieved channel (mychannel) orderer endpoint: orderer0.example.com:7050
2023-11-11 10:55:02.007 UTC 0002 INFO [chaincodeCmd] ClientWait -> txid [deee7f81ccbb79a9872335334db40ce7325551fc5b4e191fa68fd6f7d0424470] committed with status (VALID) at peer0.org3.supplier.com:11051

bash-5.1# exit

dongsheng@dongsheng-virtual-machine:~/raft-test/chaincode/java$ docker exec -it cli4 bash
bash-5.1# peer lifecycle chaincode approveformyorg --channelID mychannel --name fabric-smart-contract --version 1.0 --init-required --package-id fabric-smart-contract_1:478df03c7d1ff61d6b738a0af1e77d364b92f9a0820b7bc17824c3d27dbe4c25 --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
2023-11-11 10:55:45.161 UTC 0001 INFO [cli.lifecycle.chaincode] setOrdererClient -> Retrieved channel (mychannel) orderer endpoint: orderer0.example.com:7050
2023-11-11 10:55:47.854 UTC 0002 INFO [chaincodeCmd] ClientWait -> txid [a837db479b27e544f41cc6903304d38e6bf20f5e3bdae8f1d40df883c4a1a783] committed with status (VALID) at peer0.org4.logistics.com:13051
bash-5.1# exit

五、将链码定义提交给通道

dongsheng@dongsheng-virtual-machine:~/raft-test/chaincode/java$ docker exec -it cli1 bash
# 检查通道成员是否已批准相同的链码定义
bash-5.1# peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name fabric-smart-contract --version 1.0 --init-required --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --output json
{
"approvals": {
"Org1MSP": true,
"Org2MSP": true,
"Org3MSP": true,
"Org4MSP": true
}
}
bash-5.1# exit

dongsheng@dongsheng-virtual-machine:~/raft-test/chaincode/java$ docker exec -it cli2 bash
# 检查通道成员是否已批准相同的链码定义
bash-5.1# peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name fabric-smart-contract --version 1.0 --init-required --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --output json
{
"approvals": {
"Org1MSP": true,
"Org2MSP": true,
"Org3MSP": true,
"Org4MSP": true
}
}
bash-5.1# exit

dongsheng@dongsheng-virtual-machine:~/raft-test/chaincode/java$ docker exec -it cli3 bash
# 检查通道成员是否已批准相同的链码定义
bash-5.1# peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name fabric-smart-contract --version 1.0 --init-required --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --output json
{
"approvals": {
"Org1MSP": true,
"Org2MSP": true,
"Org3MSP": true,
"Org4MSP": true
}
}
bash-5.1# exit

dongsheng@dongsheng-virtual-machine:~/raft-test/chaincode/java$ docker exec -it cli4 bash
# 检查通道成员是否已批准相同的链码定义
bash-5.1# peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name fabric-smart-contract --version 1.0 --init-required --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --output json
{
"approvals": {
"Org1MSP": true,
"Org2MSP": true,
"Org3MSP": true,
"Org4MSP": true
}
}
bash-5.1# exit

# 将链码提交到通道
dongsheng@dongsheng-virtual-machine:~$ docker exec -it cli1 bash
bash-5.1# peer lifecycle chaincode commit -o orderer0.example.com:7050 --channelID mychannel --name fabric-smart-contract --version 1.0 --sequence 1 --init-required --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --peerAddresses peer0.org1.supervisor.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.supervisor.com/peers/peer0.org1.supervisor.com/tls/ca.crt --peerAddresses peer0.org2.build.com:9051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.build.com/peers/peer0.org2.build.com/tls/ca.crt --peerAddresses peer0.org3.supplier.com:11051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.supplier.com/peers/peer0.org3.supplier.com/tls/ca.crt --peerAddresses peer0.org4.logistics.com:13051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org4.logistics.com/peers/peer0.org4.logistics.com/tls/ca.crt

# 查询确认链码已提交到通道
bash-5.1# peer lifecycle chaincode querycommitted --channelID mychannel --name fabric-smart-contract --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
Committed chaincode definition for chaincode 'fabric-smart-contract' on channel 'mychannel':
Version: 1.0, Sequence: 1, Endorsement Plugin: escc, Validation Plugin: vscc, Approvals: [Org1MSP: true, Org2MSP: true, Org3MSP: true, Org4MSP: true]

六、调用链码

# 调用链码，插入数据，第一次调用需要 --isInit
bash-5.1# peer chaincode invoke -o orderer0.example.com:7050 --isInit --ordererTLSHostnameOverride orderer0.example.com --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n fabric-smart-contract --peerAddresses peer0.org1.supervisor.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.supervisor.com/peers/peer0.org1.supervisor.com/tls/ca.crt --peerAddresses peer0.org2.build.com:9051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.build.com/peers/peer0.org2.build.com/tls/ca.crt --peerAddresses peer0.org3.supplier.com:11051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.supplier.com/peers/peer0.org3.supplier.com/tls/ca.crt --peerAddresses peer0.org4.logistics.com:13051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org4.logistics.com/peers/peer0.org4.logistics.com/tls/ca.crt -c '{"function":"createHashInfo","Args":["hash-0" , "id1" ,  "hash1" , "发起人1"]}'
2023-11-11 11:57:05.937 UTC 0001 INFO [chaincodeCmd] chaincodeInvokeOrQuery -> Chaincode invoke successful. result: status:200 payload:"{\"fileHash\":\"hash1\",\"initiator\":\"\345\217\221\350\265\267\344\272\2721\"}"

# 查询结果
bash-5.1# peer chaincode query -C mychannel -n fabric-smart-contract -c '{"Args":["queryHashInfo","hash-0"]}'
{"fileHash":"hash1","initiator":"发起人1"}

# 调用链码，插入数据
bash-5.1# peer chaincode invoke -o orderer0.example.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n fabric-smart-contract --peerAddresses peer0.org1.supervisor.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.supervisor.com/peers/peer0.org1.supervisor.com/tls/ca.crt --peerAddresses peer0.org2.build.com:9051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.build.com/peers/peer0.org2.build.com/tls/ca.crt --peerAddresses peer0.org3.supplier.com:11051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.supplier.com/peers/peer0.org3.supplier.com/tls/ca.crt --peerAddresses peer0.org4.logistics.com:13051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org4.logistics.com/peers/peer0.org4.logistics.com/tls/ca.crt -c '{"function":"createHashInfo","Args":["hash-1" , "id2" ,  "hash2" , "发起人2"]}'
2023-11-11 12:02:53.377 UTC 0001 INFO [chaincodeCmd] chaincodeInvokeOrQuery -> Chaincode invoke successful. result: status:200 payload:"{\"fileHash\":\"hash2\",\"initiator\":\"\345\217\221\350\265\267\344\272\2722\"}"

# 查询结果
bash-5.1# peer chaincode query -C mychannel -n fabric-smart-contract -c '{"Args":["queryHashInfo","hash-1"]}'
{"fileHash":"hash2","initiator":"发起人2"}

# java智能合约
# git地址：https://gitee.com/baihu_shusheng/fabric-smart-contract.git

五、Fabric2.4.6 在java应用访问智能合约（ubuntu 22.04）

# 参考
https://blog.csdn.net/Wannabe_hacker/article/details/129203886
https://www.bilibili.com/video/BV1DR4y1M74B/?spm_id_from=333.337.search-card.all.click&vd_source=ef83736476a46166544cd38458b6b130

2019-06-26 eos合约编写
1、环境搭建运行环境是ubuntu18参考EOS笔记四合约工具eosio.cdt使用、 EOS 智能合约开发点滴...
智能合约 hello world
这是智能合约的入门教程，从hello world开始智能合约之旅。一、安装ubuntu系统 1、从官网下载ubu...
教你用Java开发一个简单的JVM
一、前言几年前，接到一个开发任务：用Java开发能运行Java智能合约的虚拟机。在开发Java智能合约时，只能使...
优得学员第九课笔记 Ulord原链及技术优势（下）
Ulord里面四个关键技术，智能合约，共识算法，隐私保护，即时支付。首先是智能合约，首先明白什么是智能合约，智能...
投票合约
编写简单的投票合约，体验智能合约从编写到发布的整个过程，环境 ubuntu16.04。本篇内容是建立在以太坊编程...
基于星云链的智能合约与Dapp（四）——编写并运行智能合约
一般智能合约需要以下几个步骤：1.编写智能合约2.部署智能合约3.调用智能合约，验证合约执行结果编写智能合约 N...
火箭入门GXChain开发系列第一篇|简介与运行原理
第一期：智能合约简介与运行原理智能合约简介智能合约应用场景智能合约与dapp 智能合约运行原理 webass...
读《区块链社会--解码区块链全球应用与投资案例》第二章-----
第二章-----智能合约 08 一、什么是智能合约智能合约是能够自动执行合约条款的计算机程序。二、智能合约的三...
以太坊智能合约---工作原理
一、什么叫智能合约智能合约其实不是合约也不智能，只是它能跑着区块链上的代码。二、智能合约语言 Solidity...
智能合约-让区块链能做更多的事情
智能合约智能合约：智能合约是一种计算机协议，在以太坊中最重要的应用就是设计和部署只能合约。智能合约最早在1995...