website logo
ConnextBlogBridgeAcademy
⌘K
🚀CONNEXT WIKI
What is Connext?
Connext Bridge
NEXT Token
Supported Chains
Connextscan
FAQs
💢CONNEXT ECOSYSTEM
Connext Team
Backers
🤖ECOSYSTEM ROLES
Community Leaders
Amarok Pilot Dev
Ecosystem
Router Operator
Subgraph Provider
Testers
Connextooor
Bridgooor
Developer
Contributors
Quarantine
Status
🏅ROUTERS
What is a Router?
Router Requirements
Revenue Streams of Routers
Slashing Mechanism
Staking Mechanism
✨TECHNICAL DOCUMENTATION
Introduction
Connext Network
nxtp
🧁PROTOCOL UPDATES
Amarok
💥CONNEXT DAO
💫RESOURCES
Important Links
Brand Kit
Events
Telegram Groups
Newsletter
Docs powered by archbee 
3min

Interoperability Approaches

Existing interoperability systems can be differentiated by determining who assumes the responsibility of mirroring information across blockchains.  

Overview of Interoperability Systems: 

The following pverview categorizes existing interoperability systems by the chosen approach for verifying crosschain data: 

Approach

Mechanism

Examples

Trust Minimized  

Generalized 

Cheap/fast, easy to build, & extend  

Natively verified 

Chain's own validator set verifies xchain data. Typically done by running a light client of origin chain inside of the destination chain's VM

IBC, Near Rainbowbridge, BTC Relay, rollup entry/exit 

✅

✅

❌

Externally verified 

3rd party validator set verifies data across chains. AKA PoS/MPC systems

Thorchain, Anyswap, Synapse, Hyphen, etc. 

❌

✅

✅

Locally verified 

N-party system is reduced to 1:1 interaction, very easy to keep trust-minimized

Connext, Hop, simple atomic swaps

✅

❌

✅



🔗Connext vs. PoS/MPC

PoS/MPC interoperability systems

Updated 23 Apr 2022
Did this page help you?
Yes
No
UP NEXT
Connext vs. PoS/MPC Systems
Docs powered by archbee 
TABLE OF CONTENTS
Overview of Interoperability Systems: 
🔗Connext vs. PoS/MPC