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>
      9eb99b3f
  3. 21 Oct, 2016 1 commit
    • Gregory Haskins's avatar
      Revert "... uses hardcoded hashcode for example02" · e3fe1e09
      Gregory Haskins authored
      This reverts commit 5d9a3eab
      
      .
      
      chaincode_example04 calls chaincode_example02 via a hard-coded ID.
      This is intentional to catch change to the ID when NOTHING in
      chaincode_example02 or in its folder changes.  ie, a test for the
      constancy of the hash generation algorithm.
      
      The patch attempt pass the ID as a parameter to prevent accidental
      changes to chaincode_example02 from causing test failures. While
      well-intented, this subverts the above reasoning behind the
      hard-coding.
      
      Also note that chaincode_example05 does take the argument as a
      parameter (so that usage is already covered).
      
      Change-Id: I8e305efb6fd577bc7d7e3d720d293cfb0e3c191f
      Signed-off-by: default avatarGreg Haskins <gregory.haskins@gmail.com>
      e3fe1e09
  4. 14 Oct, 2016 1 commit
  5. 03 Oct, 2016 1 commit
  6. 16 Sep, 2016 1 commit
    • Angelo De Caro's avatar
      C2C invocation for confidential contracts. · 5f9b3ea0
      Angelo De Caro authored
      This PR addresses chaincode to chaincode invocation for confidential contracts
      (https://jira.hyperledger.org/browse/FAB-67
      
      ). In order to achieve the goal
      the chaincode handler has been modified to contruct proper ephemeral
      transactions and security contexts.
      
      Let us consider the following scenario to describe the modification
      apported by this PR. Let us say that we have two chaincodes: A and B
      where A invokes B at some point of its computation.
      When a user invoke a chaincode A, using transaction tx,
      the certificate that the user has put in tx is passed to B when A
      invokes it. In this way, for example, chaincode B can perfom
      attribute-based access control. In addition,
      each chaincode can access it is own encrypted state and modify
      it in a proper way without affecting other chaincodes' state.
      
      This PR has been tested by adding a unit test in exectransaction_test.go.
      The unit tests, verify that C2C invocation can be perfomed when
      security is enabled.
      
      What will come next:
      1. Chaincode to chaincode query.
      2. Additional fields transfered to the invoked chaincode to
      support access control based on signature.
      
      Change-Id: I649d1953ac76e8af32d917a089a454fc0bba9fc1
      Signed-off-by: default avatarAngelo De Caro <adc@zurich.ibm.com>
      5f9b3ea0
  7. 08 Sep, 2016 1 commit
  8. 07 Sep, 2016 1 commit
  9. 04 Sep, 2016 1 commit
  10. 01 Sep, 2016 1 commit
  11. 31 Aug, 2016 2 commits
  12. 23 Aug, 2016 1 commit
  13. 16 Aug, 2016 1 commit
    • Brad Gorman's avatar
      GitHub Issue #2119 - chaincode unittesting · 23afd056
      Brad Gorman authored
      
      
      Replaced ChaincodeStub with ChaincodeStubInterface to allow
      unit testing of chaincode. MockStub added to emulate a real
      chaincode without the storage or network requirements.
      Unit test examples for chaincode_example02 to 05.
      
      I have another changeset to address tables and certificates.
      
      Change-Id: I37d6115781436e080a70d5c48c1128ee01fef3ba
      Signed-off-by: default avatarBradley Gorman <bgorman@au1.ibm.com>
      23afd056
  14. 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>
      fd498d2f
  15. 01 Aug, 2016 1 commit
    • grapebaba's avatar
      Refactor db package · 9544025c
      grapebaba authored
      
      
      Currently db will open when GetDBHandle method is invoked first time,
      so GetDBHandle method needs to use mutex.
      This patch makes db open and close in its lifecycle methods Start and
      Stop, invokes Start only when peer starts and invokes Stop when peer
      stops.
      After that, methods in db do not need to support concurrency.
      
      Change-Id: Id8612f2a846c5d626bd42c5cd4ae482076f6a975
      Signed-off-by: default avatargrapebaba <281165273@qq.com>
      9544025c
  16. 31 Jul, 2016 1 commit
  17. 26 Jul, 2016 1 commit