Walrus as a decentralized storage protocol in the Sui ecosystem initially gained its competitiveness through Sui's Move contracts and high TPS. But now, as the ecosystem enters a new stage, focusing solely on a single blockchain is no longer enough; cross-chain storage capabilities are becoming the next key point.

From a technical feasibility perspective, implementing cross-chain storage with Walrus is not as complicated as it might seem. The main issues to address are: how to build the cross-chain bridge, how to adapt data formats, and how to ensure compatibility of consensus mechanisms across different chains.

First, regarding the cross-chain bridge. Walrus's approach is to develop a dedicated cross-chain bridging solution based on the Chainlink CCIP protocol, connecting major public chains like Ethereum and Solana. It sounds ambitious, but the core mechanism is not complex—using Hash Time Lock Contracts (HTLC) to ensure the atomicity of cross-chain data transfer, thereby preventing data loss or tampering during transit. Additionally, the bridging layer must also adapt to RedStuff-encoded sliced data, allowing both main slices and sub-slices to synchronize across chains, solving the longstanding problem of incompatible data formats among different public chains.

Next, on the optimization of the encoding layer. Although RedStuff encoding is currently closely tied to Sui's Move contracts, the core XOR operations and slicing storage logic are essentially chain-agnostic. The technical team’s approach is to strip out the Sui-specific parts of the encoding and create a universal encoding interface, enabling RedStuff encoding to run in different virtual machine environments like EVM and Solana VM. This broadens the path for cross-chain storage.