电路、容器、地址Circuits, containers, addresses
分清「资产」和「账号」：电路是资产，容器与端点才是账号；再读懂 .tape 名字与容器规则。Telling assets from accounts: a circuit is an asset, containers and endpoints are the accounts — plus .tape names and container rules.
一句话
TapeOut 的操作让人犯糊涂，多半是没分清「资产」和「账号」：电路是资产，容器与端点才是账号，钱包只负责证明归属与付 Gas。
三类身份
| 角色 | 是什么 | 长什么样 | 干什么 |
|---|---|---|---|
| 电路 | 流片产出的基础资产，即电路 NFT | 一枚 NFT | 被容器持有、参与打分排名 |
| 容器 / 端点 | 挂在电路上的 ERC-6551 账户 | 8.888、#4246@0 | 收发消息、绑定网站、持有资产 |
| 钱包 | 一把钥匙，不参与业务 | 0x 开头的地址 | 签名、证明归属、付 Gas |
从元件到网站
元件不是电路，电路不是账号，一层层往上是这样：
- 元件：NAND、LATCH，最小的砖块。
- 电路：把元件按 netlist 连好再流片，得到电路 NFT。
- REF：电路可以引用已完成的电路，不必重造。
- 容器：给电路配一个账户，基于 ERC-6551。
- DeWEB：用 SiteRegistry 把网站绑到容器的身份上。
容器：绑在电路上的账户
电路容器是绑定在一枚电路 NFT 上的链上账户，遵循 ERC-6551（代币绑定账户）标准——让一枚 NFT 拥有自己的智能合约钱包。
- 要付费：BNB Chain 官方标注 0.012 BNB，X Layer 为 0.08 OKB，别拿 BNB 的数字去套；之后从容器转出资产还要付一笔很小的协议手续费，这些费用进国库、换成 BEM，其中 80% 定期销毁。
- 没有私钥：控制权等于电路 NFT 的当前持有人，谁拿着电路谁就能取走容器里的东西。
- 跟着电路走：电路转手时，容器里的资产和持续收益一起归新主人，卖电路等于连容器一起卖。
- 挂单即冻结：电路在市场挂单期间容器被冻结，且容器里的资产不计入挂单价格。
- 不能套娃：容器可以持有各种链上资产，但不能装本协议的电路。
它不是钱包：钱包属于人，容器属于你那枚电路。
所以容器承载不了锁仓、质押这类不可反悔的承诺；卖电路之前，务必清点并转出容器里的资产。
容器能做什么
| 用途 | 说明 |
|---|---|
| 存资产、收款 | 任何人都能往容器地址转账 |
| 挂链上网站 | 一个容器一个网站，地址形如 tape://4246.0.tape/ |
| 收发加密消息 | 容器就是 TapeSend 的收件地址 |
| 当一台机器的主人 | 官方链上 Linux 演示里，机器所有者就是一个容器 |
TapeID
一枚电路的链上编号叫 TapeID，完整写法 <电路#ID>.<区号>.<处理器编号>。区号标明在哪条链：BNB Chain 省略区号，X Layer 是 2，Base 是 3。
.tape 名字怎么读
规范写法是 <电路#ID>.<处理器编号>.tape，例如 4246.0.tape，即 0 号处理器（Genesis CPU）上的第 4246 枚电路。
必须带处理器编号：每台处理器的电路编号都从 1 开始，#12 在 0 号与 7 号处理器上是两枚完全不同的电路，只有「处理器 + #ID」才能唯一确定。
| 写法 | 例子 |
|---|---|
| 规范名字 | 4246.0.tape |
| 省略后缀 | 4246.0 |
| 网址 | tape://4246.0.tape/docs/ |
| 网页别名 | web+tape://4246.0.tape/docs/ |
| 简写 | #4246@0 或 4246@0 |
| 容器地址 | 0x86DD…eA95 |
| 处理器合约#ID | 0x50A9…9DD9#4246 |
其他写法必须报错，不得猜测。
多链示例：1.2.344（或 #[email protected]）是 X Layer 上 344 号处理器的 #1 电路。
最常见的错
把 0x 地址当账号填。钱包地址只证明归属，不是聊天账号。需要填账号时，填的是容器或端点，形如 8.888、#4246@0。
哈希证明什么
哈希是文件指纹：能证明你取到的是发布的那一份，不保证内容为真。内容对不对，看的是发布者本身。
In one line
Most confusion comes from mixing up "asset" and "account": a circuit is an asset, containers and endpoints are the accounts, and the wallet only proves ownership and pays gas.
Three roles
| Role | What it is | What it looks like | What it does |
|---|---|---|---|
| Circuit | the base asset a tapeout produces, i.e. a circuit NFT | an NFT | held by a container, scored and ranked |
| Container / endpoint | an ERC-6551 account attached to a circuit | 8.888, #4246@0 | send and receive messages, bind a site, hold assets |
| Wallet | a key, not part of the business | an address starting with 0x | sign, prove ownership, pay gas |
From parts to a website
A part is not a circuit, and a circuit is not an account — it stacks like this:
- Parts: NAND and LATCH, the smallest bricks.
- Circuit: wire parts per a netlist and tape out to get a circuit NFT.
- REF: a circuit can reference finished circuits instead of rebuilding them.
- Container: gives a circuit an account, based on ERC-6551.
- DeWEB: binds a website to the container identity via SiteRegistry.
A container: an account bound to a circuit
A circuit container is an on-chain account bound to a circuit NFT, following the ERC-6551 (token-bound account) standard: it gives an NFT its own smart-contract wallet.
- It costs: the BNB Chain listing is 0.012 BNB, and X Layer is 0.08 OKB — do not map one number onto the other. Moving assets out later adds a tiny protocol fee; fees go to the treasury, are swapped into BEM, and 80% is burned periodically.
- No private key: control equals the circuit NFT current holder — whoever holds the circuit can take what is inside.
- It follows the circuit: when the circuit changes hands, its assets and ongoing yield go with it; selling the circuit sells the container too.
- Frozen while listed: a listed circuit freezes its container, and the assets inside are not counted in the listing price.
- No nesting: a container can hold all kinds of on-chain assets, but it cannot hold a circuit from this protocol.
It is not a wallet: a wallet belongs to a person, a container belongs to your circuit.
So a container cannot carry lock-up or staking promises that cannot be undone. Before selling a circuit, take stock and move the assets out.
What a container can do
| Use | Detail |
|---|---|
| Hold assets, receive payment | anyone can send to the container address |
| Host an on-chain site | one container, one site, addressed like tape://4246.0.tape/ |
| Send and receive messages | the container is the TapeSend inbox |
| Own a machine | in the official on-chain Linux demo, the owner is a container |
TapeID
A circuit's on-chain ID is its TapeID, written <circuit#ID>.<area code>.<processor number>. The area code says which chain: BNB Chain omits it, X Layer is 2, Base is 3.
How to read a .tape name
The canonical form is <circuit#ID>.<processor number>.tape, e.g. 4246.0.tape — circuit 4246 on processor 0 (Genesis CPU).
The processor number is required: every processor numbers its circuits from 1, so #12 on processor 0 and on processor 7 are two different circuits; only "processor + #ID" pins one down.
| Form | Example |
|---|---|
| Canonical name | 4246.0.tape |
| Without suffix | 4246.0 |
| URL | tape://4246.0.tape/docs/ |
| Web alias | web+tape://4246.0.tape/docs/ |
| Shorthand | #4246@0 or 4246@0 |
| Container address | 0x86DD…eA95 |
| Processor contract#ID | 0x50A9…9DD9#4246 |
Any other form must error out, no guessing.
Multi-chain example: 1.2.344 (or #[email protected]) is circuit #1 on processor 344 on X Layer.
The classic mistake
Typing a 0x address as the account.A wallet address only proves ownership; it is not a chat account. When asked for an account, use a container or endpoint such as 8.888 or #4246@0.
What a hash proves
A hash is a file fingerprint: it proves you fetched the published copy, not that the content is true. To judge the content, look at who published it.