CAPS

Inspiration

We are used to the fact that each user in the blockchain is nothing but an anonymous account, but if you want to be a part of society or some community you should have an identity to be recognizable. In the web2 world, users can create their pages and use them only inside a platform that was used for creation. But how can it be handled in the web3 space with decentralization and platform independence?

Some apps allow you to create a web3 profile page. But all of them are nothing more than pages with links to web2 social networks. So the utility of such apps tends to be zero.

What it does

We’ve built a bunch of tools that will allow you to create a truly decentralized identity.

Cross-App Profile System (CAPS) is the base of the ecosystem for the decentralized society. There are:

• CAPS dApp - UI that helps to deploy profiles
• CAPS JS SDK - A library for integration with CAPS
• CAPS Browser Extension - A helper app that helps to use profiles outside of the CAPS dApp

We reimagined the concept of soulbound tokens and now you can collect real achievements in your profile. It can be gaming achievement, course certificates, work experience, or proof of some event attendance, whatever you want. These achievements are minted by another profile or third-party app. And everyone can see them. The utility of such tokens rests on the shoulders of their creators.

See how it works in the demo video!

How we built it

The frontend and browser extension was built using TypeScript and React and do the work of interacting with the Near API, using the Near-API-JS library.

Smart contracts were written with the Near Rust SDK. All external data is stored on Arweave.

We also have a tiny back-end service for importing data from Twitter and GitHub and publishing data to Arweave. It was written in Go.

What we learned

We dived into the NEAR ecosystem and got a new experience. Prior to this hackathon, our team had experience with blockchains such as Tezos, Ethereum, TON, and Solana, so the transition to NEAR went smoothly for us, especially due to the friendliness of the NEAR ecosystem.

Accomplishments that we're proud of

Our main achievement is the well-coordinated work of the team. We tried several ideas, changed the development vector several times, and in the end, we chose a project with a clear development vision that we believe in.

What's next for CAPS

We are going to continue to improve the CAPS ecosystem and build a community of users and developers around it. We also have some plans for a CAPS based teamwork platform.

Built With

• arweave
• go
• near
• react
• rust
• typescript