TRADE-OFFS
What I cut to make proof readable
Every decision here traded reach for restraint. A verification page is more useful the more openly it opens, more convincing the more it is branded, and easier to ship the narrower its scope and each of those pulls against either privacy, credibility, or the moment when the receiver actually needs it.
WHAT I CHOSE | WHAT I CUT | WHY |
|---|---|---|
Verification scoped to sender and receiver | A link anyone can open | An open link turns a payment confirmation into a lookup tool. Chain data is traceable regardless and we never claimed otherwise, but the product should not be the thing that makes it easy. |
Hash moved to walllet's explorer | The hash on the receipt | Receipts are for reading, hashes are for verifying, and those are two different people. Crypto-natives lose nothing, one layer down they get the hash and a route to the chain's own explorer. |
Confirmed transactions only | Pending and failed states | A scope decision to ship, and the weakest one I made here, those are the states where a readable page is worth the most. |
Verification data first, mark last | A neutral, unbranded receipt | The shared receipt is the only thing walllet sends to people who don't use it. Branding it is fair; leading with the branding would make proof look like an advert. |
MY CONTRIBUTION
What I owned on Trust check?
WHAT I OWNED
Trust check as a concept and the argument for removing the hash from the receipt. The receipt's structure, amount and asset first, parties, then status, time and fee in dollars, then verification. The QR alongside the tap target, because proof is often held up to someone standing next to you rather than sent. The shared image and the decision about what it carries. The relationship between walllet's explorer and the chain's, so nothing was hidden, only reordered.
A receipt is for reading. A hash is for verifying. Those are two different people.
DESIGN DETAIL
How the receipt is built to leave the app?
The receipt reads top to bottom as a document rather than a confirmation screen: what moved, between whom, whether it landed, when, and what it cost the fee in dollars, named with the token it was paid in. Verification sits at the bottom as its own block, tappable and scannable, so the same screen serves someone reading it on their own phone and someone showing it across a table.
The shared version is the same document without the interface around it. Nothing that matters for verification is lost in the handoff, which is the point a screenshot of a confirmation screen is not evidence, but a receipt that carries its own verification is.