go chaincode now sets the Asset owner as client identity certificate string (instead of base64 str)
Reason for the update: "GetClientIdentity().GetID()" api in go chaincode returns base64 string, while same api in java chaincode returns the same data as string
go & java chaincode sets same owner string
updated js app verify method
Signed-off-by: Sijo Cherian <sijo@ibm.com>
Java chaincode that can be deployed via test-network, with shortname 'private'
Unit test for core transactions
Bugfix for QueryAsset txn function signature
Incorporated PR feedback
Signed-off-by: Sijo Cherian <sijo@ibm.com>
* commercial paper enhancements
Signed-off-by: Paul O'M <mahoney@uk.ibm.com>
* commercial paper enhancements
Signed-off-by: Paul O'M <mahoney@uk.ibm.com>
* commercial paper enhancements
Signed-off-by: Paul O'M <mahoney@uk.ibm.com>
* Add further README changes from #335
Signed-off-by: Paul O'M <mahoney@uk.ibm.com>
* Add further README changes from #335
Signed-off-by: Paul O'M <mahoney@uk.ibm.com>
* Add further README changes from #335
Signed-off-by: Paul O'M <mahoney@uk.ibm.com>
Update ERC-20 readme to indicate the new contract name
and add TransferFrom tutorial for Go chaincode.
Signed-off-by: David Enyeart <enyeart@us.ibm.com>
This PR changes the auction sample to a simple blind auction with just a
single item to be sold to the highest bidder.
Signed-off-by: Arnaud J Le Hors <lehors@us.ibm.com>
Added check to avoid double spent in token-utxo chaincode
In the transfer function it was possible to pass the same utxo more than once in the array of input utxos without any error. Making it possible to spend the same utxo more than once in the same transaction and like this create more tokens than minted. To fix this I changed the array that was used to store the input utxo states to a map and so utxos were stored in the map by there key, which made it possible to know if a key and so a utxo had already been used.
I tested this by setting up the test-network, deploying the token-utxo chaincode with my fix, minting a utxo and trying to spent this utxo more than once in the same transaction, which was not possible anymore. It can only be spent one time anymore with this fix.
Add new chaincode and javascript application to demostrate
the use of chaincode events and block events with private data.
Signed-off-by: Bret Harrison <beharrison@nc.rr.com>
This PR adds ERC20 capabilities to the token-account-based sample.
It includes javascript Chaincode and the updated README to explain
how to use tokens in the Fabric test-network.
Signed-off-by: Yuki Kondo <yuki.kondo.ob@hitachi.com>
The current scripts given to setup the user environment do not work
on Mac:
$ . ./magnetocorp.sh
-bash: cd: /Users/lehors/Projects/Go/src/github.com/hyperledger/fabric-samples/commercial-paper/organization/magnetocorp
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed./../../../test-network: No such file or directory
-bash: ./scripts/envVar.sh: No such file or directory
[...truncated...]
export FABRIC_CFG_PATH="/Users/lehors/Projects/Go/src/github.com/hyperledger/fabric-samples/commercial-paper/organization/magnetocorp"
export PATH="/Users/lehors/Projects/Go/src/github.com/hyperledger/fabric-samples/commercial-paper/organization/magnetocorp"
export PEER_PARMS=""
Saving session...
Saving session...
The session history related output is actually captured when setting the environment variables:
$ echo $FABRIC_CFG_PATH
/Users/lehors/Projects/Go/src/github.com/hyperledger/fabric-samples/commercial-paper/organization/magnetocorp
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed./../../../config
With this simple change the scripts work:
$ echo $FABRIC_CFG_PATH
/Users/lehors/Projects/Go/src/github.com/hyperledger/fabric-samples/commercial-paper/organization/magnetocorp/../../../config
Signed-off-by: Arnaud J Le Hors <lehors@us.ibm.com>
The user's PATH must be set on the first use of Terminal 2 for the
call to the fabric-ca-client command to succeed. The current README
only sets it later. This fix changes that.
Signed-off-by: Arnaud J Le Hors <lehors@us.ibm.com>
The user's PATH must be set on the first use of Terminal 2 for the
call to the fabric-ca-client command to succeed. The current README
only sets it later. This fix changes that.
Signed-off-by: Arnaud J Le Hors <lehors@us.ibm.com>
