四倚聚、Fabric2.4.6 智能合約(java)（ubuntu 22.04）

一、maven打包項(xiàng)目

mvn clean package
生成 target/chaincode.jar,之所以沒(méi)有直接用源碼，是因?yàn)榘惭b鏈碼的時(shí)候术裸，需要構(gòu)建maven倘是，拉取依賴等，時(shí)間太長(zhǎng)袭艺；

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創(chuàng)建并安裝鏈碼包

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

# 創(chuàng)建鏈碼包
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

# 查詢安裝結(jié)果 （fabric-smart-contract_1 已經(jīng)安裝成功）
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創(chuàng)建并安裝鏈碼包

# 拷貝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

四瘪撇、通過(guò)鏈碼定義

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
# 檢查通道成員是否已批準(zhǔn)相同的鏈碼定義
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
# 檢查通道成員是否已批準(zhǔn)相同的鏈碼定義
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
# 檢查通道成員是否已批準(zhǔn)相同的鏈碼定義
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
# 檢查通道成員是否已批準(zhǔn)相同的鏈碼定義
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

# 查詢確認(rèn)鏈碼已提交到通道
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]

六、調(diào)用鏈碼

# 調(diào)用鏈碼倔既，插入數(shù)據(jù)恕曲，第一次調(diào)用需要 --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" , "發(fā)起人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\"}"

# 查詢結(jié)果
bash-5.1# peer chaincode query -C mychannel -n fabric-smart-contract -c '{"Args":["queryHashInfo","hash-0"]}'
{"fileHash":"hash1","initiator":"發(fā)起人1"}

# 調(diào)用鏈碼，插入數(shù)據(jù)
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" , "發(fā)起人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\"}"

# 查詢結(jié)果
bash-5.1# peer chaincode query -C mychannel -n fabric-smart-contract -c '{"Args":["queryHashInfo","hash-1"]}'
{"fileHash":"hash2","initiator":"發(fā)起人2"}

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

五渤涌、Fabric2.4.6 在java應(yīng)用訪問(wèn)智能合約（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

最后編輯于：2023.11.24 15:28:27

?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請(qǐng)聯(lián)系作者

人面猴
序言：七十年代末佩谣，一起剝皮案震驚了整個(gè)濱河市，隨后出現(xiàn)的幾起案子歼捏，更是在濱河造成了極大的恐慌稿存，老刑警劉巖，帶你破解...
沈念sama閱讀 212,383評(píng)論 6贊 493
死咒
序言：濱河連續(xù)發(fā)生了三起死亡事件瞳秽，死亡現(xiàn)場(chǎng)離奇詭異瓣履，居然都是意外死亡，警方通過(guò)查閱死者的電腦和手機(jī)练俐，發(fā)現(xiàn)死者居然都...
沈念sama閱讀 90,522評(píng)論 3贊 385
救了他兩次的神仙讓他今天三更去死
文/潘曉璐我一進(jìn)店門袖迎，熙熙樓的掌柜王于貴愁眉苦臉地迎上來(lái)，“玉大人腺晾，你說(shuō)我怎么就攤上這事燕锥。” “怎么了悯蝉？”我有些...
開(kāi)封第一講書人閱讀 157,852評(píng)論 0贊 348
道士緝兇錄：失蹤的賣姜人
文/不壞的土叔我叫張陵归形，是天一觀的道長(zhǎng)。經(jīng)常有香客問(wèn)我鼻由，道長(zhǎng)暇榴，這世上最難降的妖魔是什么厚棵？我笑而不...
開(kāi)封第一講書人閱讀 56,621評(píng)論 1贊 284
?港島之戀（遺憾婚禮）
正文為了忘掉前任，我火速辦了婚禮蔼紧，結(jié)果婚禮上婆硬，老公的妹妹穿的比我還像新娘。我一直安慰自己奸例，他們只是感情好彬犯，可當(dāng)我...
茶點(diǎn)故事閱讀 65,741評(píng)論 6贊 386
惡毒庶女頂嫁案：這布局不是一般人想出來(lái)的
文/花漫我一把揭開(kāi)白布。她就那樣靜靜地躺著查吊，像睡著了一般谐区。火紅的嫁衣襯著肌膚如雪。梳的紋絲不亂的頭發(fā)上逻卖，一...
開(kāi)封第一講書人閱讀 49,929評(píng)論 1贊 290
城市分裂傳說(shuō)
那天卢佣，我揣著相機(jī)與錄音，去河邊找鬼箭阶。笑死，一個(gè)胖子當(dāng)著我的面吹牛戈鲁，可吹牛的內(nèi)容都是我干的仇参。我是一名探鬼主播，決...
沈念sama閱讀 39,076評(píng)論 3贊 410
雙鴛鴦連環(huán)套：你想象不到人心有多黑
文/蒼蘭香墨我猛地睜開(kāi)眼婆殿，長(zhǎng)吁一口氣：“原來(lái)是場(chǎng)噩夢(mèng)啊……” “哼诈乒！你這毒婦竟也來(lái)了？” 一聲冷哼從身側(cè)響起婆芦，我...
開(kāi)封第一講書人閱讀 37,803評(píng)論 0贊 268
萬(wàn)榮殺人案實(shí)錄
序言：老撾萬(wàn)榮一對(duì)情侶失蹤怕磨，失蹤者是張志新（化名）和其女友劉穎，沒(méi)想到半個(gè)月后消约，有當(dāng)?shù)厝嗽跇?shù)林里發(fā)現(xiàn)了一具尸體肠鲫，經(jīng)...
沈念sama閱讀 44,265評(píng)論 1贊 303
?護(hù)林員之死
正文獨(dú)居荒郊野嶺守林人離奇死亡，尸身上長(zhǎng)有42處帶血的膿包…… 初始之章·張勛以下內(nèi)容為張勛視角年9月15日...
茶點(diǎn)故事閱讀 36,582評(píng)論 2贊 327
?白月光啟示錄
正文我和宋清朗相戀三年或粮，在試婚紗的時(shí)候發(fā)現(xiàn)自己被綠了导饲。大學(xué)時(shí)的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片。...
茶點(diǎn)故事閱讀 38,716評(píng)論 1贊 341
活死人
序言：一個(gè)原本活蹦亂跳的男人離奇死亡氯材，死狀恐怖渣锦，靈堂內(nèi)的尸體忽然破棺而出，到底是詐尸還是另有隱情氢哮，我是刑警寧澤袋毙，帶...
沈念sama閱讀 34,395評(píng)論 4贊 333
?日本核電站爆炸內(nèi)幕
正文年R本政府宣布，位于F島的核電站冗尤，受9級(jí)特大地震影響听盖，放射性物質(zhì)發(fā)生泄漏胀溺。R本人自食惡果不足惜，卻給世界環(huán)境...
茶點(diǎn)故事閱讀 40,039評(píng)論 3贊 316
男人毒藥：我在死后第九天來(lái)索命
文/蒙蒙一媳溺、第九天我趴在偏房一處隱蔽的房頂上張望月幌。院中可真熱鬧，春花似錦悬蔽、人聲如沸扯躺。這莊子的主人今日做“春日...
開(kāi)封第一講書人閱讀 30,798評(píng)論 0贊 21
一樁弒父案蝎困，背后竟有這般陰謀
文/蒼蘭香墨我抬頭看了看天上的太陽(yáng)录语。三九已至，卻和暖如春禾乘，著一層夾襖步出監(jiān)牢的瞬間澎埠，已是汗流浹背。一陣腳步聲響...
開(kāi)封第一講書人閱讀 32,027評(píng)論 1贊 266
情欲美人皮
我被黑心中介騙來(lái)泰國(guó)打工始藕，沒(méi)想到剛下飛機(jī)就差點(diǎn)兒被人妖公主榨干…… 1. 我叫王不留蒲稳，地道東北人。一個(gè)月前我還...
沈念sama閱讀 46,488評(píng)論 2贊 361
代替公主和親
正文我出身青樓伍派，卻偏偏與公主長(zhǎng)得像江耀，于是被迫代替她去往敵國(guó)和親。傳聞我的和親對(duì)象是個(gè)殘疾皇子诉植，可洞房花燭夜當(dāng)晚...
茶點(diǎn)故事閱讀 43,612評(píng)論 2贊 350

四抵栈、Fabric2.4.6 智能合約(java)（ubuntu 22.04）

四倚聚、Fabric2.4.6 智能合約(java)（ubuntu 22.04）

一、maven打包項(xiàng)目

四瘪撇、通過(guò)鏈碼定義

五获茬、將鏈碼定義提交給通道

六、調(diào)用鏈碼

推薦閱讀更多精彩內(nèi)容