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 
2min

Contract-only Development Processes

The requirement for signature dependencies and offchain auctioning is removed as an external proof mechanism is no longer required. This allows routers to simply front the required capital on the destination chain until the data from the origin chain is ported to its destination over the messaging layer. On the destination chain, both transactions from the end user and the router are compared for validity. With this mechanism, contract-only development processes are enabled which simplifies the devX (developer experience). 



🔗Consensus Routing

Offchain consensus mechanism

Updated 22 Apr 2022
Did this page help you?
Yes
No
UP NEXT
Consensus Routing
Docs powered by archbee 
TABLE OF CONTENTS
🔗Consensus Routing