DeHost — hosting that can't be taken down.

01What it does

DeHost is a decentralized hosting platform that lets users publish websites and files without relying on traditional servers or centralized providers. Content is stored and served through blockchain infrastructure, making it resistant to takedowns and single points of failure. There's no cloud provider between the site owner and the reader; there's no server you can pressure to remove content; there's no single machine whose failure takes the site offline.

End-to-end, the flow is: connect a wallet, register a blockchain domain, publish a file or a full static site, and the content is now reachable through the decentralized network under that domain. Owners manage everything — domains, deployed sites, wallet identity — through a single dApp.

02The frontend build

SvelteKit + Svelte 5, TypeScript throughout

The application is built on SvelteKit with Svelte 5 components and TypeScript across the codebase. SvelteKit handles routing, layouts, and static generation for the shell; the wallet-connected surfaces are reactive Svelte 5 components with fine-grained state. Vite powers the build for fast local iteration.

Reusable component library

Rather than building each screen from scratch, the frontend is composed from a hand-built component library — form inputs, wallet-aware primitives, transaction-status displays, empty states, responsive layouts. Everything is Tailwind-styled so theming and density adjustments live in one place, and every component is designed responsively rather than as a desktop layout with mobile fixes bolted on.

Production-grade UX and SEO

SEO metadata, canonical URLs, and preview cards are wired into the SvelteKit shell so shared links behave properly in Twitter, LinkedIn, and messaging apps. Loading and error states are first-class — every async operation (wallet connect, contract read, publish confirmation) has its own explicit UI rather than a spinner and a hope.

03Wallet, chain, and account abstraction

Multi-wallet onboarding

Users can sign in with the wallets they already have — the standard EIP-1193 injected wallet path — but the interesting bit is account-abstraction sign-in for users who don't want to install a browser extension. Account abstraction (ERC-4337-style) lets a user create a smart-contract wallet from a familiar credential and interact with the chain without ever seeing raw seed phrases. That path unlocks the app for users who aren't already crypto-native.

If your dApp only works for people who already own a MetaMask install, you've decided in advance that no one new is coming.

On-chain domain registration and management

Domains are on-chain assets, registered and managed through the app. The frontend handles domain lookups, availability checks, registration transactions, ownership transfers, and pointing a registered domain at a specific piece of content. The user sees a familiar "domains dashboard" UI; underneath, every action is a chain interaction with clear pre- and post-transaction states.

Base chain deployment

The app is deployed on the Base chain — currently on Base testnet at dehost.io, with the same code path ready to run against mainnet when the smart-contract side is ready. Network switching is automatic where possible and prompted where it can't be; the UI always shows which network the user is currently interacting with, and destructive actions confirm the network before firing.

04Status

Live on Base testnet at dehost.io. The full application surface — wallet onboarding, domain registration and management, file and site publishing, transaction status flows, responsive design across breakpoints — is shipped. Co-built with a colleague; ongoing work continues on the smart-contract and infrastructure side; mainnet cut-over comes later.