NoDataStorage

Introduction

Most modern systems are built on the assumption that if you want to verify something, you must store it. This approach creates databases, accounts, registrations, and record‑keeping systems that contain user identities, transaction histories, and links between products and their owners.

NoDataStorage (NDS) represents a fundamentally different approach. It allows verification of product authenticity, warranty status, and entitlement to benefits without storing any identifying information about the product or the customer. The identity of the product is not stored. The identity of the product is always re‑derived through computation.

NDS is a cryptographic identification mechanism without a database.

Core Principle

The foundation of the system is a cryptographic proof of payment, referred to as payment_proof. This proof serves as a deterministic input from which the identity of the product can be derived.

payment_proof may exist in three forms:

1. Bitcoin on‑chain transaction
   payment_proof = TXID

   TXID is the public identifier of a Bitcoin transaction recorded in the Bitcoin blockchain. It is globally verifiable, immutable, and exists independently of the manufacturer.

   payment_proof_bytes = TXID_bytes
2. Lightning Network transaction
   payment_proof = LN_invoice_string

   A Lightning invoice is a cryptographically signed string representing a Lightning payment. It is not archived by the manufacturer. Its preservation is the sole responsibility of the user.

   payment_proof_bytes = SHA256(LN_invoice_string)
3. FIAT payment via bank transfer
   payment_proof = BU:DATE:ID

   where:

   BU = manufacturer's bank account in standardized format
   DATE = date of settlement in YYYYMMDD format
   ID = payment identifier (e.g., variable symbol or reference number)

   payment_proof_bytes = SHA256(BU:DATE:ID)

   This string is provided to the client together with the product and enables cryptographic derivation of the product identity.

Cryptographic Identity Derivation

After obtaining payment_proof_bytes, the manufacturer uses a private secret key:

and computes an authentication identifier using the HMAC‑RIPEMD160 cryptographic function:

The result is a binary value of exactly 160 bits.

This value is converted into a textual representation using Base64 encoding:

Formally:

The resulting NDS_ID is physically engraved directly onto the product.

Authenticity Verification

Verification of the product does not require a database.

The manufacturer recomputes:

If computed matches the engraved NDS_ID, the product is authentic.

No lookup is required, because the identity of the product is not stored — it is always re‑derived through cryptographic computation.

Warranty and Product Identity

NDS functions as a cryptographic warranty mechanism.

The manufacturer provides an extended warranty of 3 years from the time of payment, covering material and manufacturing defects. The payment date can be deterministically derived from payment_proof.

NDS also enables identification of legitimate existing customers without storing their identity and allows cumulative benefits to be provided.

Absence of a Database

The manufacturer does not store:

• product lists
• customer lists
• owner identities
• product identifiers
• transaction databases within the NDS system

The identity of the product exists exclusively as the result of cryptographic computation.

FIAT Payments and Epistemic Risk

FIAT payments introduce a fundamental difference. The banking system inherently creates accounting records, and the manufacturer is legally required to retain financial records in accordance with applicable regulations.

These records exist outside the NoDataStorage system and are not part of its architecture.

Their existence increases the amount of information that exists about a transaction and therefore increases the potential epistemic risk of compromise.

For this reason, FIAT payments are not the preferred form of payment from a privacy and epistemic security perspective.

Preference for Cryptographic Payments

Bitcoin and Lightning Network payments preserve the full NoDataStorage architecture, because product identity is derived solely from cryptographic proof without creating external identity records within the manufacturer's system.

To encourage maximum privacy protection, the manufacturer provides a 10% discount when payment is made using Bitcoin or Lightning Network.

This payment method minimizes the amount of existing identifying information and preserves the epistemic integrity of the system.

Epistemic Security

The security of the NDS system does not result from protecting stored data, but from the absence of stored data.

There is no database to compromise. There is no identity to steal. There is no record to exploit.

Product identity exists only as the result of cryptographic computation.