Dwelp

Problem Statement

Dwelp is a decentralized application that combats the growing issue of fake certificates, circulars, and degrees by enabling institutions to digitally sign official PDFs using blockchain. These documents can then be verified by anyone — no account, no login, no middleman.Think of it as a trustless, public notary for the digital world.🚀 How It WorksAdmin Dashboard (Issuer Portal)Accessible only by the deployer's wallet (contract owner)Uploads and signs PDF documents using a private keyStores signed file data on IPFS via PinataSaves the cryptographic signature and file hash on-chainVerification Portal (Public Portal)Open to any user without loginAnyone can upload a document and check if it’s an officially signed fileMatches signature using the stored hash on-chain and public key from contract💡 Why Dwelp? "The institute will remain closed tomorrow!" We’ve all received such messages — some true, many fake. Dwelp eliminates the doubt. With on-chain signatures and IPFS storage, official documents can be verified instantly and trustlessly.🔐 Key FeaturesInstitutional PDF signing using private-public key cryptographyReal-time blockchain-based signature verificationAdmin-only contract access via wallet-based controlTamper-proof document storage on IPFS (via Pinata)Public portal for open document verificationSecure UI with RainbowKit and wallet loginFully decentralized architecture — no centralized backendMobile-responsive and production-ready🛠 Tech StackFrontendTypeScript · React · Tailwind CSSWagmi · Viem · RainbowKitSmart Contracts & InfraSolidity · FoundryPolygon Amoy (testnet)Infura RPCPinata + IPFS for file storageOpenSSL + crypto module for PDF signing

Solution

This project uses Ethereum and Polygon (Layer 2) for storing the hash and public key on-chain while the PDF/Document itself is stored on Pinata. The CID is then stored on-chain along with the hash, and signature. So when the admin uploads a PDF, the document gets hashed, signed and the PDF/doc is uploaded on Pinata At the verification portal, the hash is again taken, searched through the contract. If the hash is found, verified by the public key, the document is shown verified.