mlh-fellowship / cryptodrive Goto Github PK

Update the documentation on

• Project outcome
• tech Stack
• Progress
• Challenges
• Learnings

CryptoDrive needs a greeting bot, whenever a contributor, raises their first issue or sends their first PR.
If you would like to contribute, feel free to create a branch and send a pr to staging.

Need to Add a Boiler Plate for Smart Contracts and write a smart contract to store the file hashes and filenames uploaded by a particular folder.

Make a beautiful Landing page, and revamp the theme of the app.

While we upload a file it sends a request to pay the gas fee to store the user details and then upload details but if the user clicks on reject then it should be handled so for that we need to handle an alert to state please try again and stating a proper reason.

There are lot of edge cases involved in the application. Few of them are.

• Private Key Incorrect. (During SignUp, SignIn, MyFiles, Shared Files)
• Metamask not Found
• Private Key Extension Incorrect.
• User Already Exists (During SignUp)
• User Doesn't Exist (During File Sharing)

We need to create a function that actually generates a private and public key once a new user joins or signup

You can refer to this link to fix the typo
https://github.com/MLH-Fellowship/CryptoDrive/blob/3818aa78a0d68503b81f016c2dec63f3c38a5e9d/src/pages/Landing/src/components/sections/FeaturesSplit.js

Adding a new feature for sharing files via sender to receiver and storing them in the smart contract as a mapping.

Try to deploy the client on Dfinity.

I will be using the pretty naive approach to build Dark Mode, via CSS and bit JavaScript.
In this approach wherever you want to put a dark mode component, you need to add an id=theme to that component.

This is just hacky stuff.

If the user uploads an empty file then it should stop the upload and send an alert to the user stating that the uploaded file is empty.

We are following best practices in our code.
But we do need comments in some parts to let other contributors understand what we are doing.

Encryption and Decryption Modules in client-side need to be added

Setup a basic server to upload a file using multer and IPFS

Currently, CryptoDrive is not yet prepared for Mobile Devices.
Making it prepared for mobile devices, will be helpful for users to upload and share files via their mobo device.

It helps in optimizing the build files and make the file structure clean by importing from required modules

Need to code the tests for smart contracts and create some custom checks.

For using better coding practices I want to implement the CI for the project.

Need to Deploy the smart contracts in Testnet like RinkeBY and make changes to configure file

probably the usenamne should be username

Need to write web3 integration for accessing the smart contract from the client-side for storing the file hash when a person upload the files to ipfs

We need to have a project initial startup code so that it will be much easier to structure the code.

Hi, I am working on a similar project but I need to run this project and see how it's working. I downloaded the project and did npm install but nothing happens when I click on signup. can you please guide me how to run this project.

Custom Tests with truffle tests for sharing files in local blockchain before deployment need to be performed

IPFS integration to store the encrypted data is need to be added and need to retrive that

Integrate IPFS with client-side and revamp upload UI

A contributing guide is helpful for people who would like contribute to the project and it helps them setup their dev environment and get started.

The project uses Huffman Compression Algorithm, to process faster communication.
We are looking to improve on it further.

If you have any ideas, feel free to comment it.

Need to create the smart contract functions for Storing the PassHash and Public Key.

Build and Integrate Authentication UI.

When we are logging t the website it gets crashed and following error is coming on screen

We make sure, you really own your own data.
But as a service, people can misuse it by uploading spam script-based files.

A strategy has to be derived in order to work on the same.

Web3 should identify the current web provider and need to connect to the metamask and then need to load the contract hosted somewhere with the help of the ABI and Address. It would be much better if we could do it in separate modules

Currently, if you want to share an already shared file on CryptoDrive, it needs to be first downloaded by user, and uploaded and then shared. This is bad UX.

The following feature will help to overcome this.

Implementing Share feature, on Shared Files Section.
This will enrich UX and avoid unnecessary heads on user

MDN has a particular list of Malicious File Types.
Creating a checker function, which gets the extension of the file and checks, whether it is a malicious or nonmalicious file.
If malicious, the user will be popped up on an alert screen, asking, whether he is sure, to download it or not.

Need to handle an edge case where a user doesn't have sufficient amount of the ethers in the Metamask wallet then we need to stop the process and send the alert stating that the ether wallet balance is insufficient.

We need to display my files from smart contract to the dash board.

We have the smart contracts built for Sharing Files.
It's time to deploy them.
Along with that, writing functions in Web3 to interact with the contracts

Crypto drive runs on zero servers.
Hence the computation process does need to be parallelly processed for larger files.
Web workers is a great idea to implement parallel processing on client side.

• Add Decryption to incoming file from IPFS
• Improve IPFS upload strategy by using compression