hyperledger-labs / nft-auction

NFT Auction application lets user to create NFTs and auction them off to other users in a marketplace model using Hyperledger Fabric

NOTE: This lab has been archived and is no longer being maintained.

nft-auction

NFT Auction application lets user to create NFTs and auction them off to other users in a marketplace model using Hyperledger Fabric.

Scope of Lab

This lab uses Hyperledger Fabric as the underlying ledger technology to create an auction market. This helps the developer to vizualize how the NFT concept can be extended to private blockchains like Hyperledger Fabric. The application uses Hyperledger Fabric 2.X version in its current form.

Initial Committers

• https://github.com/sahinul-haque
• https://github.com/DilipManjunatha

Setup

Please read SETUP

nft-auction's Issues

Chaincode definition approved on peer0.org1 on channel 'defaultchannel' failed

I got the Error on Ubuntu 20.04, when start ./start.sh in auction-restapi/network/local. (the dependencies are ready)

Chaincode definition approved on peer0.org1 on channel 'defaultchannel' failed

Before that I got the log: Error: The required parameter 'sequence' is empty. Rerun the command with --sequence flag

Create a MAINTAINERS.md file

Example: https://github.com/hyperledger-labs/solang/blob/main/MAINTAINERS.md Example of a pointer: https://github.com/hyperledger-labs/homebrew-solang/blob/main/MAINTAINERS.md

Uploading artwork fails on Mac

Uploading an art image through the web app crashes the nodejs server.

[2022-04-01T11:08:19.692] [INFO] invoke-chaincode - Transaction successfully submitted at 2022-04-01T15:08:19.692Z
dyld: lazy symbol binding failed: Symbol not found: __ZN2v87Isolate37AdjustAmountOfExternalAllocatedMemoryEx
  Referenced from: /Users/jjs/nft-auction/nft-auction/auction-restapi/node_modules/images/vendor/darwin-x64-binding.node
  Expected in: flat namespace

dyld: Symbol not found: __ZN2v87Isolate37AdjustAmountOfExternalAllocatedMemoryEx
  Referenced from: /Users/jjs/nft-auction/nft-auction/auction-restapi/node_modules/images/vendor/darwin-x64-binding.node
  Expected in: flat namespace

sh: line 1: 34714 Abort trap: 6           node app.js
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! [email protected] start: `cd node && node app.js`
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/jjs/.npm/_logs/2022-04-01T15_08_19_704Z-debug.log

I successfully set up the components of this project on my Mac running Big Sur using nvm and selecting node version 14.

If I restart the server after the crash, the artwork image is the watermark only:

Anyone with ideas?

chaincode definition on peer0.org1 on channel 'defaultchannel' failed (LINUX)

Hey there,

I've been trying to deploy the auction app on my Ubuntu and made sure that all dependencies are up to date. However, I keep receiving this error. I would appreciate it if you could point me in the right direction to get this fixed.

~/Documents/nft/nft-auction/auction-restapi/network/local
Finished vendoring Go dependencies
Error: error getting chaincode bytes: listing deps for package ../../../auction-chaincode/src/goauction failed: exit status 2
Chaincode packaging has failed
Deploying chaincode failed
deploying chaincode on channel 'defaultchannel'
executing with the following

• CHANNEL_NAME: defaultchannel
• CC_NAME: auctionchaincode
• CC_SRC_PATH: ../../../auction-chaincode/src/goauction
• CC_SRC_LANGUAGE: go
• CC_VERSION: 1.0
• CC_SEQUENCE: 1
• CC_END_POLICY: NA
• CC_COLL_CONFIG: NA
• CC_INIT_FCN: Init
• DELAY: 3
• MAX_RETRY: 5
• VERBOSE: false
• CC_SKIP_PACKAGE_INSTALL: true
• CC_SKIP_DEPLOYMENT false
  Vendoring Go dependencies at ../../../auction-chaincode/src/goauction
  ~/Documents/nft/nft-auction/auction-chaincode/src/goauction ~/Documents/nft/nft-auction/auction-restapi/network/local
  go: unknown subcommand "mod"
  Run 'go help' for usage.
  go: unknown subcommand "mod"
  Run 'go help' for usage.
  go: unknown subcommand "mod"
  Run 'go help' for usage.
  ~/Documents/nft/nft-auction/auction-restapi/network/local
  Finished vendoring Go dependencies
  Skipping Chaincode packaging and installing...
  Using organization org1
  Installed chaincodes on peer:
  Query installed successful on peer0.org1 on channel
  Using organization org1
  Error: The required parameter 'sequence' is empty. Rerun the command with --sequence flag
  Usage:
  peer lifecycle chaincode approveformyorg [flags]

Flags:
--channel-config-policy string The endorsement policy associated to this chaincode specified as a channel config policy reference
-C, --channelID string The channel on which this command should be executed
--collections-config string The fully qualified path to the collection JSON file including the file name
--connectionProfile string The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information
-E, --endorsement-plugin string The name of the endorsement plugin to be used for this chaincode
-h, --help help for approveformyorg
--init-required Whether the chaincode requires invoking 'init'
-n, --name string Name of the chaincode
--package-id string The identifier of the chaincode install package
--peerAddresses stringArray The addresses of the peers to connect to
--sequence int The sequence number of the chaincode definition for the channel
--signature-policy string The endorsement policy associated to this chaincode specified as a signature policy
--tlsRootCertFiles stringArray If TLS is enabled, the paths to the TLS root cert files of the peers to connect to. The order and number of certs specified should match the --peerAddresses flag
-V, --validation-plugin string The name of the validation plugin to be used for this chaincode
-v, --version string Version of the chaincode
--waitForEvent Whether to wait for the event from each peer's deliver filtered service signifying that the transaction has been committed successfully (default true)
--waitForEventTimeout duration Time to wait for the event from each peer's deliver filtered service signifying that the 'invoke' transaction has been committed successfully (default 30s)

Global Flags:
--cafile string Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
--certfile string Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
--clientauth Use mutual TLS when communicating with the orderer endpoint
--connTimeout duration Timeout for client to connect (default 3s)
--keyfile string Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
-o, --orderer string Ordering service endpoint
--ordererTLSHostnameOverride string The hostname override to use when validating the TLS connection to the orderer
--tls Use TLS when communicating with the orderer endpoint
--tlsHandshakeTimeShift duration The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint

Chaincode definition approved on peer0.org1 on channel 'defaultchannel' failed
Deploying chaincode failed