blockchain

来源： https://stackoverflow.com/questions/63041856/docker-exec-cli-peer-channel-create-failed-to-create-new-connection-context-d

来源： https://stackoverflow.com/questions/63041856/docker-exec-cli-peer-channel-create-failed-to-create-new-connection-context-d

问题 In hyperledger fabric, suppose there is a channel, 'channel_12' between org1 and org2 and another channel, 'channel_13' between org1 and org3. Suppose there are 2 users, 'Org1User1' & 'Org1User2' in org1. Can we restrict the access of Org1User1 to channel_12 and that of Org1User2 to channel_13? 回答1: One way with which we can achieve this is: While enrolling the user we can set the attributes in the X509 certificate for the user about which channel he has access to. For this, we need to

问题 I want my smart contract to return 7 or 8 UNIQUE random numbers ranging from 1 to 100 upon calling the contract. What can be the best approach to obtain such result? 回答1: Probably if you are trying to build roulettes, lotteries, and card games using the Ethereum blockchain, as the Ethereum blockchain is deterministic, it imposes certain difficulties for those who have chosen to write their own pseudo-random number generator (PRNG). Some Vulnerable Methods Currently Used If you are using the

问题 i get an error for hyperledger fabric. I followed the documentation and I came across his error when I ran the below command peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem the error being BAD_REQUEST -- error validating channel creation transaction for new channel

问题 i get an error for hyperledger fabric. I followed the documentation and I came across his error when I ran the below command peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem the error being BAD_REQUEST -- error validating channel creation transaction for new channel

问题 I could not find anything concrete about how Hyperledger Sawtooth handles the problem of infinite loops created by mistake or voluntarily by the developer (Only some issues regarding the IntKey transaction family Intkey workload command run in endless loop with wrong URL). I am sure that on Hyperledger Fabric the concept of the timeout of chain code execution avoids the creation of infinite loops, but which mechanism is used in Hyperledger Sawtooth ? Thanks! 回答1: The best thing to do is to

问题 npm start > server@1.0.0 start C:\Users\07\OneDrive\Desktop\Final Try\fabcar-blockchain-sample\web-app\server > ./node_modules/nodemon/bin/nodemon.js src/app.js '.' is not recognized as an internal or external command, operable program or batch file. npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! server@1.0.0 start: `./node_modules/nodemon/bin/nodemon.js src/app.js` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the server@1.0.0 start script. npm ERR! This is probably not a problem

问题 I am trying to run the byfn network in Hyperledger Fabric for version 1.4. I have started the containers, the crypto materials are setup, configuration is setup and the channel is created. However when it comes to the peer joining step i get the following error + peer channel join -b mychannel.block + res=1 + set +x 2020-02-12 07:53:23.356 UTC [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2020-02-12 07:53:23.395

问题 I am trying to run the byfn network in Hyperledger Fabric for version 1.4. I have started the containers, the crypto materials are setup, configuration is setup and the channel is created. However when it comes to the peer joining step i get the following error + peer channel join -b mychannel.block + res=1 + set +x 2020-02-12 07:53:23.356 UTC [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2020-02-12 07:53:23.395