Blockin
  • Blockin Overview
  • How Does It Work?
  • Developer Docs
    • Core Concepts
    • Getting Started
      • 🖊️User Signatures
      • 🖥️Sign In with BitBadges
      • 🆔Verification
      • 📤ChainDrivers
        • Setting Chain Drivers
        • Chain Driver Interface
        • Implementing a New Chain Driver
        • List of Implemented Chain Drivers
          • EthDriver
          • SolDriver
          • CosmosDriver
          • BtcDriver
          • AlgoDriver
    • Library Documentation
Powered by GitBook
On this page
  • Installation
  • Goal
  • Resources
  1. Developer Docs

Getting Started

PreviousCore ConceptsNextUser Signatures

Last updated 1 year ago

Pre-Readings -

Installation

In any codebase that requires Blockin, run npm install blockin

Goal

Blockin is open-source and customizable. This results in many implementation decisions that you potentially need to make. Consider the best ones for your use cases. Each implementation will have its pros and cons. However, every implementation requires having users sign a challenge message and a verifier verifying the (message, signature) pair, regardless of how you do so.

For custom backend verification implementations (i.e. not outsourced), you will need to implement the ChainDriver functionality as well.

Resources

- The BitBadges quickstart natively implements Blockin in a few methods explained in this documentation. It provides boilerplate to allow you to customize your Blockin experience how you would like to.

Completely Outsourced - Completely outsource your authentication to BitBadges. Only applicable when you can pre-generate signatures (e.g. user pre-generates a QR code and presents it at ticker booth at later time). Visit .

https://bitbadges.io/auth/linkgen
Core Concepts
🖊️User Signatures
🆔Verification
📤ChainDrivers
BitBadges Quickstart