YAR Docs
  • TestNet Instruction
    • Introduction
    • Add YARchain TestNet
    • Add a few others TestNets
    • YAR v.1.0beta — Rewarding Usage Experience
  • DEV DOCS
    • Protocol
    • Fees
    • Use cases
    • Hello world!
  • WhitePaper
    • Introduction
    • YAR architecture
      • YAR objective
      • YARchain architecture
      • Connectors architecture
    • Project mechanics
      • Nodes
      • Chain Connection
      • Witness operations
      • Consensus on transactions
      • Threshold Signature Scheme (TSS)
      • Scaling
      • Management
      • Voting in YAR DAO
      • Supported networks
      • Protocol updates
      • Use cases
      • $YAR Utilization
      • Transaction fee and cross-chain calls discount
    • Conclusion
    • LEGAL DISCLAIMER
Powered by GitBook
On this page

Was this helpful?

  1. WhitePaper
  2. Project mechanics

Chain Connection

Two-way secure state management

YAR chain is connected to networks like Bitcoin and Ethereum via bidirectional security busses of the YAR protocol. This means that subjects and objects in networks may or may not be bound to subjects and objects in other networks. State management only synchronizes the state of a transaction or linked smart contract on the external network. Specifically, the system tracks:

  • which part of an object has been moved;

  • associated information such as the transaction ID;

  • the address of the sender;

  • the address of the person receiving the asset.

It's worth noting that only information about YAR-related transactions is synchronized, but not every transaction in the external network.

To make this possible, code must be written for each connected network, the so-called "network connectors", which describe possible scenarios for working with objects and subjects of the external network.

PreviousNodesNextWitness operations

Last updated 2 years ago

Was this helpful?