Card · vCard 4.0 · receipt on BSV

Ryan Wold
Founder, Civic Studio LLC

Builds feedback systems inside institutions. Commissioner, City of Vacaville Parks & Recreation Commission.

Vacaville, CA
ryanwold.net Receipt pending
Receipt
issued
2026-09-25 19:49:03 UTC
document
ryan-wold/20260925T194903Z.vcf
sha-256
4a23a44faac8b619e5805f7e3023c96184280ae782d5ea64bcc56f6092d10645
tx
not yet on the ledger
signed
no identity named
Not yet checked.
Add to contacts

A card with three entries

This card is a plain vCard, the format your phone's contacts app already reads. What's new is the receipt on the back.

  1. My record. Every version I issue is kept byte-for-byte and never rewritten.
  2. Your copy. Whatever you download is yours. You can check it against my record without asking me.
  3. The receipt. A transaction on the BSV ledger carries the card's fingerprint (its SHA-256), not the card. It proves this exact card existed, unaltered, by a certain block. It's signed by the BAP identity the card names. The signing keys live in my wallet and can rotate without changing who the identity is.

This is Ian Grigg's triple-entry accounting applied to a business card. Two parties' records, plus a third that neither can quietly edit.

Your contact details aren't on the public card, and nothing personal is on the ledger. You don't need a wallet to read or check it. The signature is checked against the BAP index at the receipt's block, so a key I've since rotated still counts for what it signed.

Check a copy you hold

Choose a .vcf you downloaded earlier. It's hashed in your browser and never uploaded.

Check it without this page

curl -s https://ryanwold.net/ryan-wold/20260925T194903Z.vcf | shasum -a 256
# expect 4a23a44faac8b619e5805f7e3023c96184280ae782d5ea64bcc56f6092d10645

Receipts follow a small, readable format: receipts/v1. The full ledger of versions is at ryan-wold/receipts.

Versions