The overhide remuneration API originally supported two simple end-points:
This, for all ledgers supported:
These were originally public ledgers: two blockchains and a publicly visible anonymized receipts ledger for USD.
As of 2022 the landscape has changed and transaction privacy is louded as a feature in second layers on top of the original blockchains via various centralizing oracles and other solutions.
As of this writing privacy is introduced into the US dollar overhide-ledger paving the way for other private ledger currency integrations: the API changes introduced now can be applied to any other non-public ledgers added to the overhide ecosystem in the future.
Privacy in overhide-ledger transactions means that transactions are visible only to parties that can prove ownership of an address involved in a transaction: either the payer or the payee.
With reference to the overhide-ledger API documentation (test, prod), the
GET /v1/get-transactions/.. endpoint now takes an optional
signature — which is the
Authorization header value signed by the
from-address. If this signature resolves, the API will return private transactions as well as public.
What constitutes a private transaction? Transactions are added to the ledger via the
transact.js as returned by the
You may continue to store public transactions with overhide-ledger, although this is not the default behaviour.
Privacy in overhide-ledger does not mean the data is somehow locked in a silo and you cannot get at your data.
Neither the data — nor the access to it (the code) — is in any way locked in.
No alternative ledger available or you want your own? No problem: all of the overhide service code is available on GitHub including redacted deployment scripts. You should be able to stand up your own cluster. Need help? Please ask questions at r/overhide.
⚠ as of this writing there is an outstanding issue for importing data into a new overhide-ledger instance. This functionality has not yet been coded. Please feel encouraged to contribute.