BitBadges
Ctrlk
  • Overview
    • πŸ‘‹BitBadges Overview
    • 🎨Use Cases
    • πŸͺ™BADGE
    • πŸ”—Official Links and Resources
    • 🀝Brand Guidelines
  • πŸ—οΈToken Standard
    • πŸ“šOverview
    • πŸ“”Pre-Readings
    • πŸͺ„The BitBadges Standard
    • πŸ‘€Multi-Chain Accounts
    • 🧠Concepts
    • πŸ“¨Messages
    • πŸ”Queries
    • ⌨️Type Definitions
    • πŸ’‘Examples and Snippets
    • πŸ“‘Events
    • ❓FAQ
    • ⛓️Integrate The Standard?
    • πŸ™Source Code
  • ⌨️For Developers
    • πŸ”¨Getting Started
    • πŸ“šBitBadges API
    • βš’οΈBitBadges JS / SDK
    • ⛓️BitBadges Blockchain
    • 🎁BitBadges Claims
      • Overview
      • Concepts
        • Standard vs On-Demand
        • Completion Methods
        • Gating On-Chain Approvals
        • Claim Numbers
        • Success Logic
        • Signed In vs Select Address
        • Universal Approach - Claim Codes
        • Identify By Socials / Emails?
      • Checking Custom Criteria
      • Implementing Custom Utility
      • Leveraging AI
      • BitBadges API & Claims
      • Dynamic Stores
      • Custom Plugins / Webhooks
      • Integrate with Zapier
      • Integrate with Pipedream
      • In-Site Plugins
      • Tutorials
    • πŸͺ„BitBadges x AI
  • x/gamm
    • πŸ“šOverview
    • πŸ“¨Messages
Powered by GitBook
On this page
  1. ⌨️For Developers
  2. 🎁BitBadges Claims

Concepts

Standard vs On-DemandCompletion MethodsGating On-Chain ApprovalsClaim NumbersSuccess LogicSigned In vs Select AddressUniversal Approach - Claim CodesIdentify By Socials / Emails?
PreviousOverviewNextStandard vs On-Demand