🌉
Telegraph: Crosschain Bridge
  • Getting Started
    • What is Telegraph
    • Telegraph Token
    • Core Concepts
      • Message Data
      • Time Based Thresholds
    • Bridging Fees
      • Fee Distribution
      • Fee Table by Chain
        • Ethereum
        • BSC
        • MATIC (Polygon)
        • AVAX
        • HECO
  • Node Overview
    • What's in a node
    • Transactions
    • Networks
    • Validators
  • Examples & Tutorials
    • EVM Chains
      • Hello World!
      • ERC20 Transfers
      • Securing Your Smart Contract
  • Contract Documentation
    • Port Contract
    • Telegraph Port Addresses
  • LLM Integration
    • ChatGPT Plugin
Powered by GitBook
On this page
  1. Node Overview

Transactions

Stored transactions are used to keep track of messages that the validator may have to sign and broadcast. These transaction documents are generated either through the detection of an event on a port contract, or receiving an unknown signed transaction from another validator. Each transaction contains information required for validators to properly route the message to its final destination. Developers can pass multiple types of data(int, string, bool, byte) arrays to their end destination.

Below are the fields that make up a transaction:

Transaction Data
  • DetectionTime

  • Hash

  • EndHash

  • LogIndex

  • BlockNumber

  • Event

  • Sender

  • Addresses

  • Ints

  • Strings

  • Bools

  • FeeAmount

  • StartChain

  • Destination

  • End Chain

  • SignedCount

  • Signers

  • R

  • S

  • V

  • H

  • IsConfirmed

PreviousWhat's in a nodeNextNetworks

Last updated 2 years ago