Open Source Software Library

Users interact with D‑Wave quantum computers through a web user interface (UI), and through open-source tools that communicate with the Solver API (SAPI). The SAPI components are responsible for user interaction, user authentication, and work scheduling. In turn, SAPI connects to back-end servers that send problems to and return results from QPUs and additional solvers, which are located in different geographical regions (for example, North America or Europe).[1]

This repository is a template for creating an Aries Verifiable Credential Registry (VCR) Issuer Agent. Aries VCR is the foundational technology upon which the Government of British Columbia's OrgBookBC was built. Aries VCR Issuer Controller is a starter kit for building an Aries agent that issues verifiable credentials to instances of an Aries VCR, such as OrgBookBC. This repo contains code for an issuer controller that works with Aries Cloud Agent Python (ACAPy) framework. The controller and an instance of ACA-Py can be deployed together to implement an Aries issuer agent. aries-vcr-issuer-controller was developed as part of the Verifiable Organizations Network (VON). For more information on VON, visit https://vonx.io. Even better, join in with what we are doing and contribute to VON and the Trust over IP community. Still not sure what this is? Please see this Getting started with VON overview, paying particular attention to the VON Issuer/Verifier Agent section. That's what this repo implements.

Digital wallet solution comprised of plugins layered on top of OpenWallet Foundation ACA-Py, which streamlines the process of sending and receiving digital credentials for governments and organizations.

An Indy Tails Server is file server that is designed to receive, store and serve Hyperledger Indy Tails files. Indy tails files are generated by an issuer of Indy AnonCred verifiable credentials when a Revocation Registry is created and must be published to a location accessible by all holders that receive a credential referenced in that Revocation Registry. The generated file is static, it does not change, and the credential holders use the tails file to produce a zero-knowledge proof of non-revocation about their credential and include it when responding to a proof request with a proof that includes claims from a revocable credential. If you are new to Indy AnonCreds Revocation, please review this document to understand how Indy revocation works, and where tails files fit in. An Indy Tails Server is a customized file server that makes it easy for AnonCred Issuers to publish tails files and for holders to access those tails files. A tails file does not have to be published to an Indy Tails Server, they can be published anywhere as long as there exists a URL accessible to all holders to access the tails file. If holders are mobile iOS or Android apps, the URL must use SSL (e.g. must be https:) due to the restrictions in those OS's. Support for publishing tails files to an Indy Tails Server is built into Aries Cloud Agent Python.

Analytics dashboards for GeoBC authorization tools, helping teams understand usage and operational patterns. The repository supports evidence-based improvements to geospatial access services.

Wildfire Predictive Services application for prevention, preparedness, response and recovery decision support. It combines Python, React and geospatial data to help wildfire teams analyze weather and risk.