Posts

Showing posts with the label hyperledger-fabric

using schemaless data for Hyperledger Fabric/Composer?

Image
Clash Royale CLAN TAG #URR8PPP using schemaless data for Hyperledger Fabric/Composer? I need to store data from json files in hyperledger. The data is schemales. Hyperledger Fabric uses Couchdb which stores schemaless data. I need to query the data later on. But im unsure if Fabric can handle schemaless data because of the asset definition that is see in the example projects for example (in the marble project) // ----- Marbles ----- // type Marble struct { ObjectType string `json:"docType"` //field for couchdb Id string `json:"id"` //the fieldtags are needed to keep case from bouncing around Color string `json:"color"` Size int `json:"size"` //size in mm of marble Owner OwnerRelation `json:"owner"` } I know that in Composer you can't store schemaless data since you have to use assets. By clicking ...

peer node unable to create chaincode container - dial unix /host/var/run/docker.sock: connect: permission denied error

Image
Clash Royale CLAN TAG #URR8PPP peer node unable to create chaincode container - dial unix /host/var/run/docker.sock: connect: permission denied error I am trying to setup hyperledger network on centos Using 1.1.0 images from ibmblockchain docker hub. I am able to start up the network without any issues. that is 1 orderer, 3 kafkas, 3 zookeepers and 2 peers. But every time i try to instantiate chaincode, I see the below error in the peer docker containers. Can anyone help me with this issue. 2018-07-19 19:05:30.570 UTC [dockercontroller] Start -> ERRO 3ac start-could not recreate container , because of Post http://unix.sock/containers/create?name=dev-peer1.bns-250A-v1.0.2-b3: dial unix /host/var/run/docker.sock: connect: permission denied 2018-07-19 19:05:30.570 UTC [container] unlockContainer -> DEBU 3ad container lock deleted(dev-peer1.bns-250A-v1.0.2-b3) 2018-07-19 19:05:30.570 UTC [chaincode] launchAndWaitForRegister -> DEBU 3ae stopping due to error while launching: Post h...

Will the existing ledger (state + blockchain) also be shared with the new member to the channel?

Image
Clash Royale CLAN TAG #URR8PPP Will the existing ledger (state + blockchain) also be shared with the new member to the channel? In the scenario of adding a new member (a new organization's peer) to existing channel, will the whole previous ledger (state + blockchain) also be duplicated on this new peer? Or just the genesis/more recent reconfiguration block will be shared with the new member? As the doc below says, When adding a new member to an existing channel, either this genesis block, or if applicable, a more recent reconfiguration block, is shared with the new member. I found an answer in another question, New organizations can be added to the channel after its creation, and they would also be caught-up via gossip and then by virtue of receiving ordered transactions from the ordering service, etc. But I haven't found it explicitly in the document, not sure whether it is correct or not... Only found something related in the Gossip protocol doc : Bring newly connected peers ...