[Feature Request]: DecenTrade lacks a secure backend; currently, the frontend directly interacts with IPFS

[AmanSingh494]

Is there an existing issue for this?

• [X] I have searched the existing issues

Feature Description

Currently, DecenTrade relies on the frontend to interact with IPFS directly, which raises significant security concerns. Exposing IPFS requests through the frontend can potentially lead to vulnerabilities, such as unauthorized access to IPFS data or manipulation of requests. After Integrating a database, a secure backend would be needed to manage requests and functionalities.

Use Case

1. Interactions with IPFS
2. Interactions with Database

Benefits

• Safely process and validate requests to IPFS before forwarding them.
• Manage communication with the database to ensure data integrity and security.
• Provide secure endpoints for the frontend to interact with, reducing exposure of sensitive data and operations.
• Improve overall security by centralizing logic that interacts with both the IPFS and the database.

Priority

High

Record

• [X] I agree to follow this project's Code of Conduct
• [X] I'm a WOB contributor
• [X] I want to work on this issue
• [X] I'm willing to provide further clarification or assistance if needed.

[AmanSingh494]

I request @4darsh-Dev to assign this issue to me!!

[4darsh-Dev]

assignd to you @AmanSingh494 , you have do the setup for backend .

changes to be done

1. make a separate folder /backend in the root
2. add .env variables as done in frontend and one .env.example to avoid errors.
3. ethereum.js which is present in frontend should be setup in backend
4. use json web token for secure authentication