- Utilize leveldb for history of keys instead of couchdb

- Single leveldb database serves all chains to optimize
  footprint (same structure as leveldb block index database
  and leveldb state database)

- Block commit writes a history key for each key/value
  that is updated in a tran, in the form:
   ns~key~blocknum~trannum

- History database is an index for history of key writes
  over time.  The key values are not included to reduce
  size of database.

- GetHistoryForKey() finds all records starting with ~ns~key
  and returns the transactions that updated the key.

- Subsequent changeset will lookup and return the txid
  and historic value from the block storage.  Client can
  then GetTransactionById to see the historic transactions.

- Since history db size is much reduced, it is now enabled
  by default in core.yaml.

- Upon crash recovery, ledger initialization will ensure
  that both state db and history db in sync with block storage

Reused existing test logic, therefore the changeset
is relatively large to ensure tests still pass.

Change-Id: I79103aa39957f58d246de5b5295fb40a4b9c033b
Signed-off-by: denyeart <enyeart@us.ibm.com>

https://jira.hyperledger.org/browse/FAB-1859



The refactor and cleanup of "ccprovider" package
(core/common/ccprovider) paved way for further cleanup.
As a first step let us move back all the system chaincode (lscc,
vscc, cscc, qscc, escc) to be in their own packages under system_chaincodes.

Change-Id: Idfe91e351c97e97c614df808e3b1af9d207fd65a
Signed-off-by: Srinivasan Muralidharan <muralisr@us.ibm.com>

https://jira.hyperledger.org/browse/FAB-1856



The gossip team requires a way to be notified when the channel
configuration changes.  This changeset allows the configtx manager to be
constructed with a slice of functions to call when a new configuration
is committed.

Change-Id: Ib318e271b7c00685117d10d0982ccc8a09a9801e
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

point to new arch doc
point to design wiki page
fix false statement about endorsers
change consensus to ordering
[ci skip]

Change-Id: I8a22f424c5b36a872928bd48da0f275e1cdbc110
Signed-off-by: Nick Gaski <ngaski@us.ibm.com>

The normal flow for chaincode deployment involves an
implicit stop of the container as subphases of deployment.
However, devmode chaincode is primarily under the control
of a user, not the peer.  Therefore, the current peer
is broken for devmode because it tries to shutdown
the container after registration.  Because the chaincode
was started by the user, the stop ultimately fails but not
before the peer has confused its internal state by marking
it as down.

The primary problem is that subsequent calls into the
chaincode will ultimately fail on account of the quasi
running-but-not-really-running state and an inability
to try to correct the problem autonomously due to the
lack of control over the users process.

This patch addresses all of the above by acnowledging that
devmode chaincode should simply be left in a running
state.

Change-Id: I2e8f1f81a33019a10e3e65d1416ea4426a19e77a
Signed-off-by: Greg Haskins <gregory.haskins@gmail.com>

https://jira.hyperledger.org/browse/FAB-1851



This changeset adds a peer sharedconfig package.  The sharedconfig is
named as such, because it is configuration which is shared across all
peers for a channel, as opposed to the local configuration which the
peer sources from its yaml file.

Change-Id: I46bc408ed15a065020722666ee8e50d9f679e665
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

This commit adds a method VerifyByChannel that is channel-contexted
and does the same thing as Verify, just that it causes the MSP
layer to use a specific MSP manager.

Change-Id: I6b7401935f7751b434be893769810a3ba4fad76f
Signed-off-by: Yacov Manevich <yacovm@il.ibm.com>

https://jira.hyperledger.org/browse/FAB-1848



There is a typo in the peer/configuration.proto where instead of
specifying AnchorPeers, it specifies AnchorPees.  This CR fixes that.

Change-Id: I97333f76c838850d1891048ea9e33d826716519e
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

Add Response to ChaincodeAction. Reject proposal response that
status code >= 500 in endorse system chaincode.

Change-Id: Id441c3575941be3f11c044e083e482fb653740e5
Signed-off-by: jiangyaoguo <jiangyaoguo@gmail.com>

https://jira.hyperledger.org/browse/FAB-1840



Change-Id: If53dbe94604ae3cca1083bb31d40798a16adee02
Signed-off-by: Gabor Hosszu <gabor@digitalasset.com>

Make protos needed to be rerun to update the
proto of SBFT. These (non-test-breaking) changes
were left out from the last SBFT related commit.

Change-Id: I41be03c3738d43cc9cee943cc9ebeda0b03e5d25
Signed-off-by: Gabor Hosszu <gabor@digitalasset.com>

https://jira.hyperledger.org/browse/FAB-1825



This changeset populates the MSP manager via the config transaction via
the configtx.Handler interface.  It also moves the peer msp dir to
msp/mgmt as the peer needs to stop accessing this package directly and
use the MSP manager provided by the config resources.

Change-Id: I9ee08a46fa033ad0101dd80e770c7ee327a951d9
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

Made part of the testenv docker image. Might be easier in baseimage
but testenv is really intended for testing.

Unresolved question is how fabric-ca and fabric-sdk gets softhsm

Change-Id: I9cbb5590f23705b29c0cd0f80afdcc7920572072
Signed-off-by: Volodymyr Paprotski <vpaprots@ca.ibm.com>

Before pkcs11 modifications, sync up the two directories.

This applies the change from Angelo:
https://jira.hyperledger.org/browse/FAB-1276
https://gerrit.hyperledger.org/r/#/c/2983/



Change-Id: Ifbecd32567658d13ceaa250c702dba69f87ca655
Signed-off-by: Volodymyr Paprotski <vpaprots@ca.ibm.com>

Currently for debug purposes there is a log printout
which prints gossiping message from the delivery service
client. This is usefull while doing small debuging and
testing, while in heavy load it garbages the console.

This commit is to stop printing this message to reduce
log output and make it more usefull.

Change-Id: I20e3c38e9076cec09fd9438b42d3a56882399b54
Signed-off-by: Artem Barger <bartem@il.ibm.com>

Fixed all golint warnings under gossip/gossip/util

Change-Id: Ia68cdb4eee9e0737168b7e4a76b84e16c81f6602
Signed-off-by: Yacov Manevich <yacovm@il.ibm.com>

https://jira.hyperledger.org/browse/FAB-1812



The peer needs to apply configuration transactions as they are
committed.  This changeset hooks the configtx.Manager.Apply method into
core/committer/txvalidator/validator.go so that configuration is updated
as configuration blocks are committed.

Because it was in the same path, it also passes the MSPManager to the
validator to remove one of the dependencies on the throwaway MSP
multichain manager.

Change-Id: I4d606d850dddb684468d7a5dd7257e8dd967ad28
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

Print out original plaintext and digest when in
debug mode.
Helps SDK developers when debugging signature
issues as they can compare values on either side
of gRPC

Change-Id: I6286f0bf20a6ab71e72e8ddedcf167c661b41dcb
Signed-off-by: tuand27613 <tdang@us.ibm.com>