Introduction to overhide-ledger and Motivation for Why it’s Useful.

Workflows

Some Basics from Crypto Ledgers

Ledger Based Authorization

Figure 1: Ledger-based authorization workflow.

Typical Web 2.0 Authorization

Figure 2: Web 2.0 authorization flow

Remuneration APIs

Figure 3: Currencies abstracted by overhide remuneration API
  • get transactions / tallies
  • verify identity

From Login client to Service Business End

  • the login page is decoupled from the business logic service
  • login page interacts with ledgers to view transactions and create payments on the ledger
  • payments to ledgers are through wallets
  • authentication occurs at the login phase without necessarily using any ledger, by simply signing a public address
  • this layer is likely in the browser while the business end is in native code or some back-end ¹ ²
  • the service can be on any software stack as long as supports HTTP calls
  • authentication and authorization don’t need a browser: simple HTTP API can be called from any software stack
  • authentication and authorization can be abstracted for most ledgers; keeping the core app code the same despite ledger in use

Demo

overhide-ledger

Figure 4: Overhide-ledger for fiat dollar transactions

What Does overhide-ledger Do?

Figure 5: Payment-gateway transaction in dollars
  • account ID
  • amount
Figure 6: Transaction in on a decentralized ledger like Etehreum
  • provider address
  • user address
  • amount
  • timestamp

Differences From Blockchain

  • Stripe knows both parties intimately
  • overhide-ledger knows of both parties
  • payer can prove ownership of her public address
  • payee can prove ownership of her private address
  • everyone knows the pseudonymous payment was made for all time

Community needed

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store