The problem STKR solves

STKR, the innovative social identity application for Web 3.0, offers users a unique platform upon registration—an individualized "stkr wall." This wall serves as a dynamic canvas for users to showcase their digital NFT-based badges, or "stkrs," which can represent a myriad of aspects in their personal and professional lives. These stkrs may range from highlighting one's expertise, affiliations, and passions to more whimsical and creative expressions of their interests.

The concept of stkrs goes beyond mere digital decoration; it is deeply intertwined with the principles of decentralization and trust within the Web 3.0 ecosystem. The process of minting stkrs is facilitated through organizations that have received approval from the stkr DAO (Decentralized Autonomous Organization). This approval process ensures that organizations issuing stkrs are legitimate, accountable, and aligned with the principles of the platform.

Let's delve into the key components of this innovative system:

Stkr Walls: Upon signing up, each user is allocated a personal "stkr wall." This wall serves as a dynamic canvas where users can display their collection of stkrs. These stkrs function as visual representations of the user's identity and affiliations.

NFT-Based Stkrs: Stkrs are NFTs (Non-Fungible Tokens) that hold unique and provable characteristics. They can be created and traded on the blockchain, ensuring the rarity and authenticity of each stkr. Users have the flexibility to create or acquire stkrs that best represent their identity.

Versatility of Stkrs: The versatility of stkrs is one of their standout features. Users can choose to use stkrs to convey their professional experience, affiliations with communities, or even their hobbies and interests. For instance, a user might have stkrs that represent their roles in various professional organizations, their expertise in specific fields, or their engagement in charitable activities.

Challenges I ran into

We encountered technical challenges primarily on the backend side, writing canisters in Motoko. None of us had experience with Motoko, and there did not exist many Stack Overflow answers to help us with our frustrations. We spent a lot of time reading the documentation for Motoko, and sometimes had to take a peek into the implementation of certain data structures because the documentation was not fully comprehensive. It was quite rewarding to work on something like this, however; it tested our problem solving skills and gave us a challenge. We spent more time than normal solving trivial bugs, but we have gained a stronger understanding of Motoko as a result. We are incredibly excited to continue building with it, and have enjoyed using the language!