先选一条路Choose your route
从零开始，最短路径是：邮箱或钱包登录 → 创建示例项目 → 查看文件 → 创建私有预览 → 打开并检查。全程不需要钱包或付费交易。已有网站可以直接导入构建包；上链只在你决定正式发布时才需要。For a first run: sign in with email or wallet → create a sample project → inspect its files → create a private preview → open and check it. No wallet or paid transaction is needed. If you already have a site, import its built files instead. Onchain steps come when you choose to publish.
先记住这几个词The few terms you need
- 构建包：能直接打开的静态网站文件，根目录有
index.html；源码 ZIP 不一定是构建包。 - 部署 / 版本：某一刻固定的一组文件；导入后先归档，不会自动公开。
- 预览：给自己或测试者看的独立地址，可设置密码与有效期；它不等于正式发布。
- 芯片与容器：你持有的 TapeOut 处理器芯片用于证明权限，容器承载网站文件。CPU Index 和 Token ID 帮 TapeNow 找到正确的链上目标。
- 原生入口：TapeKit 直接按链上记录访问；Gateway：核验链上文件后通过普通 HTTPS 提供固定版本。
- 稳定入口：当前会跳转到独立版本网址；每次切换后浏览器地址与本地存储来源可能变化。
费用由谁收：本地准备和额度内预览不需链上交易；GitHub Actions、Cloudflare、数据库等用量由你自己的供应商账户结算。芯片/容器/原生访问激活的费用按上游页面和合约提示支付，链上写入的 gas 支付给相应网络，不是 TapeNow 收取的激活费。每条链的实际金额与有效期以费用说明及钱包确认页为准。
目前为限量公开测试，受邀账号继续可用。普通 A 账号可以使用官方/已验证第三方入口，或自己的 Cloudflare；TapeNow 免激活公开托管和 Pro 尚未开放。HashPort 已核验路线只在 BSC。完整兼容范围以操作界面的实际能力与A 测试说明为准。
- Build artifact: static files ready to open, with
index.htmlat the root. A source-code ZIP may not be a build artifact. - Deployment / release: a fixed set of files at one point in time. Importing archives it first; it does not publish it automatically.
- Preview: an independent URL for you or testers, optionally password protected and time limited. It is not a live release.
- Chip and container: your TapeOut processor chip proves authority; the container stores the website files. CPU Index and Token ID identify the onchain target.
- Native entry: TapeKit reads chain records directly. Gateway: verifies the files, then serves a pinned version over ordinary HTTPS.
- Stable entry: currently redirects to a separate version URL; switching may change the browser origin and its local storage.
Who charges you: preparing files and previews within the allowance do not require an onchain transaction. GitHub Actions, Cloudflare and database usage belongs to your own provider accounts. Chip, container and native access activation fees follow the upstream page or contract; write gas goes to the corresponding chain. These are not TapeNow activation fees. Check the fee guide and wallet prompt for current amounts and expiry.
This is a limited public beta; invited accounts remain supported. Ordinary A accounts can use official or verified third-party entry points or their own Cloudflare; TapeNow's public activation-free hosting and Pro are not open. HashPort has been verified only on BSC. Check the current UI and A beta policy for availability.
遇到问题，先查这里When something goes wrong
| 看到什么 | 下一步 |
|---|---|
| 收不到验证码 | 确认邮箱已受邀、检查垃圾箱和邮件地址；不要连续反复发送。请邀请人检查邀请状态。 |
| ZIP 导入失败 | 确认是构建产物，根目录有 index.html，不超过 10 MiB/500 文件；重新打包后再导入。 |
| GitHub 没有仓库/构建 | 检查授权了目标仓库、Actions 流程已安装、精确 commit 的任务成功；在「设置 → Git」刷新状态。 |
| 私有预览打不开 | 核对独立网址、一次性密码、有效期和工作空间额度；失效后由项目成员重新生成密码，旧密码作废。 |
| 钱包网络不对或余额不足 | 按发布计划切换到 BSC/BNB、X Layer/OKB 或 Base/ETH；检查每一步报价及总预算，别把估算当最终账单。 |
| 交易中断或结果不明 | 先回部署详情看交易哈希和状态；已广播交易不要盲目重签。刷新后继续确认或按界面输入已有哈希。 |
| 域名或证书尚未生效 | 在「域名」复查精确 DNS 计划、归属与 TLS，再看固定版本网址；登记成功不代表网页已可访问。 |
| 网站打开但数据/API 失败 | 分别检查 Preview/Production 连接、权限、CORS 和自己的服务状态；恢复网站文件不会回滚数据库。 |
可在项目的「活动日志」「用量与诊断」定位操作时间和错误，再把不含密钥的项目/版本 ID、时间、错误文字交给邀请你的维护者。不要发送助记词、私钥、供应商令牌或数据库密码。
| Symptom | Next step |
|---|---|
| No sign-in code | Confirm the address is invited, check spam and spelling, and ask the inviter to check its status. Avoid rapid repeat requests. |
| ZIP import fails | Use a built site with index.html at the root, within 10 MiB and 500 files; rebuild and repackage. |
| No GitHub repository or build | Check repository consent, the installed Actions workflow and the exact commit's successful job. Refresh in Settings → Git. |
| Private preview fails | Check the independent URL, one-time password, expiry and workspace allowance. A member can regenerate the password; the old one stops working. |
| Wrong wallet chain or low balance | Use BSC/BNB, X Layer/OKB or Base/ETH as shown in the plan. Review each quote and the whole-operation budget. |
| Transaction result unknown | Inspect the release detail and transaction hash first. Do not blindly sign again after broadcasting. Resume confirmation with the existing hash. |
| Domain or certificate not live | Review the exact DNS plan, ownership and TLS in Domains, then test the pinned URL. Registration alone does not mean the site works. |
| Site opens but API/data fails | Check Preview/Production bindings, permissions, CORS and your service health separately. Restoring files does not restore a database. |
Use Activity logs and Usage & Diagnostics to find the time and error, then share non-secret project/release IDs and the error with your inviter. Never send a seed phrase, private key, provider token or database password.