However, integrating IBC into Sui’s object-centric model poses challenges such as adapting IBC’s account-based assumptions to object ownership, managing asynchronous message passing for mutable objects, and ensuring secure state sync across chains.

Addressing these requires protocol-level design changes and new primitives to handle object versioning and composability in cross-chain contexts.

There has been growing interest in whether Sui could support native interoperability protocols like IBC (Inter-Blockchain Communication) to enable secure, trustless cross-chain messaging and asset transfers without relying on risky third-party bridges. While IBC was originally designed for Cosmos’ account-based chains, adapting it to Sui’s object-centric architecture would introduce unique challenges. For example, Sui would need to define how cross-chain proofs map to owned and shared objects, ensure that light clients can be efficiently verified by Move smart contracts, and maintain parallel execution without introducing ordering conflicts from external state. These design adaptations could make interoperability on Sui more complex than in Cosmos, but also potentially more secure and efficient, since Move’s strong type system and resource ownership model provide stricter guarantees around asset handling. If implemented, a native IBC-like protocol on Sui could set a new standard for scalable, trust-minimized interoperability across ecosystems.

There are discussions in the Sui community about supporting native interoperability protocols like IBC to enable trustless cross-chain messaging and asset transfers without third-party bridges.

However, integrating IBC into Sui’s object-centric model poses challenges such as adapting IBC’s account-based assumptions to object ownership, managing asynchronous message passing for mutable objects, and ensuring secure state sync across chains.

Addressing these requires protocol-level design changes and new primitives to handle object versioning and composability in cross-chain contexts.

Sui would need to define how cross-chain proofs map to owned and shared objects, ensure that light clients can be efficiently verified by Move smart contracts, and maintain parallel execution without introducing ordering conflicts from external state. These design adaptations could make interoperability on Sui more complex than in Cosmos, but also potentially more secure and efficient, since Move’s strong type system and resource ownership model provide stricter guarantees around asset handling. If implemented, a native IBC-likeHowever, integrating IBC into Sui’s object-centric model poses challenges such as adapting IBC’s account-based assumptions to object ownership, managing asynchronous message passing for mutable objects, and ensuring secure state sync across