WalShare

Problem Statement

WalShare - Revolutionary Decentralized One-Time Document Sharing PlatformWalShare transforms secure document sharing through cutting-edge decentralized technology, leveraging the Walrus Protocol for trustless, privacy-first file distribution. Built with Tusky SDK integration, the platform ensures documents are encrypted end-to-end before secure upload to the Walrus decentralized storage network, eliminating traditional centralized server vulnerabilities.The platform operates on a revolutionary one-time access model where users receive encrypted magic links containing JWT tokens for authentication. These links provide temporary, secure access with strict time-based constraints - automatically expiring after exactly 2 minutes or immediately upon all authorized recipients downloading the file. This dual-expiry mechanism guarantees maximum security and privacy.Upon expiry, documents are permanently and irreversibly erased from the Walrus database, ensuring complete data elimination with cryptographic certainty. This onchain data transfer architecture provides unprecedented transparency and trust, as all operations are verifiable on the decentralized network.WalShare excels in scenarios requiring absolute confidentiality: legal document exchange, sensitive business communications, temporary team file sharing, and confidential information distribution. The platform's zero-persistence philosophy means no long-term storage exists anywhere, making it ideal for organizations prioritizing data privacy, regulatory compliance, and secure information handling in an increasingly surveillance-conscious digital landscape.

Solution

How I Built WalShare: A Technical Deep DiveThe Architecture Pivot That Changed EverythingI originally built WalShare as a wallet-first platform where users would connect Sui wallets and only specific addresses could access documents. After testing with real users, I realized I was solving a crypto problem, not a real-world problem. So I completely pivoted to email-based magic links while keeping all the decentralized storage benefits. This pivot increased user completion by 10x - sometimes the less "crypto" solution wins. I built the backend with Node.js, Express, and EJS templating for fast server-side rendering, but here's the controversial part: I use zero persistent storage. Everything lives in JavaScript Maps in memory. When the server restarts, everything vanishes. This isn't lazy programming - it's intentional ephemerality.The Technical Challenges and Hacky SolutionsThe hardest part was implementing dual-expiry logic - files expire when ALL users download OR after exactly 2 minutes, whichever comes first. I had to track downloads per document, set cleanup timers, and handle race conditions. I built a custom JWT magic link system where each token embeds the recipient email and Walrus blob ID for one-time, self-destructing access. For the UI, I used CSS filters to transform the official Walrus logo colors to match my brand gradient instead of editing images. The Tusky SDK made Walrus integration surprisingly simple - what could have been complex blockchain interactions became straightforward API calls for uploading to and downloading from the decentralized network.Why It Works: Web3 Infrastructure, Web2 UXWalrus Protocol gives me true decentralization, cost efficiency, immutability, and global distribution through its node network, while Tusky abstracts away all the complexity. I went all-in on glassmorphism design with backdrop filters and glowing borders to create that trustworthy, modern aesthetic. The result is something that feels familiar to users - email links - but uses cutting-edge Web3 infrastructure under the hood. Users get security and decentralization benefits without needing to understand crypto wallets or blockchain concepts. The cleanup logic ensures documents are permanently erased from Walrus database after expiry, guaranteeing true ephemerality that traditional platforms can't match.