ProjectsDecentra-Blog
01 / Project Details
LiveDecentralized blogging platform
Decentra-Blog
DecentraBlog combines wallet-based identity, IPFS content storage, on-chain publishing actions, and an indexed read layer into a single product experience. Instead of forcing users to choose between verifiability and usability, it treats blockchain as the trust layer and a modern web stack as the experience layer.
RoleFull-Stack Web3 Engineer
Duration4 Weeks
ClientPersonal Project
Year2026
Project Summary
A Web3-first publishing product designed to make decentralized blogging feel fast, credible, and usable in practice.
02 / Snapshot
Core Model
On-chain actions with off-chain indexed reads
Publishing Flow
Wallet-authenticated post creation, editing, likes, and comments
Content Layer
IPFS-backed post and comment metadata with cover image support
Reader Experience
Fast feed, full-text search, profile views, comments, and version history
03 / Overview
Building a decentralized publishing experience that feels credible, fast, and usable.
DecentraBlog was shaped as a product that closes a common gap in Web3 applications: many systems can prove ownership and state changes, but few make everyday publishing feel smooth enough for real readers and authors. This project solves that by splitting responsibilities intelligently across contracts, IPFS, an indexer, and a polished App Router frontend.
Challenge
The core challenge was designing a blog product that preserved Web3 credibility without inheriting Web3 friction. Storing everything directly on-chain would be expensive and awkward for content-rich posts, while relying entirely on off-chain systems would weaken the product’s trust story. The other challenge was UX: wallet connection, signed sessions, transaction confirmation, indexing delay, and eventual consistency all had to be handled without making the interface feel brittle or confusing.
Solution
I designed DecentraBlog as a hybrid architecture. Smart contracts store the minimum durable state and emit the product events that matter. Post and comment bodies live in IPFS. A Ponder-powered indexer transforms chain activity into a query-optimized Postgres read model. On top of that, the Next.js web app provides a clean publishing and reading experience with wallet-aware authentication, graceful loading states, searchable content, responsive layouts, profile analytics, edit history, and post-action indexing feedback.
04 / Stack & Scope
What shipped
Tech Stack
Next.jsReactTypeScriptTailwind CSSWagmiViemWalletConnectPonderPostgreSQLFoundrySolidityIPFS / Pinata
Team Context
Solo Full-Stack Web3 Engineer
Deliverables
- Editorial, card-based feed experience
- Wallet-authenticated publishing flow for new posts
- Cover image upload and metadata publishing to IPFS
- On-chain post creation, editing, likes, and comments
- Version-aware post detail pages with archived snapshots
- Full-text search with pagination
- Public author profile pages with aggregated stats
- Reward token support for engagement incentives
- Health monitoring and production-friendly service boundaries
Key Highlights
- Hybrid trust model that keeps blockchain usage meaningful without sacrificing usability
- Version history that preserves earlier post states instead of overwriting content blindly
- Indexed read layer that makes search, profiles, and feeds fast enough for real product use
- Wallet + session UX that treats authentication as a product flow, not just a technical requirement
05 / Process
From product framing to final polish.
Step 01
Product Framing
Defined the product around a simple question: what should be verifiable on-chain, and what should remain flexible off-chain? That framing shaped the entire system. Contract responsibilities were kept lean and durable, while rich content and UI complexity were handled where they belong: IPFS, indexed storage, and the application layer.
Step 02
Identity & Publishing UX
Built a wallet-driven access model with SIWE-style signature verification, httpOnly session cookies, and guarded publishing routes. This made the authoring experience feel coherent: connect wallet, sign in, upload assets and metadata, submit the on-chain action, then wait for indexing with explicit product feedback instead of silent uncertainty.
Step 03
Event-Driven Read Architecture
Implemented a Ponder indexer that listens to publishing, update, like, and comment events, fetches metadata from IPFS, and writes a query-friendly Postgres projection. This unlocked the product features that matter for day-to-day use: fast feed loading, version-aware post retrieval, profile statistics, engagement counts, and search.
Step 04
Interface Polish & Reliability
Refined the experience around real product edges: responsive layouts, comment flows, search states, mobile navigation, wallet drawers, index polling after transactions, health checks, and resilience around session mismatch or delayed chain/index updates. The goal was not just to make the app work, but to make it feel intentional.
06 / Gallery
Selected product views
07 / Closing Notes
This project focuses on making decentralized publishing feel like a real product—not just a technical proof of concept.
Product Value
Turns decentralized publishing into a cleaner, faster, more understandable experience
Technical Strength
Connects contracts, IPFS, indexing, database reads, and modern frontend UX into one coherent system
Portfolio Signal
Shows end-to-end ownership across architecture, implementation, reliability, and product presentation
08 / Next Project