🦧
Profile.io User Docs
  • Introduction
    • What is Profile.io?
    • Profile Product Roadmap
    • Design Direction
    • Motivation & Values
    • SSI Basics & Concepts
    • Profile.io
    • Profile.io Technical Docs
  • System Overview
    • Profile.io Architecture
      • User Profile ID Data
      • Profile Structure
      • Themes
      • Issuer (Organisation) ID
      • Badges (VCs SB NFTs)
      • Data Registries
        • Schema Registry
        • Trusted Registry
        • DID Registry
    • Profile Verification
    • P2P Payments
    • App/Dapp Marketplace
    • Account Abstraction
    • Social / Content Growth Vectors
    • Decentralisation, OpenSource Overview and Compatability
    • Proof of Personhood (POP) Algorithm
  • Profile Implementation
    • Current live platform status
    • User Flows
    • Use Cases
    • About / Contact
    • External Resources
      • Developer Documentation
Powered by GitBook
On this page
  1. System Overview
  2. Profile.io Architecture

Badges (VCs SB NFTs)

PreviousIssuer (Organisation) IDNextData Registries

Last updated 1 year ago

Badges denote a users verified credentials and can have various underlying verifiable technologies such as SSI VCs, soulbound nfts and others as they emerge. Programability provides dapp/app use cases beyond verification

Badges are initially issued by other users and orgs.

In future, a play to earn marketplace may be introduced with training / certification partners.

Badge Example, Profile embedding and associated org Farcaster app/dapp

Badge Thesis

Badges are verifiable and programmable.

Badges are Verifiable Credentials that are attached to a user's Profile ID, that are issued to them by Issuers (Organisations). The details contained within the Badge are stored privately off-chain, and it is entirely at the user's discretion whether they want to make it public.

Profile.io initial central design will focus on real world user achievements such as academic and skill credentials, club membership and work/career. In general badges are bound to a user and non-transferable other than from issuer to user. While third party badges may enter the ecosystem, user to user transferability may be an issue to overcome given transfer can break down the trust framework (eg POAPs have genuine utility in our ecosystem but are technically transferable so may not reflect a user's actual achievement/credential). The focus is not on amassing NFT art in your profile or various crypto tokens. However, as are open source, the developer community may choose to give users the option for this in third party apps/dapps or potentially even a parallel core profile network.

Standardised for different badge types is under development and will be subject to policy with ability for issuers to influence policy. Schema will assist programatic interface of developer for the .

Badges are ZK enabled - particularly relevant to for ZK app access authentication.

All users to receive onboarding badges as progress towards - unlocking incentives such as access to verified user P2P payment dapp.

user profiles
App/Dapp marketplace
proof of personhood
dapp/app
marketplace
Badge treatment
Badge treatment in Profile
Organisation apps/dapps unlocked for badge holder
Gated Farcaster Alumni Community from out the box app/daps
Public / Private Badges -- Pending Verification / Verified Credential Treatments
Schema