Hi Fabric Community, I'm exploring the offline transaction signing flow in hyperledger fabric by using Fabric Node SDK. I came across the following official tutorial. https://hyperledger.github.io/fab

#fabric #fabric-sdk-node #fabric-offline-tx-signing #hyperledger-fabric

Hello Mark, Thank you for your reply. I will discuss with team here if we are good to go with off chain approach or just remove the date filter and fetch blocks, batch wise, like fetch blocks from lat

#fabric-sdk-node

The blocks in Fabric are just a chain of sequentially numbered blocks. They are not indexed by creation time. If you want to index them by creation time (or rather the timestamp of transactions contai

#fabric-sdk-node

thanks Anup. Actually we have created an independent client application (Plain HTML and Js based) to show transactions in a meaningful way to end user and showing all these information in Tree Grid on

#fabric-sdk-node

use event on chaincode action store blockdetails in offchaindb and query one user request comes

#fabric-sdk-node

Dear team, Please find sometime to review my concern. Is it possible to fetch all blocks using node sdk ? If yes then how? Or if there is any other way too please let me know. Thanks & Regards Madhwen

#fabric-sdk-node

Hello team, I am having an use-case where i have to show blocks as per date applied by the user. I am using hyper-ledger fabric v2.x with NodeJs sdk. Currently i am using for loop to fetch each block

#fabric-sdk-node

Hello, I have a HLF running on azure AKS cluster. I have a couchdb acting as a wallet to store the identities of the blockchain admin and users. It is hosted along with all the other pods. when i crea

#couchdb #fabric-kubernetes #hyperledger-fabric #kubernetes #fabric-sdk-node

If you do want to provide your own implementation of how the client waits for a submitted transaction to be committed by network peers, this tutorial has some useful information: https://hyperledger.g

#fabric-sdk-node

See the answer to the same question with nearly identical client code here: https://lists.hyperledger.org/g/fabric/topic/transaction_event_is_not/91619514 You are attaching your listener in the correc

#fabric-sdk-node

Hi Team, I am using fabric node sdk api for events. Transaction (commitEvent) is not working.New block is generated successfully but transaction event is not emitted. Passing eventhandler option in ga

#fabric-sdk-node

There look to be two issues here: You are listening for a transaction ID that you never submit, so no commit will ever occur. You are attaching your commit listener after the commit has occurred so it

#fabric-sdk-node

Hi fabric team, I am trying to implement transaction event in following way but somehow event is not invoke.Pls check below snippet code. ==============================================================

#fabric-sdk-node

Hi, I can run and test my Smart Contract manually using command like this without any error: peer chaincode invoke -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com --tls true --cafil

#fabric-sdk-node

Good day, Thank you for your reply! And apologies for my late reply. For the TLS certificates, I used the registerEnroll.sh script that is included in the test-network files (in /test-network/organiza

#hyperledger-fabric #fabric-sdk-node #fabric-orderer #fabric-peer

My guess has something to do with the TLS certs. In order to access your peers by the HL Fabric client, you need to configure the certificates properly. If you access them by IP instead of FQDN, you s

#hyperledger-fabric #fabric-sdk-node #fabric-orderer #fabric-peer

Hello everyone, I've been running into a problem with a Hyperledger Fabric network that I’ve deployed non-locally and I would like to ask for some insights or assistance regarding this problem. I depl

#hyperledger-fabric #fabric-sdk-node #fabric-orderer #fabric-peer

Those certificate verification failures during the TLS handshake look like a problem to me. I guess the node certificates are not valid for localhost. Maybe you could add entries to your client's loca

#fabric #kubernetes #fabric-sdk-node

Hello, we are running a Hyperledger Fabric network on Kubernetes (using minikube, kubectl to run locally) and then trying to connect the Node SDK with the network. Currently, we have a fabric network

#fabric #kubernetes #fabric-sdk-node

To close the loop on this one... we found that two peers were configured to use a single CouchDB database, and therefore the peers were stepping on each other and getting inconsistency between peer da

#fabric #fabric-peer #fabric-sdk-node #fabric-endorser #fabric-kubernetes