We have just migrated to Fabric 2.0 and all of our components (peer, orderer, binaries) are at v2.0.0.
Our Fabric Node SDK is still at v1.4.8 and most of its functions are working such as
createChannel, updateChannel, installChaincode etc.
However, when I try to use Channel.sendInstantiateProposal, I get an error
"Channel <channel_name> has been migrated to the new lifecycle. LSCC is now read only".
I get the fact that this is likely a mismatch between the SDK and the Fabric components, however, is there any way to get this to work besides upgrading to Fabric Node SDK 2.0?
The configtx.yaml file used to bring up the network has capabilities all set to V2.0:true. The notes indicate that V2.0 capabilities are non-backward compatible so I am assuming I cannot set them to V1.4 and still work with Fabric 2.0 components.
Thanks
In this case, the v1.4 SDK is compatible with v2, but the new chaincode architecture in v2 does not have an instantiation of the chaincode as part of its lifecycle. Instead, it uses a new, four-step process as defined in the official documentation. This is why the v1.4 SDK is failing at that line in particular, where you call Channel.sendInstantiateProposal(). The SDK is working fine, but that operation is not supported by the new chaincode lifecycle.
As for a solution, unfortunately, in v2 SDK there is no way to perform administrative tasks, and you have to use the Peer CLI for such operations.
The official documentation seems to confirm your assumption that SDKs are not necessarily forward-compatible when it comes to new features, such as the new chaincode lifecycle (see the blue 'Note' box).
Related
some files are missing from the Fabric samples, docker images, and binaries download like the first-network folder and others. how do I get the missing files imported on vscode?
At the time of writing, first-network no longer exists as a Hyperledger Fabric sample. If you are using an old versions of Fabric (for example, v1.4) and the corresponding documentation, which does describe first-network, you will need to make sure you specify the appropriate version when installing Fabric components so it pulls the samples from the correct branch of the samples repository. For Fabric v1.4, that would be this branch:
https://github.com/hyperledger/fabric-samples/tree/release-1.4
If you are using the latest version of the Fabric and its documentation, test-network is now used to deploy a sample network and chaincode.
Using HLF 1.4 and trying to conform to documentation, however, docs indicate that go 1.11.x MUST be installed -- is there not support for go 1.12.7? If not, when? 1.11.x is considered "archived".
Please advise. Thanks.
I'm currently running fabric 1.4.3 with go version 1.13.5 so it seems that the docs are out of date
I am quite new to Hyperledger Blockchain and have started with exploring 2 sample codes.
(1) https://medium.freecodecamp.org/ultimate-end-to-end-tutorial-to-create-an-application-on-blockchain-using-hyperledger-3a83a80cbc71 - where creating an application using hyperledger was taught - through creating .bna, .card files, deploying them etc. Also saw that an Angular extension is supported, giving the UI.
(2) Classic first-network http://hyperledger-fabric.readthedocs.io/en/release-1.1/build_network.html - where chaincode was deployed etc.
My question is, how can I get a UI for (2),like I did in (1)? It was quite convenient.
In the First tutorial, you used Hyperledger Composer to create a BNA which is a friendly way to create chaincode, and there is an Angular Application generator included.
In the second you directly installed some chaincode on to Fabric without a UI (and without using Composer. In this case you would have to write the UI yourself. In the first example you can build your own app by extending the generated app.
Composer is a tool that makes it easy and fast to create chaincode and applications to run on Fabric. If you don't use Composer you do have some more flexibility, but you have to do more work yourself.
What is the main goal to modify fabric source code from 0.6 version to 1.1?
what is the most important change logs ? Architecture? Please describe or provide some important reference!
Each release is accompanied by changelog entries linking to the JIRA issues closed (representing every commit), and we also publish release notes in two places: on the GitHub repositories (fabric, fabric-ca, fabric-sdk-node, fabric-sdk-java, fabric-chaincode-node) and in the documentation that uplevel to a more human accessible description of the major new features or changes.
tl;dr: v0.6 -> v1.0.0 was a major re-architecture of the consensus model and added support for channels. v1.1.0 -> v1.1.0 is a series of performance and scale improvements, added support for Javascript (Node.js) chaincode, added support for CouchDB and attribute based access control and a few other features, but is forward compatible with v1.0.x releases and can be upgraded in place.
I mean how know if the peer online or not, how many transactions/sec, for monitoring purpose?
I've tried searching the Node SDK design spec and no lucky.
try the blockchain explorer
It's proposal and documents are here. It works for fabric v-0.6 (I used it in my project last year), but it seems not support fabric v1.0 at this moment.