I am new to hyperledger fabric so I started with the documentation.
Hyperledger Fabric Documentation: https://hyperledger-fabric.readthedocs.io
I found one more readthedocs which is explaining the fabric too.
https://openblockchain.readthedocs.io
What are the differences between them and which I should prefer as developer?
thanks
I think it is the same thing (They explain about Hyperledger Fabric), but the official docs of Hyperledger Fabric its more practical, you have the First Network tutorial, chaincode tutorials, etc, and the Open Fabric Docs its like more theorical.
OpenBlockchain is for Fabric 0.6, which is no longer being worked on.
Related
I am new to Hyperledger Fabric and when I followed the Hyperledger Fabric chaincode tutorial, the go importing failed as below. How to solve it? Thank you! The Hyperledger Fabric version is 2.4. Go version is 1.18.
This sounds like its more of a general golang question about dependencies than anything specific to hyperledger fabric, so maybe worth reading about go module dependencies for example https://go.dev/doc/modules/managing-dependencies
I'm trying to use DIDs/VCs from hyperledger Indy with Hyperledger Fabric. Simply I want to replace Fabric's certificate based identity/MSP with DIDs/VCs. However, as far as I understand this is not direct. The existing code based have lots of dependencies on Fabric-CA. Could someone help me to figure out potential starting points to do this customisation?
you cant try to use this modified peen-node:
https://github.com/trustbloc/fabric-mod
https://github.com/trustbloc/trustbloc-did-method/blob/main/docs/spec/trustbloc-did-method.md
or read this research:
https://arxiv.org/pdf/2104.03277.pdf
or check other did:methods that support HLF:
https://www.w3.org/TR/did-spec-registries/
or look to this project:
https://github.com/BLOCKOTUS/blockotus-organism
Currently, the only framework that can verify DID/VCs from Hyperldeger Indy is the Hyperledger Aries. There are several projects where people are trying to integrate either some of the Indy or Aries functionalities into Fabric in order to be able to issue and verify DID/VCs.
Take a look at the following projects in the "Hyperledger Mentorship Program" community:
Hyperledger Fabric - Hyperledger Aries Integration to support Fabric as Blockchain ledger
Or an older project Extending HL Fabric for connecting with HL Indy.
However, the easiest way is to have two DLTs, one for DID/VCs issue and verification (Indy), and one for transactions, etc.
I'm using the fabcar project: https://github.com/IBM/blockchain-application-using-fabric-java-sdk
It uses HyperLedger 1.4.1. I would like to know a bit more about privacy-enhancing solutions.
How is Zero Knowledge Proof (ZKP) implemented?
Are there any other techniques or solutions implemented?
Thank you very much.
You can implement it using Identity Mixer as stated by IBM Hyperledger Dcoumentation.But I have not come across any working example so far neither from IBM Hypeledger site nor any other unofficial dev blogs.
https://hyperledger-fabric.readthedocs.io/en/latest/idemix.html
I've been studying the Hyperledger Fabric framework reading the docs for quite a while now but I'm getting a little lost in the middle of all that info. My question is: Is there any guidelines/"Step by step" on how to design a blockchain network from scratch? If you are starting a new project, where do you start?
Because I think I would understand it way more quicker if I actually started coding a little instead of reading and reading and reading...
Thanks a lot!
Edit 1:
I've chosen #kekomal answer as the correct one but I'd like to thank #Isha Padalia for the awesome VS Code extension and tutorial.
If you are really interested in learning and diving into Hyperledger Fabric, avoid byfn script. It performs a lot of magic for building a very simple Hyperledger Fabric network. After that, you have a network that you don't know how has been created and you have absolutely no idea of how to start deploying your custom network. There are daily questions here from people who started that way and are absolutely lost.
I find interesting this tutorial: https://medium.com/beyondi/setup-the-hyperledger-fabric-network-from-scratch-b82913b47549. Take into account that it is a little bit outdated.
You can complement it with this newer tutorial: https://www.blockchainexpert.uk/blog/how-to-deploy-hyperledger-fabric-network-from-scratch. Don't only run the steps. Analyze the files in https://github.com/blockchain-expert/hyperledger-fabric-network-from-scratch. Try playing with configtx.yaml, crypto-config.yaml and docker-compose files to customize your network and understand what you are doing.
Customize your organizations, your consortiums, your ordering service, your peers... Create your channels, join them, update your anchor peers... And understand what you are doing.
After that, if your network had one orderer, deploy a new one with more than one (with Raft consensus). If your network was using cryptogen, deploy a new one using Fabric-CAs instead. Or you can follow by playing with chaincodes.
NOTE: Apart from Hyperledger Fabric itself, it is essential to have basic notions of docker and PKI.
You are a beginner in Hypelredger fabric development then you have first cleared the concept of the orderer, peer, CA, and organization concept. And then first you have to start IBM Blockchain Platform VS Code extension for fabric. It will provide a local fabric environment to create, test and deploy a fabric smart contract. Also generate 1 peer, 1 orderer, 1 CA service under VS code environment.
Here is a link to start development with VS code extension.
Hope it will help you:)
hi #d3v9 start from here https://hyperledger-fabric.readthedocs.io/en/release-1.4/build_network.html. also you can find some great article on medium
Will anyone explains about consensus in hyperledger fabric and how it will work in fabric with a simple example. I have gone through so many websites but I didn't get any idea. please let me know anyone. thanks in advance.
Read this high-level description, and the transaction flow diagram it links to.
The official documentation is always a good place to start...