LogoLogo
  • Guide to Developing on Layer One X
    • Contents
    • L1X vs. Other Chains
    • L1X Technology Overview
      • X-Talk Overview
      • L1X System Architecture
      • XTalk Deep Dive
  • L1X Documentation
    • Setup L1X Development Environment
  • Use Cases
    • Use Case 1: Decentralised Finance (DeFi)
      • Key Components and Protocols
      • Use Case Implementation Examples
      • Future Trends and Innovations
    • Use Case 2: Non-Fungible Tokens (NFTs)
      • Applications in Art, Gaming, and Collectibles
      • Use Case Examples and Case Studies
      • Emerging Trends in NFTs
    • Use Case 3: Identity Management
      • Importance of Self-Sovereign Identity
      • Use Cases in Identity Verification and Authentication
      • Projects and Initiatives in Identity Management
      • Privacy and Security Considerations
    • Use Case 4: Content Monetisation
      • Challenges in Content Monetisation
      • Blockchain Solutions for Micropayments and Royalties
      • Use Case Examples in Publishing, Music, and Media
      • Future Opportunities and Trends
    • Use Case 5: Voting and Governance
      • Advantages of Blockchain in Voting Systems
      • Use Cases in Elections, Polls, and Governance
      • Projects and Platforms for Decentralised Voting
      • Challenges and Considerations
    • Use Case 6: Decentralised Storage
      • Problems with Centralised Storage Solutions
      • Use Cases in Decentralised File Storage
      • Projects and Platforms for Decentralised Storage
      • Scalability and Performance Challenges
    • Use Case 7: Gaming and Virtual Worlds
      • Introduction to Blockchain Gaming
      • Use Cases in Virtual Economies, Assets, and Ownership
      • Notable Projects and Success Stories
      • Trends and Innovations in Blockchain Gaming
    • Use Case 8: Healthcare and Medical Records
      • Importance of Data Integrity and Security in Healthcare
      • Use Cases in Medical Records Management
      • Projects and Initiatives in Health Data Management
      • Regulatory Compliance and Privacy Concerns
    • Use Case 9: Decentralised Autonomous Organisations (DAOs)
      • Understanding DAOs
      • Use Cases in Governance, Funding, and Decision Making
      • Future Developments
    • Use Case 10: Supply Chain Management
      • Overview of Supply Chain Challenges
      • Blockchain Solutions in Supply Chain
      • Use Case Examples in Tracking and Traceability
      • Potential Benefits and Challenges
  • Get Started with L1X SDE
    • L1X Workspace Overview
      • L1X SDE toolkit architecture
    • Development Workspace Environment & Contract Types
      • 1 - Contemporary Contracts
      • 2 - ERC20 Contract Deployment and Cross Contract Call
      • 3 - X-Talk Flow Cross Chain Contract
      • 4 - Balancer-v2
  • Build with Developer Playground
    • Developer Playground Resource
  • Core Concepts
    • Account
    • Address
    • Transaction
    • Smart Contract
    • Contract Lifecycle (VM)
    • Cross-Contract call
      • L1X VM Cross-Contract Calls
      • L1X VM-EVM Cross Contract Calls
    • Cluster
Powered by GitBook
On this page
  1. Guide to Developing on Layer One X
  2. L1X Technology Overview

XTalk Deep Dive

PreviousL1X System ArchitectureNextL1X Documentation

Last updated 1 year ago

X-Talk Flow Contract includes X-Talk Port Contract, X-Talk Commander Contract, X-Talk Helm and X-Talk Customs Contract as building blocks for the X-Talk Flow Contract. These contracts process instructions based on X-Talk messaging standard or instruction sets.

X-Talk Port Contract

  • The X-Talk Port Contract lives on the Listener Node.

  • The X-Talk Port Contract is responsible to bring data into the L1X Protocol and providing it to the X-Talk Commander Contract.

  • Data include real-world data (Oracle), event data from other protocols and custom data insertion scripts that bring data from applications or configured endpoints through API's.

  • The data is transformed into a standard serialisable format (X-Talk Message) which is then pushed towards validation.

  • The Event Listening Nodes validate the data attaching a unique identifier and send it to the Scheduler for further processing.

  • The Scheduler is responsible to group and send the serialised data according to filters and specific rules around the filters such as type of information, event types which is then sent to the responsible cluster.

X-Talk Commander Contract

  • The X-Talk Commander Contract is the main orchestrator in defining and instructing the flow of the contract.

  • Its allows developers to build modular logic around cross-chain applications with interfaces that include Contract Storage, Flow Logic and Business Logic Entrypoints.

  • Contract Storage allows you to load and save complete or specific state of the contract such as events, default and/or transformed payloads, business logic and other defined states.

  • Flow Logic includes required methods which are save_event_data(...), entrypoint_Business() and get_payload_to_sign(...).

    • save_event_data(...) method saves event data to the contract. Based on the source ID and event type, it categorises the event and processes it accordingly. It then checks existing events and sets up payloads to be executed, depending on the nature of the event.

    • entrypoint_Business() is where core business logic would be added which will pass control to the entrypoint function. This will allow you to store the default event data and apply transformation to it before creating the payload.

    • get_payload_to_sign(...) method fetches the payload related to a given global transaction ID. The payload can then be signed for cross-chain verification.

  • Business Logic Entrypoints allow you to transform payload through the same contract or cross-contract calls including L1X VM and L1X EVM which extend X-Talk and Solidity contracts while maintaining the instruction flow.

X-Talk Helm

  • X-Talk Helm includes implementation to Route, get data and provide instruction to the X-Talk Customs contract to sign and broadcast payload to internal contracts or cross-chain contracts.

  • It provides modularity that will allow routing and selecting the appropriate signing-broadcasting nodes to interact with the default or transformed payload.

X-Talk Customs Contract

  • X-Talk Customs Contract is responsible to provide the right signing to the payload before it broadcast it to the appropriate destination.