<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[TRAMPTO Blog]]></title><description><![CDATA[TRAMPTO Blog]]></description><link>https://trampto.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Sun, 22 Nov 2026 17:02:46 GMT</lastBuildDate><atom:link href="https://trampto.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[E-signature or hash seal? They answer different questions]]></title><description><![CDATA[Originally published on DEV. "Just get it e-signed" has become the default answer to anything involving a document. But an e-signature and a hash seal…]]></description><link>https://trampto.hashnode.dev/e-signature-or-hash-seal-they-answer-different-questions</link><guid isPermaLink="true">https://trampto.hashnode.dev/e-signature-or-hash-seal-they-answer-different-questions</guid><category><![CDATA[Security]]></category><category><![CDATA[Productivity]]></category><category><![CDATA[startup]]></category><dc:creator><![CDATA[TRAMPTO]]></dc:creator><pubDate>Sat, 21 Nov 2026 14:10:08 GMT</pubDate><content:encoded><![CDATA[<p><em>Originally published on <a href="https://dev.to/trampto/e-signature-or-hash-seal-they-answer-different-questions-1d25">DEV</a>.</em></p>
<p>"Just get it e-signed" has become the default answer to anything involving a document. But an e-signature and a hash seal answer two different questions, and mixing them up leads to paying for the wrong tool, or trusting the wrong one.</p>
<h2>Two questions, not one</h2>
<ul>
<li><strong>Who agreed to this?</strong> That's what a signature answers. It ties a person to a document.</li>
<li><strong>Is this exactly the document that was issued?</strong> That's what a hash seal answers. It ties a document to its exact content at a point in time.</li>
</ul>
<p>Plenty of documents need only the second: a quote you send, an invoice, a report, meeting minutes, a deliverable. Nobody needs to "sign" them. What matters is that what arrives is exactly what left.</p>
<h2>What an e-signature gives you</h2>
<ul>
<li>Identity of the signer (how strong depends on the type: simple, advanced or qualified, in EU terms).</li>
<li>Intent: the person agreed to the content.</li>
<li>Usually an audit trail kept by the signing platform.</li>
</ul>
<p>The cost: accounts for the signer, a workflow, often a per-envelope or per-seat price. Great for contracts. Overkill for "here is my quote".</p>
<h2>What a hash seal gives you</h2>
<p>A SHA-256 fingerprint of the file, registered with a date. Change one character and the fingerprint no longer matches.</p>
<ul>
<li><strong>Integrity</strong>: anyone can check the file hasn't changed since sealing.</li>
<li><strong>No accounts needed</strong> to verify: the recipient opens a link or drops the file.</li>
<li><strong>Privacy</strong>: the fingerprint reveals nothing about the content.</li>
</ul>
<p>What it does <strong>not</strong> give you: proof of who wrote the document, or that anyone agreed to it.</p>
<h2>A quick way to choose</h2>
<table>
<thead>
<tr>
<th>You need to prove...</th>
<th>Use</th>
</tr>
</thead>
<tbody><tr>
<td>Someone agreed to terms</td>
<td>E-signature</td>
</tr>
<tr>
<td>The document wasn't altered after you sent it</td>
<td>Hash seal</td>
</tr>
<tr>
<td>Both</td>
<td>Sign it, and seal the signed copy</td>
</tr>
</tbody></table>
<h2>Where TRAMPTO fits</h2>
<p><a href="https://trampto.com">TRAMPTO</a> is the hash-seal side. You seal a PDF in your browser (the file is never uploaded) and share a public verification link. The recipient checks it in seconds, for free, with no account.</p>
<p>It's not a signature and doesn't try to be. Where the law requires a qualified e-signature or seal, use one. For the many everyday documents where the real risk is a quiet edit, a seal is the lighter, cheaper tool.</p>
<h2>What do you use?</h2>
<p>Do you e-sign everything by default, or only contracts? Where has a plain "this is the exact file" check been enough for you?</p>
]]></content:encoded></item><item><title><![CDATA[How do you prove a document existed on a given date (without a notary)?]]></title><description><![CDATA[Originally published on DEV. You finished a proposal, a design, a report or a contract draft. Months later someone says they had the idea first, or that…]]></description><link>https://trampto.hashnode.dev/how-do-you-prove-a-document-existed-on-a-given-date-without-a-notary</link><guid isPermaLink="true">https://trampto.hashnode.dev/how-do-you-prove-a-document-existed-on-a-given-date-without-a-notary</guid><category><![CDATA[Security]]></category><category><![CDATA[Productivity]]></category><category><![CDATA[startup]]></category><dc:creator><![CDATA[TRAMPTO]]></dc:creator><pubDate>Mon, 16 Nov 2026 12:28:03 GMT</pubDate><content:encoded><![CDATA[<p><em>Originally published on <a href="https://dev.to/trampto/how-do-you-prove-a-document-existed-on-a-given-date-without-a-notary-4hpn">DEV</a>.</em></p>
<p>You finished a proposal, a design, a report or a contract draft. Months later someone says they had the idea first, or that the version you sent was different. You know the date. Can you prove it?</p>
<p>The usual answers are weaker than they look.</p>
<h2>What people usually rely on</h2>
<ul>
<li><strong>The file's "created" or "modified" date.</strong> It lives on your computer and can be changed in seconds. It proves nothing to anyone else.</li>
<li><strong>An email to yourself.</strong> Better, but it shows that <em>an</em> attachment existed, not that today's file is the same one. Edit the PDF afterwards and nobody can tell.</li>
<li><strong>A cloud folder.</strong> Version history helps, but it's controlled by you and the provider, and it's hard to show to a third party.</li>
<li><strong>A notary.</strong> Strong, but slow and paid, for something you might need several times a week.</li>
</ul>
<p>The gap in all of them is the same: they show a date, but not that <strong>this exact file</strong> is the one that existed on that date.</p>
<h2>Date + fingerprint</h2>
<p>A cryptographic hash (SHA-256) gives any file a 64-character fingerprint. Change one character and the fingerprint is completely different.</p>
<p>If you register that fingerprint with a date in a place you don't control, you get two things at once:</p>
<ol>
<li><strong>When</strong> the document was registered.</li>
<li><strong>That it hasn't changed since</strong>, because anyone can recompute the fingerprint of the file they have and compare.</li>
</ol>
<p>You don't need to share the content to do it: the fingerprint reveals nothing about what's inside.</p>
<h2>How we do it at TRAMPTO</h2>
<p>With <a href="https://trampto.com">TRAMPTO</a> you seal the document in your browser (the file is never uploaded), and you get a certificate and a public verification link. Anyone who opens the link sees the date it was sealed and whether the file they hold is exactly that one.</p>
<p>Useful for:</p>
<ul>
<li><strong>Proposals and quotes</strong>: the version you sent, on the day you sent it.</li>
<li><strong>Creative work and deliverables</strong>: proof that a design or report existed by a date.</li>
<li><strong>Minutes and agreements</strong>: the content as it was when everyone agreed.</li>
</ul>
<h2>The honest limits</h2>
<ul>
<li>The date comes from <strong>TRAMPTO's register</strong>, not from a qualified timestamp authority or a blockchain. It's strong everyday evidence, not a notarial deed.</li>
<li>It proves the file existed and hasn't changed since sealing. It doesn't prove <strong>who</strong> wrote it or that the content is true.</li>
<li>Where the law requires a qualified timestamp or a notary, use those.</li>
</ul>
<p>For the day-to-day question, "can I show this is the exact file I had on that date?", a sealed fingerprint gets you most of the way, in seconds and for free to verify.</p>
<h2>Over to you</h2>
<p>Have you ever needed to prove when you created something? How did you do it, and did it hold up?</p>
]]></content:encoded></item><item><title><![CDATA[The invoice scam that changes one line: why "it looks right" is not verification]]></title><description><![CDATA[Originally published on DEV. A supplier sends you an invoice. Same logo, same layout, same amount, same reference. You pay it. Two weeks later the supplier…]]></description><link>https://trampto.hashnode.dev/the-invoice-scam-that-changes-one-line-why-it-looks-right-is-not-verification</link><guid isPermaLink="true">https://trampto.hashnode.dev/the-invoice-scam-that-changes-one-line-why-it-looks-right-is-not-verification</guid><category><![CDATA[Security]]></category><category><![CDATA[fintech]]></category><category><![CDATA[cybersecurity]]></category><dc:creator><![CDATA[TRAMPTO]]></dc:creator><pubDate>Sun, 15 Nov 2026 13:11:01 GMT</pubDate><content:encoded><![CDATA[<p><em>Originally published on <a href="https://dev.to/trampto/the-invoice-scam-that-changes-one-line-why-it-looks-right-is-not-verification-54di">DEV</a>.</em></p>
<p>A supplier sends you an invoice. Same logo, same layout, same amount, same reference. You pay it. Two weeks later the supplier calls: they never got the money.</p>
<p>Somewhere between their outbox and your accounts team, one line changed: the IBAN.</p>
<p>This is one of the most common business payment scams, and it works for a boring reason: <strong>nobody checks the bank details, because everything else looks right.</strong></p>
<h2>How it usually happens</h2>
<ul>
<li><strong>A compromised mailbox.</strong> The attacker reads real conversations and waits for an invoice to be sent, then forwards an "updated" copy.</li>
<li><strong>A lookalike domain.</strong> <code>supplier-invoices.com</code> instead of <code>supplier.com</code>. The email says "we changed banks, please use the attached invoice".</li>
<li><strong>An edited PDF.</strong> Changing a few characters in a PDF takes seconds, and with AI tools the result is visually perfect: fonts, spacing, everything.</li>
</ul>
<p>The amount is the same, so nothing feels off. That is the whole trick.</p>
<h2>Why the usual checks fail</h2>
<ul>
<li><strong>Looking carefully</strong> doesn't work when the edit is pixel-perfect.</li>
<li><strong>The file name and date</strong> prove nothing: they're trivially copied.</li>
<li><strong>"It came from their email"</strong> only means it came from <em>an</em> email that looks like theirs.</li>
</ul>
<p>The real question isn't "does this invoice look genuine?" but <strong>"is this exactly the file the supplier issued?"</strong> And that question has a mathematical answer.</p>
<h2>Verification with a fingerprint</h2>
<p>A cryptographic hash (SHA-256) turns any file into a 64-character fingerprint. Change one character of the IBAN and the fingerprint changes completely.</p>
<p>So the flow becomes:</p>
<ol>
<li>The supplier <strong>seals</strong> the invoice when they issue it: its fingerprint is registered.</li>
<li>The invoice travels with a <strong>verification link</strong>.</li>
<li>Before paying, you open the link or drop the PDF on the verify page. Your browser recomputes the fingerprint and checks it against the register.</li>
</ol>
<p>Match: it's byte-for-byte the invoice they issued. No match: someone changed something, even if you can't see what.</p>
<p>This is what we built <a href="https://trampto.com">TRAMPTO</a> to do. Sealing runs in the browser, so the invoice is never uploaded, and verifying is free and needs no account.</p>
<h2>What it doesn't replace</h2>
<p>To be clear about the limits:</p>
<ul>
<li>It proves the file <strong>hasn't changed since it was sealed</strong>. If the attacker controls the supplier's own system <em>before</em> sealing, the seal won't catch that.</li>
<li>It doesn't replace good habits: <strong>confirm any bank-detail change by phone</strong>, using a number you already had, never one from the email.</li>
</ul>
<p>But for the most common version of the scam, an edited PDF in transit, a fingerprint check turns "it looks right" into "it is right".</p>
<h2>Your turn</h2>
<p>Has your company (or a client) ever received an invoice with changed bank details? How did you catch it, or how did it slip through? I'd love to hear the stories.</p>
]]></content:encoded></item><item><title><![CDATA[Making PDFs tamper-evident in the browser with SHA-256 (and why we hash the sealed file, not the original)]]></title><description><![CDATA[Originally published on DEV. AI has made it trivial to edit an invoice, a quote or a contract so cleanly that nobody can spot the change by eye. A PDF has…]]></description><link>https://trampto.hashnode.dev/making-pdfs-tamper-evident-in-the-browser-with-sha-256-and-why-we-hash-the-sealed-file-not-the-original</link><guid isPermaLink="true">https://trampto.hashnode.dev/making-pdfs-tamper-evident-in-the-browser-with-sha-256-and-why-we-hash-the-sealed-file-not-the-original</guid><category><![CDATA[JavaScript]]></category><category><![CDATA[Security]]></category><category><![CDATA[webdev]]></category><category><![CDATA[pdf]]></category><dc:creator><![CDATA[TRAMPTO]]></dc:creator><pubDate>Fri, 13 Nov 2026 23:15:32 GMT</pubDate><content:encoded><![CDATA[<p><em>Originally published on <a href="https://dev.to/trampto_006da128a0ab6e1f6/making-pdfs-tamper-evident-in-the-browser-with-sha-256-and-why-we-hash-the-sealed-file-not-the-4k4c">DEV</a>.</em></p>
<p>AI has made it trivial to edit an invoice, a quote or a contract so cleanly that nobody can spot the change by eye. A PDF has no memory: the file name, the date and the layout all look the same after someone changes "1,800 €" to "4,800 €".</p>
<p>So instead of trying to <em>detect</em> a forgery by how it looks, we built <a href="https://trampto.com">TRAMPTO</a> to <em>prove</em> that a document hasn't changed, with plain math. This post walks through how it works, the one design decision that bit us, and what this approach does <strong>not</strong> prove.</p>
<h2>The idea in one line</h2>
<p>Compute a SHA-256 fingerprint of the document, register it, and give the recipient a link where they can recompute it themselves. Change one byte and the fingerprint no longer matches.</p>
<h2>Hashing in the browser with Web Crypto</h2>
<p>No libraries needed. The whole thing runs client-side with the Web Crypto API:</p>
<pre><code class="language-ts">export async function sha256Hex(bytes: Uint8Array): Promise&lt;string&gt; {
  // Copy only this view's bytes: a Uint8Array can be a window
  // into a larger ArrayBuffer, and hashing the whole buffer
  // would give you a different (wrong) fingerprint.
  const buffer = bytes.buffer.slice(
    bytes.byteOffset,
    bytes.byteOffset + bytes.byteLength
  ) as ArrayBuffer;
  const digest = await crypto.subtle.digest("SHA-256", buffer);
  return Array.from(new Uint8Array(digest))
    .map((b) =&gt; b.toString(16).padStart(2, "0"))
    .join("");
}
</code></pre>
<p>That <code>slice(byteOffset, …)</code> line looks redundant until it isn't. If the bytes come from a parser or a file reader that hands you a view over a bigger buffer, hashing <code>bytes.buffer</code> directly silently fingerprints the wrong data. Two codebases that both "compute SHA-256 of the file" will then disagree, and every verification fails.</p>
<p>Because the hash is computed on the device, <strong>the document itself never leaves the browser</strong>. Only the fingerprint, the file name and a seal ID go to the register.</p>
<h2>Sealing: two hashes, not one</h2>
<p>When a document is sealed, we compute two fingerprints:</p>
<ol>
<li><strong><code>contentHash</code></strong>: SHA-256 of the original file, before we touch it.</li>
<li>We add a tiny visual micro-seal to each page (about 6 mm, 15% opacity, bottom-right corner, respecting page rotation) and write <code>contentHash</code> into the PDF metadata.</li>
<li><strong><code>stampedHash</code></strong>: SHA-256 of the <strong>final sealed PDF</strong>.</li>
</ol>
<pre><code class="language-ts">const contentHash = await sha256Hex(pdfBytes);          // original
const pdfDoc = await PDFDocument.load(pdfBytes);
for (const page of pdfDoc.getPages()) drawDiscreetMark(page);
pdfDoc.setSubject(`TRAMPTO-HASH:${contentHash}`);
const sealedBytes = new Uint8Array(await pdfDoc.save());
const stampedHash = await sha256Hex(sealedBytes);       // public fingerprint
</code></pre>
<p>The public verification link is <code>/v/{stampedHash}</code>.</p>
<h2>The decision that matters: hash the <em>sealed</em> file</h2>
<p>It's tempting to make the public fingerprint the hash of the original. Don't. The file people actually send around is the sealed one. If the link pointed at the original's hash, a recipient holding the sealed PDF could never reproduce it.</p>
<p>The order is an invariant: <strong>hash original → seal → hash sealed</strong>. If you ever change the order, the seal drawing, or touch the PDF after computing <code>stampedHash</code>, every link you've already issued stops verifying. We treat that sequence like a database migration: it doesn't change casually.</p>
<h2>Verifying</h2>
<p>The recipient opens the link (or drops the file on the verify page). The browser recomputes SHA-256 of the file they have and looks it up in the register:</p>
<ul>
<li><strong>Match</strong> → the file is byte-for-byte the one that was sealed, and we show when it was sealed.</li>
<li><strong>No match</strong> → something changed, even a single byte.</li>
</ul>
<p>One detail worth copying: distinguish <strong>"not found"</strong> from <strong>"network error"</strong>. If the backend is down, we must not tell someone their genuine document is fake. A failed lookup throws and asks to retry; only a clean "no row" means "not verified".</p>
<h2>Other formats</h2>
<p>Word, PowerPoint, images and text are converted to PDF in the browser first (heavy libraries like <code>pdf-lib</code> and <code>mammoth</code> are loaded on demand with dynamic <code>import()</code> so the app opens instantly). Then the same sealing flow runs.</p>
<h2>What this does <em>not</em> prove</h2>
<p>Being honest about limits matters more than the feature list:</p>
<ul>
<li><strong>It proves integrity, not authorship.</strong> It shows the file hasn't changed since it was sealed. It doesn't prove who wrote it or that its content is true.</li>
<li><strong>It's not a qualified e-signature.</strong> It doesn't replace eIDAS qualified signatures or seals where the law requires them.</li>
<li><strong>The "when" relies on our register.</strong> The sealing date comes from TRAMPTO's database, not from a blockchain or a qualified timestamp authority.</li>
</ul>
<p>For quotes, contracts, invoices, reports and certificates, where the risk is "someone quietly changed the numbers", that's usually exactly the guarantee you need.</p>
<h2>Try it</h2>
<p><a href="https://trampto.com">trampto.com</a>: verifying is always free, and the first 3 seals are free. I'd love feedback from other devs, especially on the verification UX for people who have never heard of a hash.</p>
]]></content:encoded></item></channel></rss>