The Ledger-Based Authorizations APIs were originally written with fully publicly visible ledgers in mind. In 2022 the landscape is such that some desire these anonymized transactions kept fully private. To this end, as of now, the overhide-ledger allows — and by default keeps — all transactions private.

The overhide free open-source offering is now complete with ready-to-use widgets to be intergrated into your Web product in support of logins and in-app purchases (IAP).

The overhide APIs and the ledgers.js library (starting with version 4.2.0) support normalizing in-app purchase fees to US dollars — to reduce the hassle of fluctuating cryptos.

The overhide APIs and the ledgers.js library (starting with version 4.0.0) encourage use of access tokens. Not yet mandatory, but will be soon enough.

Answering the basic question of what is Ledger-Based Authorization.

An synopsis of Ledger-Based Authorizations and available software to incorporate in Web services.

A discussion of overhide deployments as they're running at https://overhide.io and https://ledger.overhide.io; as well as the future direction of components yet to be completed.

An introduction to ledger-based authorizations.

When authoring a service or application that wholly runs in a user-agent such as a browser, you must be cognizant that the application source code is in the clear and modifiable.

This becomes an issue when your business-logic has code flows conditional on authorization tiers.

An introduction of overhide-ledger: a centralized Web 2.0 ledger of dollar transactions exposed through a minimal API.

The intent of the ledger is to enable a simple authorization workflow that's useful today for dollars and tomorrow for cryptos.