Work 03 / TapeKit

A fully decentralized website

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.

Related infrastructure: TapeSend
TapeKit reads and verifies DeWEB content across chains; TapeSend adds cross-chain, end-to-end encrypted messaging on top of the same circuit-container identity. It is a standalone product, not a third-party application case. Explore TapeSend →

01 / Concept

What is TapeKit

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.

The core difference from traditional hosting: a normal website needs a server you keep paying for, a DNS entry, protection against DDoS, and a database that can be deleted. A TapeKit website is written permanently onto the chain — publish once, and it stays reachable forever, immune to a company shutting down or a policy changing.

02 / Core features

Four properties, one design

100% on-chain

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.

Multi-node verification

Byte-for-byte SHA-256 checks

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.

Censorship-resistant

No middleman service

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.

Permanent

Content stays forever

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

Three address formats

TapeKit supports three levels of addressing, from a friendly on-chain name down to a raw contract address:

1. On-chain name (most common)

tape://4246.0
#4246@0

Costs 0.08 BNB per 30 days, renewable up to 120 months. The fee is paid to the container and the name activates automatically.

2. Circuit container ID

processor contract address + #ID

Points directly at the container's tokenId — suited to developers and technical users.

3. Container contract address

0x86DD…eA95

The lowest-level access method: the container's raw Ethereum address (an ERC-6551 account).

Browser support: currently requires the TapeKit browser extension (Chrome MV3) or a Service Worker gateway. The longer-term goal is native tape:// support in mainstream browsers.

04 / Publishing flow

How a site owner publishes on-chain

Publishing a decentralized website takes three steps: prepare the files, upload them to the chain, activate a name.

Step 1

Prepare static files

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.

Step 2

Upload to BNB Chain

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).

Step 3

Activate an on-chain name

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.

Limits

Technical constraints

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

Apps and tools built on TapeKit

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.

01 · Ecosystem directory

TapeOut.link · a directory with built-in tape:// resolution · 2026-09-16 13:20 UTC

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.

View announcement → · Open TapeOut.link →

02 · Directory + gateway

tapeout.space · an on-chain site directory and community gateway · 2026-09-18 19:06 UTC

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.

View announcement → · Open tapeout.space →

06 / Browse DeWEB

Use the continuously updated site directory

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.

Browse DeWEB sites →
Open web.tapeout.link
This directory is maintained by a third party. Its listings, ordering, and site availability are not endorsements by this site. Verify a site and any transaction details before connecting a wallet.

07 / Milestones

TapeKit 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.

  1. TapeKit open-sourced

    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.

    View announcement → · Open GitHub repo →