Launching today
SwanShare
Cryptographically verifiable credentials & e-signatures
7 followers
Cryptographically verifiable credentials & e-signatures
7 followers
SwanShare lets any organization issue tamper-evident, publicly verifiable credentials and e-signatures. Each credential is signed with RSA-PSS, hashed with SHA-256, Merkle-batched, and anchored to a hash-chained ledger (optionally a public blockchain or OpenTimestamps). Anyone can verify authenticity for free — no account required. Exports W3C Verifiable Credentials & Open Badges 3.0. E-sign with tokenized links and sealed PDFs that include a certificate of completion.
Hey everyone! 👋
I built SwanShare after seeing how easy it is to fake a certificate, diploma, or signed document — and how hard it is for the receiver to actually check if one is real. Most "verification" today is just a PDF you have to trust, or a closed portal only the issuer can confirm.
Who it's for:
Training providers, bootcamps & universities issuing certificates and diplomas that employers can instantly trust
Associations & licensing bodies issuing professional licenses/memberships that stay verifiable (and revocable) over time
HR & ops teams that need signed offer letters, contracts, and compliance docs with proof they weren't altered
Anyone receiving a credential — a recruiter, admissions officer, or client — who needs to confirm it's real in seconds
Why it's needed: credential fraud is cheap and everywhere, while checking authenticity is slow, manual, or impossible. Issuers lose trust in their own certificates, and receivers have no independent way to verify them.
How SwanShare solves it: every credential and e-signature is cryptographically signed (RSA-PSS), hashed (SHA-256), and anchored to a tamper-evident ledger — and anyone can verify it for free, no account needed. It exports open standards (W3C Verifiable Credentials, Open Badges 3.0), so you're never locked in.
Along the way it grew from "just credentials" into e-signatures too — sealed PDFs with a certificate of completion, plus optional anchoring to a public blockchain for extra-strong proof.
Would love your feedback on the verification flow and what credential types you'd want supported next!