Blockchain CBDH Practice Test - Questions Answers, Page 8

Explorer can view, invoke, deploy or query blocks, transactions and associated data, network information, chain codes and transaction families, as well as other relevant information stored in the ledger. Powerful, easy-to-use, highly maintainable, open source browser for viewing activity on the underlying blockchain network.

Reference: https://fabric-docs-test.readthedocs.io/en/latest/glossary/#chaincode

Reference: http://tutorialsdiary.com/hyperledger-fabric-tutorials-chaincode-interface-chaincodestubinterface/

Users can use chaincode (for business rules) and membership service (for digital tokens) to design assets, as well as the logic that manages them. There are two popular approaches to defining assets in most blockchain solutions: the stateless UTXO model, where account balances are encoded into past transaction records; and the account model, where account balances are kept in state storage space on the ledger. Each approach carries its own benefits and drawbacks. This blockchain fabric does not advocate either one over the other. Instead, one of our first requirements was to ensure that both approaches can be easily implemented with tools available in the fabric.

Reference: https://hyperledger-fabric.readthedocs.io/en/release-1.4/chaincode4ade.html

Chaincode may be deployed on multiple channels, each instance is isolated within its channel. Each channel maintains their own chaincode and ledger.

There are generally two ways to develop business contracts: the first way is to code individual contracts into standalone instances of chaincode; the second way, and probably the more efficient way, is to use chaincode to create decentralized applications that manage the life cycle of one or multiple types of business contracts, and let end users instantiate instances of contracts within these applications Reference: https://fabric-docs- test.readthedocs.io/en/latest/FAQ/chaincode_FAQ/