把链上网站，交给普通浏览器。

Gateway 为 BSC、X Layer 和 Base 上的 TapeKit 静态网站提供 HTTPS 入口。文件仍由你发布到链上；网关核验后缓存固定版本，访客无需钱包或 gas。

第一次发布

在项目设置选择网络及自己的 CPU、NFT。已有站点可从「生态与链上站点」导入。导入只创建归档，不转移 NFT。
在部署详情完成发布检查。新文件先执行链上发布、读回与原生激活；已上链的相同文件可直接接入。
打开 Gateway，点击「核对持有人与发布目标」。检查钱包、链、项目、版本和文件清单。
点击签名发布。钱包签署的是五分钟有效的归属证明，不是付款交易。两个独立 RPC 会读取同一区块的文件，逐一核对内容哈希。
成功后分享「稳定入口」。地址会跳转到独立版本网址，避免新旧脚本和页面混用；「核验清单」可以独立下载。

绑定自己的域名

在「域名」登记普通子域名，访问服务选 TapeNow Gateway。依次准备域名与证书、检查 DNS、确认配置，再核验启用。也可在自己的 DNS 服务商手动添加记录。Cloudflare 可能稍后返回额外证书 TXT 记录；证书未就绪时重新准备并检查 DNS，再重试核验。

需要域名控制权、有效证书和当前 NFT 归属全部通过。现阶段客户域名也会跳转至独立版本网址，不支持任意裸域或通配域名自动接入。

更新、恢复和停止

更新：重新导入与批准，写链后再发布 Gateway。外部改写链上文件不会自动替换已批准的网站；「检查归属与链上更新」会报告差异。
恢复：在历史部署选择签名恢复该 Gateway 版本。切换的是稳定入口，业务数据库和链上容器不会随之倒退。
停用历史缓存：旧网址停止服务，链上副本保留。当前版本不能直接停用；可以先切换版本或暂停整个项目。
暂停/到期：项目暂停、芯片归属变化或协议激活过期会停止入口。节点临时不可用时仅在现有核验租约内继续提供旧缓存，超时拒绝访问。

当前限制

每站点最多 500 个文件、10 MiB，总计最多 20 个活动网关版本。它服务静态网站，不替代 SSR、业务 API 或数据库。当前为邀请 Beta、小规模验收，未承诺生产 SLA。供应商配额共享，免费名额保护不是账户总账单硬上限。

给开发者和代理

公开能力接口 /api/gateway/capabilities；站点清单位于 /__tapenow/manifest.json。下面的 SDK 可读清单与校验文件，也提供受登录、CSRF、项目角色控制的发布/恢复/域名接口。钱包签名必须由调用方明确取得。

WebMCP：后端和 SDK 可以作为工具接入基础，但当前没有注册浏览器原生 WebMCP 工具，能力接口会返回 webmcpRegistered:false。不要把清单当成无需信任网关的链轻客户端证明。

Your on-chain site. An ordinary browser.

Gateway serves TapeKit static sites on BSC, X Layer and Base over HTTPS. You publish files on-chain; Gateway verifies and caches a pinned version. Visitors need no wallet or gas.

Publish your first entry

Select your chain, CPU and NFT in project settings. Import existing sites through the ecosystem page. Importing creates an archive; it does not transfer the NFT.
Complete the release review. New files must be published, read back and activated on-chain first. Existing matching files can connect directly.
Open Gateway and check the owner and target. Review wallet, chain, project, release and file manifest.
Sign and publish. The ownership message expires after five minutes and is not a payment. Two independent RPC operators attest files at the same block; actual bytes must match their hashes.
Share the stable entry. It redirects to a separate version URL to avoid mixing old and new assets. Download the verification manifest separately.

Connect your own domain

Add a normal subdomain and choose TapeNow Gateway. Prepare the hostname and certificate, review DNS changes, confirm them, then verify and enable. You can also add the records at your own DNS provider. Cloudflare may return additional certificate TXT records later; prepare again, review DNS and retry verification.

Domain control, TLS and current NFT ownership must all pass. Custom domains also redirect to a separate version URL. Arbitrary apex and wildcard onboarding is not supported in this release.

Update, restore and stop

Update: import, approve, write on-chain and republish. External on-chain edits do not silently replace the approved website; the ownership/content check reports differences.
Restore: select a historical deployment and sign to restore its Gateway version. This switches the stable entry; it does not roll back the on-chain container or business database.
Retire old cache: its old URL stops serving, while on-chain copies remain. Switch away from the current version before retiring it, or suspend the project.
Suspension and expiry: project suspension, changed ownership or expired protocol activation stops access. Temporary RPC failures permit cached delivery only within the remaining verification lease.

Current limits

Up to 500 files and 10 MiB per site, with 20 active Gateway versions per project. Static sites only; SSR, APIs and databases remain external services. This invitation beta has limited acceptance coverage and no production SLA. Shared provider quotas and the included-hostname guard are not account-wide billing caps.

Developers and agents

Read /api/gateway/capabilities and the site’s /__tapenow/manifest.json. The SDK reads manifests, verifies downloaded bytes and wraps session/CSRF/role-protected publication, recovery and domain APIs. Wallet signatures must be obtained explicitly by the caller.

WebMCP: these APIs provide an integration foundation. Native browser tools are not registered; capabilities report webmcpRegistered:false. The manifest is a gateway attestation, not a trustless blockchain light-client proof.

JavaScript SDK

import { readGatewayManifest, verifyGatewayFile,
         createGatewayClient } from '/sdk/tapenow-gateway.mjs';

const proof = await readGatewayManifest(versionUrl);
for (const file of proof.files) {
  await verifyGatewayFile(versionUrl, file);
}
// In the signed-in TapeNow origin:
const session = await (await fetch('/api/session')).json();
const client = createGatewayClient({ csrf: session.token });
const challenge = await client.prepare(releaseId, walletAddress);
// Show the exact challenge.message and ask the wallet to personal_sign it.
await client.publish(releaseId, { challengeId: challenge.id, signature });

WebMCP · Receipt verification / 回执验签