Hello; In terms of parsing the history really would need to be parsed to find specific values; depending on the size you could always put the data into a different data structure, so it becomes a clas

#fabric-chaincode #chaincode #database #fabric-questions

Hello, I use Level DB and I am using GetHistoryForKey to get the history of a key which return some records. Is there an efficient way to parse the returned records in order to find some specific valu

#fabric-chaincode #chaincode #database #fabric-questions

As a application owner and contract developer, you have the flexibility to define the structure of ledger data. You can handle it based on application needs in the contract/chaincode method which is m

#database

Hello FemGeek, In Hyperledger Fabric, data is already stored as a key-value representation. You can model the value structure as you please. For example: “key1”: “value1" or “key2”: { “property1”: “he

#database

Hello, I'm troubled about how to represent RCM Healthcare claim payments from payer as assets. How can I design the data to represent a key-value pair on the ledger.

#database

Hi everyone, I'm currently designing a private blockchain network for a government Certification authority that has services for cloud-based digital signatures. in the network I designed, the governme

#hyperledger-fabric #privatedata #database #aws

Hi everyone. We are trying to build an application in HL Fabric with CouchDB and Golang, and it has grown a bit too much, and now we have many data types where we need to make join equivalents in the

#couchdb #database #fabric

FYI: we are working with the GO SDK, and we have a struct with idCategory (integer) and another structure with the idCategory and its value. I need to "join" the result. Maybe the solution is not rela

#couchdb #database

Hi. My name is Rodrigo and I am starting with HF (v2.2). Can someone point me a link about how to perform a JOIN (the equivalent map-reduce) using couchdb? I need a doc, an example, something (I googl

#couchdb #database

The second version of the chaincode would have to support both the old and new data. There are various approaches possible: You could attempt to unmarshal the JSON using new data structure, and if it

#fabric #database #couchdb #fabric-chaincode #hyperledger-fabric

I've a query on how we need to deal with data structure changes in chaincode. Lets say, you have deployed the chaincode in production and lot of data stored in ledger and world state db(Couchdb). If y

#fabric #database #couchdb #fabric-chaincode #hyperledger-fabric

Thanks Matthew! I didn't know decoding it was so easy. By any chance, do you know how to get a block and decode it via APIs instead of CLI?

#fabric-sdk-node #database #fabric-questions

Thanks David! Will probably do your first pair of suggestions as it is the easiest to do for now. I'll be looking forward to the new snapshot feature though.

#fabric-sdk-node #database #fabric-questions

It is recommended to use endorsement policy > 1 to ensure that multiple peers are in agreement for each transaction. Similarly you can query multiple peers if the state is in doubt. This will protect

#fabric-sdk-node #database #fabric-questions

The value is base64 encoded, not encrypted. The value is represented as bytes and base64 is how bytes are represented in JSON. Your value is decoded as: {"class":"aipay.payment","key":"\"0004_workstat

#fabric-sdk-node #database #fabric-questions

In case of disputes, we need to provide assurance to our client that items in the couchdb are not manipulated and thus backed by transactions in the blockchain, which is secure and trusted by both par

#fabric-sdk-node #database #fabric-questions

In addition to CORE_PEER_GOSSIP_EXTERNALENDPOINT for exposing the peer endpoints to other orgs, make sure you understand how anchor peers are configured to bootstap the cross-org communication: https:

#fabric #database #consensus

Hi Dave, You are right and thank you for sending the lines of the default behaviour. After some investigations, I think I'm missing CORE_PEER_GOSSIP_EXTERNALENDPOINT. I have CORE_PEER_GOSSIP_BOOTSTRAP

#fabric #database #consensus

'peer node reset' should only be used if you suspect your peer's data is corrupted - it resets all channels to genesis block so that peer can re-pull/re-process blocks, but wouldn't change block disse

#fabric #database #consensus

Another note regarding this: Currently org2 is way more active in terms of gossip. Org1 is really "inactive". Org1 logs: 2019-11-07 12:51:40.979 UTC [gossip.discovery] periodicalSendAlive -> DEBU 1ae6

#fabric #database #consensus