soji | Devpost

Soji front end

Inspiration

Sending images and gif's online via discord is fun. Sending audio in discord is also fun. However you can't search for pre-existing audio clips on discord. We want to marry the two, this marriage is called Soji (sound + emoji) . We also don't want our soji's to be removed because someone doesn't like our soji's so we want to store them on IPFS.

What it does

A user can upload a small mp4 or image with a sound to create a soji. The Soji platform then stores the soji to IPFS which can then be used in discord or other messaging apps.

How we built it

Non Technical: We built SOJI using standard agile SDLC approach, using GITHUB and discord to manage our development cycle. Front-Technical: We built this using react type script, web3uikit, mui, morales and js-ipfs. Backend-Technical: Using hard hat, some chain link functions and openzeppelin

Challenges we ran into

Understanding how the back end actually is peiced together and how to mint tokents. Please note that this project is still not 100% complete we still need to implement the minting process and run complete test cases for minting.

Accomplishments that we're proud of

Proud of developing a proof of concept for a front end and backend. We are proud about learning about how react typescript interacts with the etherum blockchain.

What we learned

How Etherum, IPFS and Chainlink all interact with each other and that. Getting started with with writing ETH contracts is not as scary as we thought it was. I also found out how important IPFS and chainlink are to not just etherum but to the whole cryptocurreny echosystem.

What's next for soji

Write test cases for the front end and back end.
Complete and finish up the rest of the Soji backend contracts.
Implement a reward system. Maybe some sort of PROOF OF MINTING where the network is supported by an internal token.
Push the contract to a live Network.
Create Discord and Status.io, embedable intergrations