The problem SkillBased solves

Today’s social networks are centralized, limiting user ownership, transparency, and data portability. Users have little to no control over their identities and content, and professional networks often fail to verify or authenticate credentials and skills in a trustworthy way. These platforms often monetize user activity without sharing value with the creators, and suffer from issues like censorship, opaque algorithms, and lack of interoperability.

Our application solves these issues by creating a decentralized, onchain professional social network built on the Base ecosystem. Users can post, like, and comment, while their profiles are enriched through integration with Basenames, bringing verified avatars and social handles.

A key innovation is our onchain credential system, where users can list skills and achievements, and others can endorse them directly onchain, creating a verifiable, trustless reputation layer. We also integrate with Talent Protocol to surface relevant user data and career insights, enhancing the professional context.

By putting identity and reputation in the hands of users, we empower professionals to build a portable, provable profile that evolves with their contributions—something no traditional network can offer.

Challenges we ran into

There were several challenges we had to overcome while developing our application, some simple, and others that took us days to solve. These are the ones that we consider the most important and that brought us the most learning:

• Onchainkit: The onchainkit library was quite easy to use, provides a great development experience and simplifies the implementation of many features that would otherwise take many lines of code to implement. However, we found some unexpected things, such as basenames not displaying correctly (showing the address instead of the basename), and the Socials component not displaying anything. We thought it was something we were configuring wrong, and after hours of checking, we decided to ask for help in the Discord channel. They answered us quite fast, and reviewed the case. It turns out that it was a bug in the library, and because of that the basenames and socials were not being displayed correctly. The first bug was fixed by the Base team in a matter of hours, while the second one took a little more than a week and a half. Now it works correctly, thanks to the Base team that was super responsive.