TAP-20 重新编号为 TAP-02，内容不变TAP-20 Renumbered as TAP-02, Content Unchanged

These past few days, the community has been building faster on the same set of rules The TAPs repo now has 20 PRs, 12 of them still under discussion The team has brought in two more members to help handle proposals @0xAlphana built TapeNow, helping Builders ship their work On Chain with an agent A

TAP-20 writes down, byte by byte, how a Circuit is stored On Chain and what it computes Before, the Circuit format lived only in the code of the official frontend and contracts Third party tools had to reconstruct it from that code With TAP-20, compilers, simulators and verifiers can reach the same

On Chain, a Circuit is a sequence of records with no header and no terminator A NAND record is 7 bytes and produces one signal A LATCH record is 4 bytes and outputs the one bit of state it holds A REF record references another Circuit, its length depends on the number of inputs Signal 0 is constant

Anyone can start with an Idea issue and then submit a proposal through a PR TAP-01, TAP-10, TAP-11 and TAP-20 are all still Draft Being merged as Draft means a proposal has entered public numbering and discussion, not that it is a final standard For now maintainers act as editors How editors are cho

TAP-11 lets a Circuit's holder declare, inside the On Chain website, the service they run The service manifest sits at a fixed path on the site, /.well-known/tapeapi.json It lists the service's HTTPS endpoints and methods, and the address used for signing The holder signs an EIP-712 authorization h

TAP-20 was submitted by community author Yintong Wang The draft turns the Circuit netlist format and evaluation semantics into a public document The encoding, state layout and bit packing were all checked against real Circuits on BNB Chain mainnet It also states which rules come from verified contr

社区里的一句“这里能不能改一下”，有机会成为未来大家共同使用的规则。 TapeOut 的 TAPs 仓库已经建立。无论你是不是团队成员，都可以先开一个 Idea issue，聊清楚问题，再逐步形成提案。 对 TapeUP 而言，全链账本与地铁站网络的建设，也需要持续听到使用者和开发者的声音。 页面访问哪里不顺？消息交互还缺什么？哪些接口值得统一？欢迎把想法带进公开讨论，让更多人接着往下做。

The TAPs repo now has four merged drafts TAP-01, the proposal process itself TAP-10, the DeWEB access and messaging layers TAP-11, the TapeAPI service manifest and holder delegation, by @BruceBlue TAP-20, the Circuit netlist format and evaluation semantics, by Yintong Wang Two of them are signed b

#TapeOut 的提案TAPS正在收集提案，如果有意义的方案，可以去官方提交

#TAP-20是#TapeOut 最重要的基础设施标准提案 TAP-20 为链上硬件，定义标准化 Circuit Netlist（电路网表） 在TAP-20之前： 所有NAND门、链上CPU电路，只能在官方画布查看。 电路逻辑是封闭私有数据，第三方工具无法解析、自动验证。 TAP-20做了什么： 1.将电路网表格式、评估语义整理成公开规范文档 2.统一编码、状态布局、位打包规则 3. 已经在BNB主网真实链上电路（含Behemoth巨兽4位CPU）完成实测校验 4.区分已验证合约逻辑 & 待解决开放议题 类比芯片行业：Netlist就是流片前的电路接线蓝图。 放到TapeOu

关于 TAP-20 的调整公告： 现有技术格式标准将从TAP-20调整为TAP-02，感谢大家的支持和反馈。 我们做出了如下调整： · 电路网表标准已从 TAP-20 改为 TAP-02 · 内容不变：它仍是规定 TapeOut 链上电路格式与求值语义的底层规范 · TAP-02至TAP-09将是为基础技术标准预留的编号，编号仍由editor审核通过后分配 · TAP-20 将继续预留 编号本身并不影响技术规范，但它确确实实地影响着大家怎样解读和使用。TAP标准将永远为社区服务，因此收到合理的反馈我们立刻进行了修正。在TAP发布的短短几天内，我们收获了很多讨论。虽然作为editors非常

@Blonskr @CryptoLoser9 把原来的 TAP-20 重新编号为 TAP-02。内容本身不变，依然是规定链上电路格式和运行规则的基础标准。 TAP-02 更符合它作为底层技术规范的定位，也方便未来社区建立更清晰的 TAP 标准体系。 个人理解，加油 Tapeout。

@nat_poprika 太强了，把原来的 TAP-20 重新编号为 TAP-02。内容本身不变，依然是规定链上电路格式和运行规则的基础标准。 TAP-02 更符合它作为底层技术规范的定位，也方便未来社区建立更清晰的 TAP 标准体系。 个人理解，加油 Tapeout。