Witness Chain
  • Introduction to Witness Chain
  • Infinity Watch
    • Proof of Location (Mainnet)
      • Introduction
      • Process flow
      • Architecture
      • Run a watchtower!
        • For Partner node runners
          • Running on Akash Cloud
          • Running on SuperNoderz
        • EigenLayer operators
          • Running a PoL Watchtower
          • Witness Chain AVS opt-in guide
        • At-home watchtowers
        • For DePIN/Validator Node provider
      • Demos
      • PoL Research
    • APIs
      • Campaign APIs
        • Key Terminologies
        • Authentication
        • Create Campaign
        • Edit campaign
        • Get Photo feed from campaign
        • Get Campaigns
      • Challenge APIs
        • Overview
        • Getting Started
  • Resources
    • Blogs
      • How Proof of Location Works
      • Redefining Geolocation Compliance: Witness Chain & Predicate
    • 🗞️Research
    • 🎙️Talks and Podcasts
    • 🤝Community
    • ⚖️Smart Contracts
    • File a bug
  • Archive
    • Introduction
    • Proof of Diligence Watchtower Protocol
      • How it works
      • Diligence Watchtower Roadmap
      • Watchtower Architecture
      • Chains watched
      • Smart Contracts
      • Quick Links
      • FAQs
    • For the node operators
      • Node requirements
      • Watchtower setup
        • [ARCHIVE] Mainnet Setup
          • L2 Archive Node Setup guide
        • Holesky Setup
          • L2 Archive Node Setup guide
        • Migration from archive to full node
      • Monitoring
    • Research
    • Keys Management
    • Proof of Bandwidth
      • Introduction
      • Architecture
      • For the node operators
        • Running a PoB Challenger Client
        • Running a PoB Prover Client
      • Demos
      • Research
    • 🤝Watchtower Protocol (Architecture v1)
      • 🗼How it works
      • 📅Watchtower Roadmap
      • 🏦Watchtower Architecture
      • 🔗Chains supported
Powered by GitBook
On this page
  • Basic Concepts
  • Provers
  • Watchtowers (aka Challengers)
  • Challenge
  • Broker
  • Challenge Coordinator (CC)
  1. Infinity Watch
  2. APIs
  3. Challenge APIs

Overview

The Challenge APIs are an HTTP-based API that you can use to programmatically query data about watchtowers/provers, submit and manage challenges. Since the API is HTTP-based it works with any language or software that supports HTTP, including cURL and almost all modern web browsers.

Basic Concepts

Provers

The device connected to Internet whose claimed location or bandwidth needs to be validated

Watchtowers (aka Challengers)

A pool of decentralized, trustfree servers that validate the location / bandwidth claim of the prover

Challenge

A series of UDP ping pongs/pings between the prover and watchtowers to validate the claim (Location or Bandwidth)

Broker

A server which provides APIs for provers/challengers/payers. These APIs are used to login/request-for-challenges/participate-in-challenges/submit-results-of-challenges.

Challenge Coordinator (CC)

A server which randomly selects eligible challengers for a given challenge.

It ensures that available and compatible challengers are chosen for a given challenge.

CC only responds to events from Broker and does not interact with any other system.

PreviousChallenge APIsNextGetting Started

Last updated 6 months ago