Whether a digital warehouse receipt gets accepted by a bank hinges not on the word "chain" but on whether the fingerprint can be computed locally in a browser and stay tamper-proof. Our warehousing system now packages each receipt — title, grade, quantity, location — into a 256-bit SHA-256 digest, computed entirely on the client side in the customer's browser, with the private key never leaving the device.

The payoff is concrete. An owner taps once on a phone and gets the receipt fingerprint within three seconds, without pushing commercial data to our servers. For bank due diligence, the fingerprint is matched directly against the on-chain record, and title transfer that used to clear in T+1 now settles in minutes.

The ESG layer is new this year. Per-shipment carbon footprint, calculated from the actual voyage and vessel type, generates its own fingerprint and is chained alongside the receipt. Once the EU CBAM transitional period ends, downstream refiners must account for imports against it; we front-load the data so clients can pull it at customs filing.

Technically there is nothing flashy: SHA-256 is the NIST standard hash, natively supported by the browser Web Crypto API with no plugin. We deliberately avoided a private chain, because what banks need is verifiability, not opacity.