1. 03 Feb, 2017 1 commit
    • manish's avatar
      Move Blockstorage code under /fabric/common package · 2a16532c
      manish authored
      https://jira.hyperledger.org/browse/FAB-2022
      
      
      
      This changes introduced by this CR
      - Moves the block storage code from package
      core/ledger/blkstorage to common/ledger/blkstorage
      
      - Splits the ledger_interface.go so as to move common interfaces
      and data type to common/ledger package
      
      - Moves some of the util functions to common/ledger package
      
      - Moves core/ledger/ordererledger package to orderer/ledger/fsledger
      orderer folks can futher rename/refactor this as seems suitable to them
      
      Change-Id: I759e16f00dc2ec9bb62196121083cf48eae76948
      Signed-off-by: default avatarmanish <manish.sethi@gmail.com>
      2a16532c
  2. 25 Jan, 2017 1 commit
  3. 11 Jan, 2017 1 commit
    • Jason Yellick's avatar
      Move core/util to common/util · 289b1a29
      Jason Yellick authored
      
      
      As a matter of policy, the only imports a package should have outside of
      its base dir are protos/ vendor/ and common/.  The core/util package was
      referenced all over the code, so moving it to common seems like the best
      option.
      
      Change-Id: Ic7d797be6a1b44634480a361ae7469b794685762
      Signed-off-by: default avatarJason Yellick <jyellick@us.ibm.com>
      289b1a29
  4. 01 Dec, 2016 1 commit
  5. 30 Nov, 2016 1 commit
    • Srinivasan Muralidharan's avatar
      FAB-1230 - use **TEST_CHAINID** for tests and skeleton · f7b3336d
      Srinivasan Muralidharan authored
      https://jira.hyperledger.org/browse/FAB-1230
      
      
      
      Orderer sets the stage for multichain by forcing brodcast
      and deliver clients to specify ChainID. The solo orderer
      provides a default chain called **TEST_CHAINID** to continue
      development with.
      
      It would have been easy to hard code **TEST_CHAINID** in
      the lower most utility calls to continue work - basically
      inside protos/utils/ functions.
      
      However, this changeset takes the next step fo moving to
      using multichain by exposing chainID in core APIs thus
      forcing higher layers to deal with chains. Currently these
      high layers are unit tests, CLI and SDK.
      
      CLI accepts chain ID via the "-C" param which when not provided
      defaults to **TEST_CHAINID**.
      
      Change-Id: I0d7894c8f17ce8fae6fe075c9865afae58499005
      Signed-off-by: default avatarSrinivasan Muralidharan <muralisr@us.ibm.com>
      f7b3336d
  6. 28 Nov, 2016 1 commit
  7. 27 Nov, 2016 1 commit
    • Srinivasan Muralidharan's avatar
      FAB-1198-rm old pb.Transaction, pb.Block · 61affa05
      Srinivasan Muralidharan authored
      NOTE - Removing of old proto.Transaction is the cause for
      the large change set. It affects chaincode framework and
      all users of the framework such as endorser, system chaincodes,
      unit tests etc.
      
      Transaction2 is renamed to Transaction.
      Response2 is renamed to Response.
      Message2 is renamed to Message.
      
      The changes are fully described in
          https://jira.hyperledger.org/browse/FAB-1198
      
      
      
      Summary
      =======
         . Remove old Transaction and rename Transaction2
         . Cleanup of Chaincode protobuf message
         . Add TxID for SDK and higher layers to optionally
           set (currently errors if not set)
      
      ChaincodeMessage removes QUERY and QUERY_CHAINCODE enums.
      
      Shim interface does not enforce Query or QueryChaincode.
      
      chaincode_example02 and 05 implement Query function via
      the Invoke implementation.
      
      The "noop" system chaincode is removed
         . it was using Transaction which is not an endorser
           artifact any longer
         . there are many system chaincodes to that thoroughly
           test sys chaincode functions
      
      Change-Id: Ib77b7e5a6756eac47e888309816076580ae505e7
      Signed-off-by: default avatarSrinivasan Muralidharan <muralisr@us.ibm.com>
      61affa05
  8. 23 Nov, 2016 1 commit
    • Alessandro Sorniotti's avatar
      TX proposal/endorsement/validation flow (+MSP) · 16fa08e2
      Alessandro Sorniotti authored
      
      
      This change set contains a set of functions to generate a transaction (from
      proposal, endorsements and a signing identity) and validate it (given a set
      of root CAs). The validation code will be used by the committer. The tx
      assembling code should be helpful for the SDK team to understand how
      transactions should be assembled. Additionally, it has changed the type of
      messages exchanged everywhere to be of the proper type and with signatures
      (obtained from a fixed identity for now). Finally, it contains an initial
      implementation of VSCC with unit tests (which is however not yet called by
      the committer).
      
      Change-Id: I375ecc7e61516f3c4ab8fd874aa564e99cc720fb
      Signed-off-by: default avatarAlessandro Sorniotti <ale.linux@sopit.net>
      16fa08e2
  9. 15 Nov, 2016 1 commit
  10. 11 Nov, 2016 1 commit
  11. 01 Nov, 2016 1 commit
  12. 28 Oct, 2016 2 commits
  13. 26 Oct, 2016 1 commit
  14. 29 Sep, 2016 1 commit
  15. 15 Sep, 2016 1 commit