Fully on-chain storage
Every byte of the site — HTML, scripts, styles, images, fonts — lives on BNB Chain. No https:// external references are allowed; all assets must be self-hosted.
Work 03 / TapeKit
TapeKit is an open-source browser kernel built on the TapeOut protocol: every byte of a website lives on BNB Chain, and the browser reads and verifies it directly from the chain, with no server, IP, or domain in between.
Core idea: as long as BNB Chain exists, your website stays reachable. No hosting bill, no DNS hijack, no single point of failure.
01 / Concept
TapeKit is an open-source browser kernel released by founder Blonskr on 2026-09-16, built on the TapeOut protocol. It lets browsers or apps read website content directly from BNB Chain — no cloud hosting, no DNS resolution. Users open on-chain "decentralized websites" (DeWEB) through addresses like tape://4246.0 or #4246@0.
02 / Core features
Every byte of the site — HTML, scripts, styles, images, fonts — lives on BNB Chain. No https:// external references are allowed; all assets must be self-hosted.
The browser reads each file from at least 2 independent nodes and compares it against the SHA-256 hash recorded on-chain. Any mismatch is rejected outright, guaranteeing the content hasn't been tampered with.
No domain, no DNS, no centralized server in the path. Any BNB Chain node — public RPC or self-hosted — is enough to reach the site, so no single party can take it down.
Every version is permanently stored on-chain. It won't disappear because a server lease expired, a company folded, or someone deleted it. Older versions remain retrievable too.
03 / Access methods
TapeKit supports three levels of addressing, from a friendly on-chain name down to a raw contract address:
tape://4246.0
#4246@0Costs 0.08 BNB per 30 days, renewable up to 120 months. The fee is paid to the container and the name activates automatically.
processor contract address + #IDPoints directly at the container's tokenId — suited to developers and technical users.
0x86DD…eA95The lowest-level access method: the container's raw Ethereum address (an ERC-6551 account).
tape:// support in mainstream browsers.04 / Publishing flow
Publishing a decentralized website takes three steps: prepare the files, upload them to the chain, activate a name.
Build a plain static folder with index.html at the root; every asset uses a relative path. Filenames must be Unicode NFC. Precompute the SHA-256 hash of each file.
Either use the HashPort console to pick a circuit, upload the folder, and sign the transaction, or call the contract directly: putFile writes the first 24KB, appendChunk appends the rest (up to 8.4MB per file).
Pay 0.08 BNB per 30 days (up to 120 months) and call DomainBinding.bind("name", containerAddress, months). The fee goes to the container and the name activates automatically.
24KB per chunk, 8.4MB max per file (350 chunks), up to 5,000 paths in the manifest, 32MB / 2,000 files for a preview site. No external https:// references or runtime fetch/XHR are allowed.
05 / Apps & tools
These aren't "websites built with TapeKit" — they're development frameworks or tools that consume and integrate the tape:// protocol as a capability, listed by release date.
Third-party developer @Xiao_zhanyang released TapeOut.link, the first ecosystem directory site with the TapeKit kernel built in: its search box accepts a tape:// address directly (e.g. 4246.0.tape) or a site name, resolving and opening the on-chain site right in the browser. The site organizes on-chain sites into categories such as official entry points, on-chain data, third-party exchanges, and circuit mining, and the author says it will keep indexing all DeWeb sites going forward.
What it shows: rather than publishing only one DeWEB site, TapeOut.link turns tape:// resolution itself into reusable directory infrastructure — treating the protocol as a development framework to build on, not just a one-off publication.
Third-party developer @spongemochi (also the author of TAPE STRIKE) released tapeout.space: a "circuit map" showing every website on TapeOut, with data auto-refreshed from the chain every 10 minutes, plus a community gateway that lets containers not yet on the official tapekit.org domain be reached through tapeout.space instead, along with a one-click on-chain publishing tool. The author says it was built to solve the problem that "there was nowhere to see all existing on-chain sites at a glance."
What it shows: like TapeOut.link, this turns discovery and access for the tape:// ecosystem into reusable infrastructure rather than being a single website's output.
06 / Browse DeWEB
DeWEB sites will keep appearing, changing, and going offline, so this page no longer maintains a complete list that would quickly become stale. Use the external directory below to discover sites that are currently available.
07 / Milestones
This tracks only TapeKit's own major events, in chronological order; new official announcements or version updates will be added here as they happen.
Founder Blonskr released TapeKit, an open-source browser kernel built on the TapeOut protocol, under the MIT license with the full source on GitHub. Every file of a website is stored on BNB Chain, and users read and verify content directly from the chain through the tape:// protocol — marking TapeKit's official launch.