SoL-verse
From Work to Worth, Instantly
The problem SoL-verse solves
The Problem It Solves
We’re all told to “be visible”, post your GitHub links, share updates on Twitter, contribute to DAOs.
But here’s the problem:
- Your work ends up scattered across 5 different platforms
- You rarely get any real recognition, or it feels like shouting into the void
- People can fake credentials or game the system
- And worst of all, there’s no single place where your real contributions actually count
So the ones doing real work often get overlooked. That sucks.
How Solverse Helps
Solverse gives your hard work a home.
- You submit proof of what you’ve done (like a GitHub PR or community help)
- Other people in the community verify it, and they stake a tiny bit of crypto to do so
- Once verified, you earn a Soulbound Token, your personal, on-chain proof of reputation
- And if you’re helping verify others? You get rewarded too
- Your trust score builds up, unlocking access to jobs, voting rights in DAOs, or even skipping KYC
In short, Solverse makes your contributions visible, valuable, and verified.
It’s your Web3 resume, backed by real people, not just hearts, likes, or fake reviews.
Challenges we ran into
Challenges We Ran Into
Building Solverse was both exciting and challenging for our team. While the core idea felt powerful, turning it into a functional product required navigating several technical and conceptual hurdles. Here are the key challenges we faced and how we tackled them together:
Designing Fair Verification Logic
One of our main goals was to build a reputation system where trust can’t be gamed. We didn’t want to recreate the problems of social media where anyone can endorse anyone with zero accountability. The challenge was: how do we ensure that verifiers are honest and have skin in the game?
We solved this by introducing staked peer verification. Verifiers had to stake a small amount of AVAX to approve someone’s contribution. If they verified something that turned out to be fake, their stake would be slashed. This aligned incentives and made the process more credible.
Integrating Civic Auth
We wanted to give users the option to verify their real-world identity in a privacy-preserving way. Civic Auth was a great fit for this, but integrating it into our Web3-first Next.js app wasn’t straightforward.
We had to spend time understanding Civic’s JWT flow and how to connect off-chain identity data with wallet addresses. After exploring the documentation and reaching out to the community, we successfully added Civic Auth to the flow, adding a valuable layer of trust and utility.
Through these challenges, we learned a lot not just about building with Web3 tools, but also about designing systems that balance incentives, trust, and simplicity. We’re proud of what we’ve built and excited to keep growing Solverse.
Tracks Applied (1)
Authenticate with Civic Auth
Civic Technologies
Technologies used