Tulip

💙 Introduction

Welcome to Tulip: The first platform that leverages the DeSo blockchain to bring charities and social media together. The removes the need for any website to donate and connect with causes you care about.

💡 Inspiration

People Have donated over $450B dollars in just the last year. A lot of these charities have some service as middlemen that take a cut off the donation in return for hosting the charity on their platform.

This often includes a multistep process and it is not engaging or interactive. So, we wanted to build a solution where charities and social media are more connected, so people are more inclined to donate and it makes it a more fun experience. Most importantly, there are no middlemen and all funds are transparent in the DeSo blockchain, so no cut for any companies!

⚙ What it does

Explore, Follow and Track the progress of local fundraisers, NPOs, charities, and rallies through the posts they release.
Give them some Tulip as a token of your support, or buy their NFTs to help them reach their goal, all while showcasing your contribution.
"Invest" in the charity by buying their creator coin that reflects the impact and value they bring to our community.
All proceeds are transferred to the charity's blockchain wallet without the need for any service from their side or a middle man.
Comment and like content that speaks the most with you.

🔧 How we built it

We first followed the DeSo Repos in order to set up a local node.
Deployed an E2 instance on GCP Compute Engine to mine the local blockchain.
Frontend was written in React js and styled with chakra UI

📌 Accomplishments that we're proud of

Setting up and running the local node, since it was a huge task
Using gcloud cli to compute ssh on local machine for testing
Managing to make a backend change to the repo in order to customize the feed

💪 Challenges and What we learned

None of our computers were able to run the local node, so that came as a huge surprise since we can run local ethereum block-chain without an issue. The biggest setback was figuring out how to make the backend change since the repo was very new to us and also managing access through the identity service.