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.
Related
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).
I need to develop one project on hyperledger-fabric using a GO SDK. But as per the latest release GO SDKs that have not yet been officially released.
I had gone through with this post. But still, is it better to use a Go-SDK for any development of the product? So anyone knows it's products or web projects which are in used?
From the chat of the go-sdk-fabric:
fabric-sdk-go is stable. The reason that still in beta just for missing some documentation
The package works but it is kind of a mess, the only documentation are the chainhero example, the test files and the go-doc. There are a lot of package and some of them seems to do the same but they're not always compatible with each other.
I has been deployed (this awesome deprecated tool named) hyperledger composer. After a couple of days working, click on a network card emit an error and I'm unable to login. After give up, reinstall everything from zero, does not remove this cards. Already deleted ~/compose* files, also teardown fabric and docker containers.
So my problem have two solutions:
One, find where are composer model and scripts stored to recover.
Two, fix and/or remove these files.**
Question: Where are CTO and js script files stored?
I will suggest you not to you use Composer as it is has been deprecated. Please read here. https://github.com/hyperledger/composer/blob/master/README.md
Hey could someone help me with this doubt?
I am a very beginner and not the typical profile of a developer. For a project I need to define the environment around blockchain. I need to define every tool you need and everything to install to develop and deploy software using Hyperledger Fabric.
As far as I know I will need to install the prereqs:
Docker Engine
Docker Compose
Node
npm
git
Python
VS Code
All of them are considered developing tools, isn't it?
Other tools I need will be:
Clients (CLI tools)
Apache server?
Playground. (What is that?)
IDE
Hyperledger Fabric (Is it similar to the EVM?)
Loopback and Swagger??
APIs
Anything else to add? Really thankful for helping me
you wil not need a server initially during developement (can be done locally). An IDE (VSCode is one of them !) will not be needed if you are already getting VSCode. If youre a beginner - Hyperledger Composer (runs over a hyperledger fabric instance) would probably be better to start with. Playground as you mentioned is a user interface of sorts that helps in defining,deploying and testing blockchain networks (can be visited online at https://composer-playground.mybluemix.net/). To develop networks locally you could download them and develop locally. There are many links available and if you need more I would be happy to link them ! (This series is also very helpful (IBMs ZeroToBlockchain playlist - https://www.youtube.com/watch?v=CgGX-BTYOwA&list=PLnJzIOiv6cVTjaJRtJ2srarhs-m4V3zs3)
Hyperledger Explorer is also a very useful tool for viewing your network and the data stored in the ledger.
You ought to check out Chaincoder IDE. It is a project I am working on. Helping people to get started with Hyperledger Fabric and uses almost standard CLI commands and configuration files of Fabric to get a blockchain system running either locally with docker or remote with different hosts. It is free and easy to use.
http://www.chaincoder.org/
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.