Technical Overview
OpenQ is built from an 80/20 combination of decentralized and centralized components, with a roadmap towards total decentralization by the end of 2022

OpenQ Open Source Code

All of our code is open source and can be found in our GitHub organization, OpenQDev.

The OpenQ Stack

The OpenQ stack is composed of the following elements:
  • Smart contracts running on Polygon (soon many other EVM compliant networks)
  • An open source GitHub API oracle running in Open Zeppelin Defender​
  • A subgraph from The Graph indexing all Events surrounding bounties
  • ​CoinGecko API for fetching latest token prices
  • Redis for caching token prices for 1 minute
  • GitHub OAuth2 for verifying user identity
  • Docker, Kubernetes and Helm for microservice containerization, orchestration and deployment
  • AWS Elastic Kubernetes Service (EKS) for hosting our Kubernetes cluster
  • ​cert-manager for automatic renewal of our SSL certificates

Path to Decentralization

Decentralized Hosting

We are working with Internet Computer towards a fully decentralized hosting environment, running our workloads as WASM processes on ICP's decentralized node network rather than as containers in AWS.

Disintermediated Oracle

OpenQ is working with API3 and GitHub to eventually have GitHub self-host an Airnode.
Why don't you use ChainLink?

OpenQ Architecture

The easiest way for a birds-eye and worms-eye view of every nook and cranny of OpenQ's architecture is through our interactive Ilograph diagram.

Why Transparency Matters

OpenQ is radically transparent about our architecture for two reasons:
  • Security through obscurity is no security at all
  • We want the onboarding and offboarding of our contributors to be as seamless as possible