SNSUC's warehouse-receipt trust chain starts in the browser, not with any central server stamp. Each time a warehouse issues a receipt, the front end runs the receipt fields — owner, product, quantity, location, lot — through the Web Crypto API to compute a SHA-256 digest; the 256-bit hash is written to the blockchain ledger alongside the receipt. When a buyer opens the receipt page, the browser recomputes the same digest locally and compares it byte-for-byte with the on-chain record. Any altered field breaks the hash on the spot and the receipt flags red immediately.

ESG carbon footprints travel the same channel. For every resale, the emission factor from load port to destination (bunker tonnes × voyage distance × emission coefficient) is computed at signing and turned into a tamper-evident footprint credential. Upstream refiners and downstream buyers can pull that credential by receipt id and cite it directly in Scope 3 accounting, dropping the email chase for certificates.

In practice, receipt fields are normalized before anchoring — fixed field order, units and precision — so the same receipt never yields two hashes. Each credential gets a 7-day review window; silence past the window counts as title confirmation.