The numerous overhide GitHub repositories constitute the OSS code of the overhide system.
The overhide system is comprised of two main component categories:
- ledger-based authorization
- data-store brokerage
The data-store brokerage is the main deliverable of overhide and drives development of ledger-based authorization.
Introductory material is at https://overhide.io
Learn about the system in the overhide repo.
- why?
- motivation for ledger-based authorization
- read this first
- ledgers.js
- browser library for integration of ledger-based authorization into apps & services
- ledgers.js-demo (repo)
- a demo of a ledgers.js integration
- ledgers.js-demo-serverless-dapp (repo)
- a demo of a ledgers.js integration with the remuneration APIs running in a serverless back-end (Azure)
- Remuneration APIs
- overhide-ethereum
- Ethereum implementation of ledger-based authorization APIs
- US dollars ledger (main network) (test network)
- US dollars implementation of ledger-based authorization APIs
- closed source ledger enabling ledger-based authorization with fiat currencies: US dollars
- see the ledgers.js demo for example use/integration
- uses Stripe.com for payment processing
Note everything in overhide is OSS with the exception of overhide-ledger--the US dollars ledger.
Overhide-ledger is closed source and has a pending patent application (No. 62817820) "PSEUDONYMOUS FIAT CURRENCY TRANSACTION LOGGER SYSTEM AND METHOD FOR PAYMENT GATEWAYS". It covers the fiat-currency specific IP as summarized in the why write-up.
All of the below broker components are still in early stages of development; all towards the fist release as a minimally viable product.
-
overhide (specification)
- overall documentation
- broker API documentation
- definitions
- concepts
- specifications
-
armadietto (remotestorage.io)
- fork of remotestorage.io's storage server--armadietto
- adding ledger-based authorization to this offering
Our sincere hope is to grow overhide together.
Please join us: