SYNTHR Protocol

Cross-Chain Communication

SYNTHR will, over the course of time, undertake multi-chain deployments across several networks, as per the timelines outlined in the roadmap.
  • Deployments on EVM chains such as ETH, Arbitrum, Optimism, BSC, AVAX, etc.
  • Port codebase to Rust for COSMOS IBC deployments.
  • Port codebase to Move for Aptos and Sui deployments.
To power cross-chain swaps and CDPs, SYNTHR will create a seamless cross-chain transactional environment for its users, devoid of trusted middle entities or conventional bridges, by partnering with a trustless omni-chain interoperability protocol to facilitate inter-chain trustless valid delivery of arbitrary user data, not just tokens.
  1. 1.
    Valid Delivery
Valid delivery serves as the fundamental building block of inter-chain communication and is defined as a communication primitive that enables cross-chain token transfer by providing the following guarantees:
  • Every message m sent over the network is coupled with a transaction t on the sender-side chain.
  • A message m is delivered to the receiver if and only if the associated transaction t is valid and has been committed on the sender-side chain.
Figure 10: Multi-chain deployment and communication to facilitate cross-chain swaps and CDPs.
2. Trustlessness
In order to successfully ensure trustless valid delivery, it is important that for any given message sent using the partner protocol (cross-chain communication partner), the oracle and relayer are independent of each other. This aspect of independence instead of trust eliminates malicious collusion between the two and guarantees trustlessness of valid delivery.
While the oracle is a third-party service that provides a mechanism to independently read a block header from one chain and send it to another chain, for instance, Chainlink. The relayer is an off-chain service that is similar in function to the oracle, but instead of fetching block headers, it fetches the proof for a specified transaction. The relayer service will be provided by the partner protocol, and the oracle service will be provided by Chainlink’s decentralized oracle network and associated consensus mechanisms.
Figure 11: Communication flow in a cross-chain transaction using a trustless omni-chain interoperability protocol.