TapeSend
容器之间的加密消息：链上信箱、TAP-10 端点号、端到端加密、部署状态与已知限制。Encrypted messaging between containers: the on-chain mailbox, the TAP-10 endpoint ID, end-to-end encryption, deployment status and known limits.
容器之间的加密消息
TapeSend 让电路容器之间互发消息。像 #4246@0 这样的容器就是一个收件地址，持有电路的人以容器身份发消息。每条消息写进发件人所在链上的一个小合约——DeWEB 中枢（Hub），端到端加密。消息路径上没有跨链桥、没有索引器、没有服务器，每个客户端都自己去链上核对读到的内容。它的规范编号是 TAP-10。
端点号怎么组成
端点号（Endpoint ID） 是 TAP-10 的核心：
| 字段 | 字节 | 含义 |
|---|---|---|
保留位 uint32(0) | 4 | 固定为 0 |
链 ID uint64 | 8 | BNB Chain = 56 |
| 容器地址 | 20 | 电路的 ERC-6551 账户 |
端点号 = uint32(0) ‖ uint64(chainId) ‖ 容器地址，一共 32 字节，全网唯一。BNB Chain 上显示为 #15324@30，其他链带短名，如 #[email protected]。示例（BNB Chain 上的 #4246@0）：00000000 0000000000000038 86ddae…ea95（0x38 = 56）。
加密，以及公开的元数据
消息在你自己的设备上就锁好了，只有收件人能打开（技术上用 X25519 + XChaCha20-Poly1305，载荷格式 0x02）。开锁的钥匙由钱包签名生成，不用另记密码；对应的公钥公开放在中枢上，别人用它给你发加密信。
元数据公开：谁给谁发、什么时候、多长，在链上都看得到，只有内容是加密的。
附件：小图片放在加密内容里；资产附件是转进对方容器的转账，由收件方客户端到链上核对。
上线到哪一步
send/README（2026-09-18）：中枢已在 BNB Chain 主网上线，代理地址 0xe61A…E25ee，当前实现 v3 0x80aF…EE85，各链地址相同。README 当时把 Base、X Layer 列为计划中；仓库 2026-09-19 的提交加入了「X Layer 和 Base 支持」。
同一天，X Layer 中文台 @xlayer_zh 确认 TapeOut 已在 X Layer 主网完成部署：处理器工厂、电路容器、网站仓库、TapeSend 跨链加密消息通道四个模块全部上线，X Layer 与 BNB Chain 之间可以直接互发端到端加密消息，不用跨链桥；PoD 挖矿经济体系不受影响，仍以 BNB Chain 为中心。X Layer 开容器是 0.08 OKB。Base 还在计划中。
创始人 @Blonskr 同一天发了一段约 104 秒的视频，讲他对 DeWEB 的设想：做成横跨所有主流公链的去中心化广域网。TapeSend 已在 GitHub 以 MIT 协议完全开源，附带网页、Mac、iOS、Android 四个平台的客户端，任何开发者都能拿去商用。
已知限制
任何已开通容器的人都能往别人信箱里「刷」消息（客户端对陌生人每页只显示 3 条）；被授权过电路 NFT 的合约（例如交易市场）可以在一笔交易里借用电路、以容器身份发消息（客户端会标出）。
规范还在重写
README 提到 TAP-10 规范「正在作为 DeWEB 标准的一部分重写，之后单独发布」。截至写作时，还没有独立发布的 TAP 标准文本，也没有 TAP-1 ~ TAP-9 之类的其他编号文档。
社区客户端
TapeSend 开源后，社区一天之内就做出了好几个客户端。社区作者 YW（@ywweb3）的长文《TapeSend 诞生 24 小时：三款产品爆发，狂欢背后的机遇与隐忧》（2026-09-20）记录了这段热闹，也聊了留存问题。
Encrypted messaging between containers
TapeSend lets circuit containers message each other. A container like #4246@0 is a mailing address, and whoever holds the circuit sends as that container. Every message is written into a small contract on the sender's chain — the DeWEB Hub — end-to-end encrypted. On the path there is no bridge, no indexer, no server: every client checks what it reads against the chain itself. Its spec number is TAP-10.
How the endpoint ID is built
The endpoint ID is the core of TAP-10:
| Field | Bytes | Meaning |
|---|---|---|
Reserved uint32(0) | 4 | always 0 |
Chain ID uint64 | 8 | BNB Chain = 56 |
| Container address | 20 | the circuit's ERC-6551 account |
An endpoint ID is uint32(0) ‖ uint64(chainId) ‖ container address — 32 bytes, unique across all chains. On BNB Chain it shows as #15324@30; elsewhere it carries a short chain name, such as #[email protected]. Example (#4246@0 on BNB Chain): 00000000 0000000000000038 86ddae…ea95 (0x38 = 56).
Encryption, and public metadata
A message is sealed on your own device and only the recipient can open it (technically X25519 + XChaCha20-Poly1305, payload format 0x02). The key is derived from a wallet signature, so there is no separate password to remember, and the matching public key is published on the Hub so others can send you encrypted mail.
Metadata is public: who sends to whom, when, and how long — all visible on-chain. Only the content is encrypted.
Attachments: small images go inside the encrypted content; asset attachments are transfers moved into the recipient's container, which the recipient's client verifies on-chain.
How far it has shipped
send/README (2026-09-18): the Hub is live on BNB Chain mainnet, proxy 0xe61A…E25ee, current implementation v3 0x80aF…EE85, the same address on every chain. The README listed Base and X Layer as planned at the time; a 2026-09-19 commit added "X Layer and Base support".
The same day, X Layer's Chinese channel @xlayer_zh confirmed TapeOut had deployed on X Layer mainnet: the processor factory, circuit containers, site repository and the TapeSend cross-chain encrypted messaging channel all live, with X Layer and BNB Chain exchanging end-to-end encrypted messages directly and no bridge; PoD mining economics are unchanged and still centered on BNB Chain. Opening a container on X Layer costs 0.08 OKB. Base is still planned.
Founder @Blonskr posted a ~104-second video the same day about his DeWEB vision: a decentralized WAN spanning all major public chains. TapeSend is fully open-sourced under MIT, with web, Mac, iOS and Android clients that any developer can use commercially.
Known limits
Anyone with an activated container can spam another inbox (clients show only 3 messages per page from strangers); a contract granted a circuit NFT (a marketplace, say) can borrow the circuit and send as the container within one transaction (clients flag this).
The spec is still being rewritten
The README notes that the TAP-10 spec is "being rewritten as part of the DeWEB standard and will be published separately". As of writing there is no standalone TAP text, and no TAP-1 through TAP-9 either.
Community clients
Within a day of TapeSend going open-source the community shipped several clients. YW (@ywweb3) wrote a long post, "TapeSend in its first 24 hours" (2026-09-20), about the burst of activity and the retention question.