Social Blockchain Network

The problem

Exploring what a social feed looks like when posts, reactions and tipping are on-chain primitives instead of rows in a database — including what that does to identity, ownership and creator payouts.

What I owned

• Product concept, architecture and implementation end to end
• The SocialPosts Solidity contract and its test suite, written with Hardhat and OpenZeppelin
• Wallet-based identity and on-chain post minting
• Wallet-signed likes, comments, saves and follows, plus direct creator tipping and withdrawal
• In-browser media preparation before upload — image cropping and ffmpeg.wasm video trimming
• IPFS media storage via Pinata, and subgraph-driven application data

Technical challenges

• Designing a feed UX where every write (post, like, comment, tip) is a signed on-chain transaction with real latency
• Indexing on-chain activity into a readable feed via subgraphs instead of a traditional database
• Keeping the feed usable when an indexer lags or goes down, without a database to fall back on
• Running the same application logic consistently across three separate testnets

Engineering decisions

• Posts as NFTs and reactions as signed on-chain interactions, rather than bolting a wallet onto a conventional backend
• IPFS for media so post content isn't dependent on centralized storage
• Subgraph reads with a per-chain fallback to raw event logs over RPC, so one indexer outage degrades the feed instead of emptying it
• Deployed to Base Sepolia, Ethereum Sepolia and BSC Testnet as a multi-chain testbed before any mainnet decision

Technology