Context & Problem
Educational institutions and professional organizations struggle with the secure issuance and verification of certificates. Centralized databases are susceptible to tampering, data loss, and siloing, making background checks slow and expensive.
I built Pindown as Co-founder and Head of Product & Technology at Trizwit Labs, a product studio delivering software for international clients across five engagements. Pindown was conceived to give institutions a trustless environment for document verification - an immutable ledger for credentials where validity could be proven cryptographically without depending on a single central authority.
Going in, three constraints shaped the product: blockchain technology carries high friction for non-technical users, so the experience had to feel like an ordinary Web2 application; smart contract deployment (gas) costs meant the architecture had to stay economical at bulk certificate-issuance volume; and the system needed to hold up as decentralized storage standards continued to evolve.
Key Product Decisions
- Abstract the blockchain, over exposing it. I chose to hide private keys, gas limits, and chain mechanics behind a familiar dashboard rather than surface Web3 primitives to users. Tradeoff: more engineering effort up front to build the abstraction layer. Result: an admin experience that required no crypto literacy - a hard requirement for institutional buyers.
- Hybrid on-chain/off-chain storage, over storing files fully on-chain. I chose to store only the cryptographic hash on-chain while the encrypted file lived on IPFS, rather than pay to store full documents on-chain. Tradeoff: an added dependency on IPFS availability. Result: costs that stayed viable at bulk-issuance volume instead of being cost-prohibitive.
- Build for institutional admins, over individual end-users. I chose to prioritize bulk-import tooling and role-based access control for university administrators over a polished individual-user flow. Tradeoff: less initial appeal to individual credential-holders. Result: the workflow that actually drove institutional adoption.
Execution
- Frontend Dashboard: Built with Next.js and Tailwind CSS, providing a responsive admin panel for bulk certificate generation.
- Decentralized Storage: Documents and metadata were pinned to IPFS, keeping files distributed and highly available.
- Smart Contracts: Deployed optimized Solidity contracts on Ethereum-compatible chains as the single source of truth for the hash of issued certificates.
- Relayer Network: Implemented meta-transactions so organizations could issue credentials and cover network fees seamlessly for the end user.
Delivered as part of a five-engagement client roster at Trizwit Labs, with the "abstract the blockchain" strategy driving every architectural choice above.
Outcomes & Lessons
Shipped Pindown from zero to production and onboarded 10+ early users and organizations. Lesson: Web3 adoption is bottlenecked by UX, not cryptography - no matter how elegant the underlying protocol, if an administrator can't issue a batch of 500 certificates in exactly three clicks, the product fails in a B2B setting.