The problem NFTgram solves

The art market, which saw more than $50 billion in sales last year, remains a largely unregulated field. This lack of regulation is perpetuated by the art world’s entrenched lack of transparency. NFT's are a good force in the Art Market. Each NFT-based digital creation now contains a digital signature from the artist and all vital details including time of creation, edition size, and a record of any prior sales permanently attached to the artwork. all artists got resale royalties, not only NFT artists. Additionally, all artists would know, at any given time, who owned their work and how much it had sold for, bringing an unprecedented level of transparency to the art world—one that would help bring artists from the periphery of knowledge access closer to the center. Future doesn’t address all the issues. There is still a lot of work to do in both the NFT and traditional art worlds to make them more inclusive and greener. Also, such a future would likely create new gatekeeping problems, especially for artists, collectors, and dealers less familiar or comfortable with the technology.

Challenges we ran into

• Installing appropriate dependencies is mandatory.
  Also, deployment of our smart contract in a real working network like Ethereum wasn't possible.
  Made use of Polygon Faucet to have MATIC but it took too much time to load and didn't sustain for a long period.
  We attempted to deploy it using Polygon Mainnet but due to no/insufficient funds, that was an obstacle

(THE ERROR: reason: 'insufficient funds for intrinsic transaction cost',
code: 'INSUFFICIENT_FUNDS',
error: ProviderError: insufficient funds for gas * price + value
at HttpProvider.request (C:\Users\Vaibhavi\Desktop\nft-marketplace\nft-
method: 'sendTransaction',
transaction: undefined.)

Also, we tried using Infura, an Ethereum API but they limited our choice only to select the Mainnet and the rest of the networks, the Polygon Mumbai Testnet and Polygon Mainnet were like an add-on(required charges).

However, the deployment of our web3 app on our localhost:3000 was indeed a success.

• We did encounter some commit conflicts which we are sure no one really loves solving. So after a few setbacks, we started using Github workflow as efficiently as we could and collaborated on GitHub asynchronously throughout the project.