1. 26 Oct, 2016 1 commit
  2. 24 Oct, 2016 1 commit
    • Srinivasan Muralidharan's avatar
      FAB-631 WIP - pared down peer for next arch work · 9eb99b3f
      Srinivasan Muralidharan authored
      Following skeletal end to end flow work, this submit
      takes the next steps for Endorser/Committer
        . converts chaincode and endorser to ledgernext
        . removes consensus package
        . chaincode unit tests use ledgernext
        . panics if ledger.GetLedger is called so we
          can catch codepaths that still use that. These
          are mainly core/api and core/peer
        . removes unit tests from core/api and core/ledger
          (to avoid GetLedger calls there)
        . created a minimal core/peernext. core/peer is
          still there for comparison but is not used
      Change-Id: I2627e0000e960e1aa66d27ff5ec60a38c4bb7eea
      Signed-off-by: default avatarSrinivasan Muralidharan <muralisr@us.ibm.com>
  3. 30 Sep, 2016 1 commit
  4. 17 Sep, 2016 1 commit
    • Srinivasan Muralidharan's avatar
      chaincode life-cycle system chaincode for a chain · a3687a1f
      Srinivasan Muralidharan authored
      The life-cycle system chaincode (lccc) manages chaincodes for a chain in an
      endorser. The life-cycle is basically the "deploy", "upgrade", "stop"
      and "start" actions. This changeset provides the basic chaincode for
      creating the table of chaincodes and implements just the "deploy" command.
      This work will be developed till the basic endorser functions are fully
      This driver for this chaincode will be checked in the next changeset.
      NOTE - this change also fixes the limitation where only one system chaincode
      can be running at a time.
      This is part of the feature development of FAB-181, FAB-182, FAB-183.
      Change-Id: Iff36fee7c5b9a9ce4658910db73304a6bcd7e3d4
      Signed-off-by: default avatarSrinivasan Muralidharan <muralisr@us.ibm.com>
  5. 10 Aug, 2016 1 commit
    • Gabor Hosszu's avatar
      Use repeated bytes instead of repeated string for chaincode call args · fd498d2f
      Gabor Hosszu authored
      This allows applications to easily pass arbitrary blobs without having
      to serialize them to strings.  At the same time, we also consolidate
      the function argument to be part of the repeated bytes args.
      For convenience and to simplify porting of existing chaincode to the
      new argument format, we introduce helper functions in the shim which
      cast between ([][]byte) and (string, []string).
      Change-Id: I67562523a208727157c4767e86e1ef437e997f13
      Signed-off-by: default avatarGabor Hosszu <gabor@digitalasset.com>
  6. 26 Jul, 2016 1 commit