source avatar𝕸𝖚𝖘𝖎𝖓⭕️莫信

Share

No Misinterpretation | TapeRelay Launches on X Layer: Single File Limit Expanded from 8.4 MB to ~1 PiB, Messages Are Gas-Free, Storage Paid in $BEM This afternoon, @Blonskr officially announced TapeRelay: a network designed for storing large files and transmitting encrypted messages, now live in test mode on the X Layer mainnet. The individual file limit on TapeOut’s on-chain website has been expanded from 8.4 MB to approximately 1 PiB; sending messages no longer requires gas fees; storage exceeding the free allowance is paid for using $BEM. This analysis verifies every claim in the announcement against the official website, developer documentation, the npm client library, and the smart contracts on X Layer: identifying what is currently functional and what awaits post-testing. 🐋 TapeRelay in One Minute: - “Communication nodes” store files and relay messages; data itself is not stored on-chain. - Only three contracts exist on X Layer: a node registry, a node directory, and a payment contract—handling identity, node listings, and payments. - A developer’s identity is tied to a TapeOut circuit (e.g., 1.2.0); files, plans, and keys are all registered under the circuit name. - Files are split into 1 MiB chunks, named by SHA-256 hash; the browser verifies each chunk upon retrieval—any single-byte alteration by a node will be detected. - By default, files are stored across three nodes operated by different parties; storage is considered successful once two nodes confirm. On 10/17, while writing about upgrading the DeWEB storage gateway, I asked whether large files should be stored directly on-chain or off-chain with only hashes recorded on-chain. TapeRelay chose off-chain storage—neither file hashes nor content are recorded on-chain; only node lists, encryption public keys, and payment data are stored. 🐋 7 Verified Claims from the Announcement: 1. 8.4 MB and TapeSend gas fees: TAP-10 specifies a maximum of 350 blocks per file, each block 24,000 bytes, totaling 8,400,000 bytes. Every TapeSend message is written on-chain and incurs gas. 2. ~1 PiB limit: Client code uses 1,048,536-byte chunks per encrypted file. A single-level index can list up to 32,766 chunks; a two-level index allows 32,766 × 32,766 chunks—totaling approximately 1.13 × 10¹⁵ bytes (~1 PiB). 3. Ethereum throughput ~20 KB/s: At 224 gas per byte (as calculated on 10/17 for DeWEB uploads), with Ethereum’s current block gas limit of 60 million gas, ~268,000 bytes can be written per block—roughly 22 KB/s (one block every 12 seconds). 4. 1 GB costs tens of thousands of dollars: At 224 gas per byte, 1 GB requires 224 billion gas. At today’s rate of 0.111 gwei and ETH at $1,809, this equals ~$45,000—and would occupy ~3,700 Ethereum blocks (equivalent to 12 hours of the entire chain dedicated solely to this upload). 5. Live on X Layer mainnet: Three contracts deployed on 11/10; five nodes (relay1–relay5) are online; client libraries @taperelay/client and @tapestore/client published to npm on 11/17; official website, developer guides, and AI development manuals available in both English and Chinese. Real-time network data on the site shows: over the past 7 days, 18,338 requests, 1,986 unique visitors, ~480 MB traffic (as of 11/18 15:35)—people are already using it before the announcement. 6. Open link → view file: The whitepaper on the official site is itself stored on TapeRelay. This afternoon I opened its share link in standard Chrome without connecting a wallet—the page displayed “807.7 KiB,” “Encrypted, chunk-by-chunk verification passed.” 7. Test period allowance: Each node grants each circuit 5 GiB free storage—the exact figure matches the published value of 5,368,709,120 bytes. Messages have no limit on quantity but are rate-limited to prevent abuse; downloads are free of bandwidth charges, though operators may throttle traffic. 🐋 Features Not Yet Available During Test Phase: - All five nodes are operated by the TapeOut team. The protocol supports five operators; third-party nodes are not yet open. Node software is released under MIT license with installation packages; setup instructions will be published when third-party node access opens. “Deploy a node with one command and register it in the directory” is next. - Encryption is developer-selectable: The default upload method stores public files—anyone with the hash can read them. Private content uses encrypted files; nodes receive only ciphertext and cannot see content or filenames. - Section 16 of the developer docs lists what operators can see: who (IP) accessed which file and when, file size, message sender/receiver and timestamps. Operators cannot see encrypted file content or message bodies. - “One random key per chunk” in code means: one random key per file; each chunk encrypted with a different nonce; up to 16 recipients allowed per message. - Cross-node messaging protocol is supported; demo site currently connects only to relay1. User identity is bound to a node—switching nodes creates a new identity; friends must be re-added. - “Periodic verification and repair”: Nodes do not replicate data among themselves; repair is handled by the developer’s backend or an open browser tab. - “Start playback in ~3 seconds,” “single-node throughput of several MB/s to tens of MB/s”: Figures provided by the website; I have not yet tested with large video files. 🐋 XIP and “The First” The official site states: “TapeRelay is an XIP proposal developed by the TapeOut team in collaboration with X Layer.” The full proposal is the bilingual whitepaper hosted on the site. I found no publicly accessible XIP repository or numbered proposal ID; no TapeRelay proposal yet exists in TapeOut’s TAP repository. X Layer’s official documentation on this matter awaits official release.The announcement states that TapeRelay is the first to simultaneously achieve "speed" and "trustless nodes." Similar concepts have existed before: Nostr relays only store and forward messages, with signatures verified by clients—relays cannot alter or impersonate; Storj encrypts data on the client side first, then splits and distributes chunks across multiple providers, leaving metadata and node orchestration to the official coordination service. What sets TapeRelay apart is that developer identity, node listings, and payments are all handled on X Layer, using the same circuit as the DeWEB website. 🐋 How much does it cost developers to use it now? - One-click setup: 3 transactions + 1 signature, approximately 0.08 OKB plus gas fees; during the test phase, only X Layer circuit is supported—BNB Chain contract is deployed but no nodes yet available - Each node supports up to 5 GiB, no $BEM required - For usage beyond limits, purchase node-based plans: 2 GiB for 90 days at 0.2 BEM—purchase one plan per storage provider - 95% of plan payments go to operators, 5% to the protocol; funds are held in a payment contract and released daily to operators - The payment contract currently holds 0.2 BEM—exactly the cost of one plan The test phase is expected to last two weeks. @Fabx_global has already posted that they will be among the first to integrate. When third-party nodes will open and under what rules will be announced separately by the official team. @Blonskr @TapeOutWorld @XLayerOfficial

No.0 picture
No.1 picture
No.2 picture
No.3 picture
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.