What exactly goes on the blockchain?

Only a SHA-256 hash — a 64-character fingerprint of the document — plus, for daily GPS commitments, non-identifying metadata like the date and counts. Document contents, GPS coordinates, payment details, and customer data never go on-chain.

Which documents are anchored?

New BOLs, DVIR inspections, invoices, signed documents, temperature logs, and uploaded workspace, load, HR/DQ, and compliance files are anchored automatically at creation. Records created before this feature rolled out are not backfilled, though an admin can anchor existing documents from the console.

What is the difference between Base Sepolia and Base Mainnet?

Base Sepolia is a free test network — faucet ETH, no fees, and records are not guaranteed permanent. Base Mainnet uses real ETH and produces permanent, production-grade evidence. Anchors keep the network they were created on, and any fingerprint can be re-anchored on the other network later.

How does verification detect tampering?

Verification recomputes the document's SHA-256 from the copy in private storage and compares it to the recorded fingerprint and the on-chain transaction data. If the document changed after anchoring, the recomputed hash will not match and the anchor is flagged as a mismatch.

Does anchoring expose our drivers' locations?

No. The daily GPS integrity commitment hashes the full private GPS summary first, and only that hash — with driver and ping counts — is committed on-chain. Exact locations stay in private storage.

Does this cost anything?

Each anchor is a tiny 0-value blockchain transaction. On Base Sepolia the test ETH is free. On Base Mainnet, anchoring spends a small amount of real ETH per submission, which is why the network switch is an explicit admin decision.

Can someone outside TMSDASH verify our anchored documents?

Yes. The public Verify page lets anyone check an anchor by its transaction hash or SHA-256 fingerprint, with no TMSDASH account. They can also load their own copy of the document, which is hashed locally in their browser — never uploaded — and compared against the fingerprint confirmed on-chain.

Trust & Integrity

Tamper-evident documents, anchored on the Base blockchain

Name: TMSDASH
Brand: TMSDASH
Price: 99 USD

TMSDASH fingerprints every new BOL, DVIR, invoice, and signed document with SHA-256 and anchors that fingerprint on Base — plus a daily driver-GPS integrity commitment. The documents and raw GPS data stay in private storage; only the hash ever goes on-chain.

Start free trial Book a demo

New: verify any anchor, no account needed

Anyone — an auditor, an insurer, a customer, or you — can confirm a TMSDASH-anchored document in under a minute. Here is how public verification works.

Find the reference

Every anchor is identified by its on-chain transaction hash (0x…) or the 64-character SHA-256 fingerprint it recorded.

Hash the document locally

The Verify page hashes your copy of the document right in the browser. The file itself is never uploaded anywhere.

Confirm on-chain

TMSDASH independently confirms the fingerprint on the Base blockchain. A match proves the document is unchanged since anchoring; a mismatch flags a later edit.

Verification demonstrates tamper evidence: it shows whether a document changed after its fingerprint was recorded on-chain. It does not prove the original contents were truthful, accurate, or complete.

Try it now

Paste an anchor reference to check it on the public Verify page.

Open the full Verify page

Proof your paperwork cannot be quietly rewritten

Automatic fingerprinting

Every new BOL, DVIR, invoice, signed document, and uploaded file is hashed with SHA-256 and anchored the moment it is created — no extra step for your team.

Daily GPS integrity commitment

Each morning, per carrier, the day's driver GPS activity is summarized and hashed. Only the commitment hash and non-identifying counts go on-chain — exact coordinates never leave private storage.

Testnet or Mainnet — your call

Anchors go to Base Sepolia (testnet) by default, or Base Mainnet for permanent, production-grade evidence. Existing anchors keep their network and any fingerprint can be re-anchored on the other.

One-click verification

Recompute a document's fingerprint and compare it against the on-chain record. A match proves the document is unchanged since anchoring; a mismatch flags a post-anchoring edit.

A strict privacy boundary

Only hashes go on-chain. Document bytes, GPS coordinates, payment details, and customer data are never written to the blockchain — they stay inside TMSDASH private storage.

Live on-chain tracking

Every anchor gets a transaction hash, block number, and explorer link, with pending submissions retryable and verifiable right from the anchoring console.

How it works

Documents anchor themselves

Create BOLs, DVIRs, invoices, and uploads as usual. TMSDASH hashes each one and records its fingerprint on the active Base network automatically.

GPS commits daily

A scheduled morning job summarizes the previous day's driver GPS activity per carrier and anchors one commitment hash — drivers and ping counts only, never coordinates.

Verify any time

From the anchoring console, re-verify an anchor: TMSDASH recomputes the hash from private storage and confirms the on-chain transaction carries the same fingerprint.

Upgrade to permanence

When you need production-grade evidence, switch the active network to Base Mainnet and re-anchor existing fingerprints — testnet history stays viewable and verifiable.

TMSDASH document anchoring console showing anchored document fingerprints, on-chain transaction statuses, and the active network card

Frequently asked questions

See a sample evidence report

Every anchored document and daily GPS commitment can be exported as an audit-ready evidence package. Download the samples to see exactly what your auditor receives.

PDF report

The full evidence report as a PDF: document label, fingerprint, network, transaction, verification status and history, and the tamper-evidence disclaimer.

Download sample

JSON bundle

The same evidence package in the tmsdash.evidence.v1 JSON schema, ready for automated audit tooling and record keeping.