Whitepaper

MMS Receipt White Paper

MoreMeasure Storage · Version 2 · 21 October 2026

MoreMeasure Storage Receipt: sensor-verified, tamper-evident receipts for stored agricultural products, rare earths and precious metals.

Progress

Where the project stands, newest first.

1. 27 Oct 2026
   IoT deployment at your own siteMoreMeasure now installs and monitors IoT devices at customers' own grain bins, silos, cages and vaults, so goods never have to move. Customers request a deployment on this website or in the app; we assess the site, quote, install, calibrate and go live. Points come only from receipts confirmed on Bitcoin, never from printed copies, and are spent as a discount on the monthly subscription.
2. 23 Oct 2026
   Points limit and welcome discountCustomers can use up to 150 points for discounts each month, refreshed monthly with a subscription, and new customers get 10% off their first invoice. Scanning a receipt's QR code now opens the customer's Receipts page.
3. 22 Oct 2026
   Online paymentsCustomers can pay MMS Receipt invoices with PayPal, Cash App Pay or QuickBooks, or take reward points off the bill. Payment accounts are being connected.
4. 22 Oct 2026
   Points rewardsSubscribers can keep points in their Points wallet or spend them as a discount on storage fees: $1.00 per point, from 5 points.
5. 21 Oct 2026
   Version 2 announcedSupport for every type of IoT device that measures a real-world asset, and subscriber points: one point for each receipt timestamped on the Bitcoin blockchain.
6. 19 Oct 2026
   White paper version 1 publishedThis paper sets out the receipt record, the trust model and the governance rules for the proof of value.
7. 19 Oct 2026
   MMS Receipt website launchedPublic pages explain how receipts work, with a live simulator and the storage unit application.
8. 19 Oct 2026
   Receipt data model and layout designed23 fields in seven groups, with a printed receipt and a phone e-receipt built from the same record.
9. Oct 2026
   Facility simulator built24 simulated storage units on three floors stream readings in the Azure IoT Hub format and issue hash-sealed receipts with QR codes.

Abstract

MMS Receipt turns a stored physical asset into a record that anyone can check. IoT sensors that MoreMeasure installs in each customer's bins, cages and vaults measure the quantity and quality of what is inside, Azure IoT Hub archives every reading, and the receipt service seals a snapshot of those readings with a SHA-256 hash. That hash is timestamped on the Bitcoin blockchain through OpenTimestamps, and the receipt is issued as a printed document and an e-receipt carrying the same QR code. A lender, buyer or inspector can scan the code and confirm in seconds that the quantity, quality, owner and storage unit have not changed since the receipt was issued. Version 2 widens the devices a receipt can draw on to any sensor that measures a real-world asset, and rewards subscribers with one point for each receipt timestamped on Bitcoin. This paper describes the problem MMS Receipt addresses, how the system works, what a receipt contains, and the rules that make it trustworthy as proof of value.

The problem

Stored commodities are valuable collateral, but a lender who cannot see them must trust a paper record. Grain, rare-earth oxides and bullion are held in warehouses far from the banks and buyers who rely on them, and a conventional warehouse receipt is only as reliable as the person who wrote it.

Three gaps follow from that:

• Quantity can drift from the record. Stock is withdrawn, short-weighted or pledged twice, and the paper receipt does not change.
• Quality is a one-time claim. Moisture in grain, purity in rare earths and fineness in metals are measured at intake, if at all, and can degrade or be misstated afterwards.
• Records can be altered. A receipt held in one company's database can be edited by anyone with access, and an outsider has no independent way to tell.

MMS Receipt closes these gaps by measuring the asset continuously, sealing each receipt cryptographically, and publishing proof of that seal where no single party can change it.

How it works

A receipt moves from sensor to sealed record to public proof in five steps, and verification replays those steps in reverse.

1. Measure. Each storage unit has its own sensor node reporting weight, quality and storage conditions.
2. Collect and archive. Readings flow to Azure IoT Hub, and every message is archived as JSON in Azure Blob Storage.
3. Seal. When the owner and MoreMeasure certify a receipt, the receipt service takes the current readings, builds the receipt record and hashes it with SHA-256.
4. Anchor. The hash is submitted to OpenTimestamps, which records it in a Bitcoin transaction together with many others.
5. Issue. The receipt is printed and delivered as an e-receipt, both carrying a QR code with the receipt number and hash.

Scanning a receipt's QR code. The QR code opens a web link, not raw data, so anyone can read the result. A receipt downloaded from the simulator links back to the MMS Receipt software: the customer signs in with their own account in a web browser and goes straight to their Receipts page, which lists every receipt issued to them, with the scanned receipt picked out. If the customer is already signed in, the page opens at once. Receipts from the simulator are practice receipts: they carry a "Simulated" watermark and are not stored in anyone's account.

A verifier scans the QR code; the receipt service recomputes the hash from the Azure archive and checks its timestamp proof against Bitcoin, so a receipt passes only if both independent records agree.

What a receipt contains

Each receipt is one structured record of 23 fields in seven groups. The first five groups are sealed by the hash, and the last two record the receipt's live state.

The readings on a receipt depend on what is stored:

Every reading is marked in spec, near limit or out of spec, and the worst of them sets the receipt's quality verdict: PASS, CONDITIONAL or HOLD. A HOLD verdict blocks issuance: no receipt is issued for that unit until its readings are back in spec, so a lender never receives a receipt for out-of-spec goods.

The receipt is issued in two forms built from the same record. The printed receipt is an A4 or US Letter page, black on white so it survives photocopying, with signature lines for the owner and a MoreMeasure officer. The e-receipt is a phone view with a one-tap Verify button. Both carry the same QR code.

Trust model

A receipt can be trusted because three independent records must agree: the sealed receipt, the archived sensor telemetry, and the hash timestamped on Bitcoin.

Sealing. When a receipt is issued, its sealed fields are written as canonical JSON (keys sorted, no whitespace, fixed numeric precision) and hashed with SHA-256. Changing a single digit of the quantity, a reading, the owner or the unit produces a completely different hash.

Anchoring. The receipt service submits each receipt hash to several public OpenTimestamps calendar servers. The calendars combine the hashes they receive into a Merkle tree and record its root in a Bitcoin transaction, so MoreMeasure pays no transaction fees and holds no cryptocurrency. Each receipt keeps a small timestamp proof (an .ots file) that links its own hash to that Bitcoin block. Once the transaction is confirmed, usually within a few hours, no one, including MoreMeasure, can alter or backdate it. Only the hash is published; owner, asset and quantity data never leave MoreMeasure's systems.

Verification. Scanning the QR code opens the receipt in the MMS Receipt software with its receipt number and hash. The receipt service reloads the record, recomputes the hash from the telemetry archived in Azure Blob Storage, checks the timestamp proof against the Bitcoin blockchain, and reads the receipt's current status. The verifier sees one of three results:

Residual risks. Anchoring makes tampering detectable, not impossible: the Azure records must still be protected with normal access controls. Until a Bitcoin confirmation arrives, a new receipt's proof relies on the calendar servers, so the service uses several calendars and stores the completed proof as soon as it is available. Anyone can check a completed proof with the open-source OpenTimestamps tools, without trusting MoreMeasure.

Device coverage

Version 2 is not tied to particular hardware. Any device that measures a stored asset can feed a receipt, as long as it reports under its own Azure IoT Hub identity and its readings fit the receipt's quantity, quality or condition groups.

Each new device type adds fields and limits to the catalog; the sealing, timestamping and verification steps do not change.

The nine asset classes the catalog covers: Agricultural (grain, oilseeds, coffee, cocoa, nuts); Precious metals (gold, silver, platinum, palladium); Rare earths and critical minerals; Base metals (copper cathode, aluminium, nickel, zinc); Liquids in tanks (edible oils, fuels, ethanol, chemicals); Softs in bales and bags (cotton, sugar, wool); Gemstones and diamonds; Livestock and aquaculture; Timber and forest products.

Below is the full catalog of 58 device types, grouped by what they measure. In the "Used for" column, Ag means agricultural products, Metals means precious metals and REE means rare earths and critical minerals.

Quantity (13)

The numbers a lender cares about first: weight, count and volume.

Quality (17)

Grade, purity and fineness decide the value of the goods, so they are measured, not declared.

Condition (13)

Storage conditions show the goods are still in spec.

Custody and security (7)

Security events show the goods are still there and nobody has touched them.

Location and transport (4)

For goods on the move, so a receipt can follow a shipment.

Connectivity and device health (4)

Whatever the sensor, readings travel the same way: a trusted device identity, an encrypted link, and Azure IoT Hub.

Subscriber points

Subscribers to MMS Receipt earn one MMS point each time one of their receipts is timestamped on the Bitcoin blockchain. Points reward keeping goods under continuous, verifiable measurement.

• When a point is earned. After the hourly OpenTimestamps batch containing the receipt's hash is confirmed in a Bitcoin block, the receipt service adds one point for that receipt. Every receipt in a batch earns its own point.
• Who earns it. The subscriber account named as the receipt's owner, provided its subscription is active when the Bitcoin block confirms. Cancelling a subscription keeps the points already earned.
• What does not earn. A HOLD verdict blocks issuance, so out-of-spec goods never produce a receipt or a point, and a voided receipt earns nothing. Each receipt earns at most one point.
• How it is recorded. Points are an append-only ledger in the receipt database. Each entry names the receipt number, its hash and the Bitcoin block, so any balance can be rebuilt and checked against the public blockchain. Adjustments, such as redemptions, are added as signed entries with a reason, and a balance never goes below zero.
• Welcome discount. New customers who sign up for an MMS Receipt account get a one-time 10% discount on their first invoice for the software, taken off automatically.
• Monthly limit of 150 points. A customer can use up to 150 points for discounts each calendar month. With an MMS Receipt subscription, the 150-point limit refreshes on the first day of every month. Points above the limit stay in the wallet for the next month.
• Spending points. Points are held in the subscriber's Points wallet and never expire. They can be spent as a discount on MMS fees, such as the monthly monitoring subscription, at $1.00 per point, from 5 points up to the monthly limit. Spending creates a voucher code (MMSV-XXXX-XXXX) that staff take off an invoice; an unused voucher can be cancelled and its points return to the wallet. Each voucher is a ledger entry, so the balance always matches the ledger.
• What points are. Account credits inside MMS Receipt, not a cryptocurrency or token. See the Points page.

Payments

Customers pay for the MMS Receipt service through the Billing page in the app. MoreMeasure issues each customer an invoice (numbered like INV-2026-000001, in US dollars, with what it is for and an optional due date), and the customer pays it with the service they already use.

• Points as payment. Before paying, a customer can apply an unused points voucher to an invoice. A voucher cannot be worth more than the amount left to pay; if it covers the whole invoice, the invoice is paid with points.
• Confirmation. Each checkout returns the customer to the app, which asks the provider whether the payment went through and checks the amount before marking the invoice Paid, with the provider and reference. Open payments are re-checked every 5 minutes.
• Statuses. An invoice is Open (with its due date), Paid or Void. An admin can void an unpaid invoice, which makes any voucher on it usable again.
• Card safety. Card and bank details are entered only on PayPal's, Square's or Intuit's own pages and never pass through MMS Receipt.

The Billing page is built; until MoreMeasure's PayPal Business, Square and QuickBooks Online (with QuickBooks Payments) accounts are connected, every pay button opens a practice checkout and no money moves.

Governance

Four rules keep each receipt tied to one owner, one unit and one verified snapshot.

1. Receipts are non-negotiable. A receipt cannot be transferred by endorsement or delivery. If ownership changes, MoreMeasure issues a new receipt to the new owner and marks the old one SUPERSEDED. This closes the main route to fraud: a forged or stolen paper receipt cannot be passed on as valid.
2. Owner and MoreMeasure certify together. Issuing, pledging and releasing a receipt each require sign-off from both the owner and a MoreMeasure officer, recorded on the printed receipt's two signature lines and in the receipt's event log.
3. Every change creates a new receipt. A deposit or partial withdrawal triggers fresh sensor readings and a new sealed receipt; the old receipt points to its replacement. A full withdrawal marks the receipt RELEASED, and a receipt issued in error is marked VOID. A pledged receipt cannot change until its lien holder releases it.
4. Storage units are added and retired, never erased. A new unit is registered with its floor, asset class and capacity, and bound to its own Azure IoT Hub device. A unit can be retired only when it has no ACTIVE or PLEDGED receipt; its device is disabled but its records and telemetry are kept, so past receipts always verify. A retired unit ID is never reused.

Who uses it

Proof-of-value scope

The proof of value demonstrates the full receipt cycle on simulated sensor data before any physical hardware is installed. MoreMeasure's simulator already models 24 storage units across three floors (agricultural, rare earths, precious metals) sending telemetry toward Azure IoT Hub, and issues hash-sealed receipts.

In scope for the proof of value:

• Receipt record and hashing as specified in this paper
• Printed and electronic receipt layouts
• Verification by QR code, including the three verification results
• Storage unit add and retire, with receipt status changes
• Bitcoin timestamping of receipt hashes through OpenTimestamps
• Subscriber points: one point per receipt timestamp confirmed on Bitcoin
• A device catalog open to any sensor that measures a real-world asset