Hackathon tracks
- Future of work – edu tech on blockchain; job market solutions for Web3 professionals and beyond
- Technical content – tooling, documentation and tutorials
Who we are
- Adam Turczi - Project lead and full stack web3 developer at Antisocial Labs
- Titusz Ban - Co-founder and CTO at Antisocial Labs
Inspiration
Soulbound Tokens are the next revolutionary Web3 Primitive. We have been working on the launch of Show Protocol for the past few months and we wanted to demonstrate its use through a practical, directly applicable example. We have had a lot of interest for the application of Soulbound Tokens in recruitment, and so decided to build a proof of concept talent marketplace built to empower those with skills to offer.
What it does
talent.sbt is a talent platform, where users can combine their Soulbound Tokens representing proofs of skill, educational qualifications and work experience, all verified by trusted 3rd parties, and publicly list this set of tokens as their CV, which others can view if they are willing to pay. Due to the privacy-first aspect of the protocol, although the source of the tokens is public, their content is not. As a result, those who are looking to hire qualified candidates want to access the underlying data to view the CV, and can browse a variety of listings, can place an offer, paying at least the minimum price (although they can chose to pay more). If the talent accepts the offer, they grant permissions, which the marketplace verifies, and if it is valid, releases the funds.
How we built it
We have built the marketplace as a Rust smart contract on NEAR testnet. We have also built an oracle for verifying user keys (which NEAR cannot do due to its sharded nature), using a Rust smart contract and a Python agent.
Additionally, we have forked the ReactJS developer dashboard for Show Protocol and added new pages for interacting with SBT marketplaces. It supports listing tokens, viewing listings, making offers and accepting these offer thus granting access. The existing dashboard can then be used to access the token content.
Challenges we ran into
The verification of all tokens through a series of cross-contract calls have ended up being more challenging than expected, and were descoped in the interest of time. It has also highlighted a potential improvement in the protocol to allow batch lookups on relevant token information, reducing gas costs and complexity.
Accomplishments that we're proud of
The amazing thing about being in person here at NEARCON, is getting immediate and relevant feedback from key echosystem players. We were able to partner and get commitments from ShowCode (an already established web2 recruitment platform) and BEExperience (the most important recruitment platform on NEAR) to provide talent.sbt and the Show Protocol as the underlying technology for their on-chain talent solutions.
What we learned
Hackathons are always a great opportunity to learn and experiment with new things. This was the first time we have built an oracle to support capabilities not possible with the protocol layer of NEAR. We have also learned new things in Rust (like finding that there is a .filter on .iters). Also, we have had quite a few useful ideas on what features the Show Protocol still needs to enhance user experience; like having a method for verifying if someone has accessed a token, which can be a condition to releasing the funds, to prevent the user from claiming the payment and revoking the permissions immediately.
What's next for talent.sbt
We intend to pursue the partnerships formed during NEARCON, enhancing the marketplace to fit the need of our partners, and have it ready for a mainnet launch. We are also committed to working further on the Show Protocol, supporting a thriving echosystem of SBTs on NEAR and beyond, bringing privacy-first identity to Web3.
Try it out
Our forked dashboard is live here: https://talent-sbt.web.app/
You can use the existing example SBT contract: ref-sbt.v001.sbt.testnet and the talent marketplace contract for permissions: dev-1663114678647-73704553949839
Log in or sign up for Devpost to join the conversation.