The problem ChainIn solves

The Web2 version of LinkedIn we have today contains several critical concerns:

1. User Privacy - Users have to provide extensive personal information for e.g. in order to "complete" setting up a user profile, the user has to add in their birthday, which is completely unnecessary.
2. Authenticity - LinkedIn struggles with fake profiles and inflated credentials, impacting trust and authenticity when viewing a user's profile, for e.g. users can easily endorse each other, leading to inflated profiles.
3. Inconsistency - Job application process has also been criticized for its inconsistency, causing a cumbersome experience for users seeking to apply for positions.

Challenges I ran into

• Team Dynamics: We had to rework our team and find a new member mid-hackathon due to the inactivity and lack of participation of our previous front-end developer.

• Team Constraints: Team of 3, each with full-time jobs, dedicating weekends and nights. We had to carefully plan for MVP and sacrifice certain requirements deemed secondary.

• Tableland Bug Fixes: Occasionally had to turn to Dan for help regarding bugs that I was facing with Tableland Studio. One of the best DevRels out there as he helped me solve the bugs that I was facing within the same day.