📖
ZeroAuthority Docs
  • Welcome to the Zero Authority Docs!
  • The Dao
    • Vision and Values
    • Meet the core team
    • How to contribute to the DAO
    • How to reward contributions
    • Zero Authority Solutions
      • Bounty Onchain
        • Create a bounty on v2 beta
        • How to create a bounty
        • How do I select a winner
        • Selecting Winner the Bounty
        • Bounty Ideas for Community-Centered Engagement
      • Gigs Onchain
        • Gigs on v2 beta
        • How To Offer or Accept Gig Onchain
      • Milestone Gigs Onchain
      • Overview of Email Notification
      • Reputation Onchain
      • Nova
        • 🔹 Bot Commands
        • 🔹 Token Distribution Index
        • 🔹 Try Telegram Bot
        • 🔹 Try Discord Bot
        • 🔹 Setup the Tracker Bot
        • 🔹 Setup the Stacks Tokens Bot
        • 🔹 Setup the Runes Bot
        • 🔹 Setup the NFT Bot
        • 🔸 Premium Benefits
        • 🔸 Setup Premium telegram or discord
        • 🔸 Setup Premium Notifications
    • Tokenomics
    • Product Roadmap
      • Road Map Overview
        • Roadmap Detailed
      • The Gig Marketplace
      • Bounty
      • Expertia Release
      • SmartTrail
    • Updates
      • Zero Authority V2 on Testnet
      • Zero Authority V2
      • MFA for All Access Points
      • v.1.0.0 Bounty Onchain
      • v.1.5.2 Gig Mkpl update
      • v.1.5.1 Gig Mkpl update
      • v.1.5.0 Gig Mkpl update
      • v.1.4.0 Gig Mkpl update
      • v.1.3.1 Gig Mkpl Bug Fix
      • v.1.3.0 Gig Mkpl
      • v.1.2.0 Gig Mkpl update
      • v.1.1.0 Gig Mkpl update
      • v.1.0.2 Gig Mkpl Bug Fix
      • v.1.0.1 Gig Mkpl update
      • v.1.0.0 Gig Mkpl on mainnet 🎉
      • Testnet 1.4 update
      • Testnet 1.3 update
      • Testnet 1.2 update
      • Testnet 1.1 update
      • Testnet 1.0 update
      • Target Launch Date
    • Standard Reputation Framework
      • 15 Common Categories
      • Clarity & JSON Implementation
      • Clarity Contract
      • JSON Metadata
    • Access to the Platform
    • Investors & Stakeholders
      • December 2024
Powered by GitBook
On this page
  • Clarity
  • JSON
  1. The Dao
  2. Standard Reputation Framework

Clarity & JSON Implementation

Previous15 Common CategoriesNextClarity Contract

Last updated 7 months ago

To create a Reputation (REP) badge using Clarity and JSON, you need to manage onchain logic with Clarity and define metadata with JSON.

Clarity

The Clarity contract facilitates batch endorsements, allowing authorized users to issue badges to multiple recipients. It verifies the issuer's authority and manages the process of adding badges (endorsements) to users' profiles. Key functions include add-badge (adds a badge to a user) and endorse (issues badges to multiple users at once).

JSON

The JSON metadata defines the badge's attributes, such as its name, description, image, and criteria. It helps visually represent the badge and provides context, like the number of events engaged in or the date issued.

Example structure:

{
  "name": "Community Engagement Badge",
  "description": "Awarded for actively engaging in community events.",
  "image": "https://example.com/badges/community-engagement.png",
  "attributes": [{"trait_type": "Engagement", "value": "5 events"}]
}

Together, Clarity handles issuing the badge, and JSON defines its visual and contextual properties.

Clarity Contract
JSON Metadata