Glitter Finance
  • Introduction
    • Disclaimer
    • Avoiding Crypto Scams
    • Glitter Finance Links
    • Glitter Finance Community Bug Bounty Program
  • Glitter Crosschain Platform
    • Bridge FAQ
      • General Bridge Questions
      • Algorand
      • Solana
      • Ethereum
      • Avalanche
      • Polygon
      • Tron
    • New Interface Overview
    • Bridging Tutorials
      • Algorand to Solana
      • Solana to Algorand
      • USDC: Swap Tutorial
    • USDC and EUROC Transfer
      • Audit Report for USDC Swap
    • Supported Wallets
      • Wallets Compatibility / Mapping
    • Bridging Security
    • Audits
    • Incorrect/Failed Transactions
    • Bridge Core MVP
      • Disclaimer and Key Terms
      • Bridge Core MVP
        • Core Concept
        • Bridge Relayer
        • Sending Request
        • Receiving Request
        • Glitter Bridge Protocol
        • Relaying Request
    • Token Bridge v2
      • Infrastructure
      • Lifecycle of the validator
      • Potential issues
      • Supported Networks, Token Bridge v2
      • Supported Networks, Token Bridge MVP v1
    • Glitter SDK
    • Glitter Widget
    • Supported Tokens
  • Glitter Bridge Explorer
    • Glitter Bridge Explorer
    • Glitter Bridge Explorer Guide
    • Deep Analytics
  • Glitter Arbitrage and Liquidation Bot
    • Glitter Arbitrage Bot
    • What are Arbitrage Loops?
    • State of the Project
  • Brand Assets
    • Logo
      • Clearspaces
      • Logo Dont's
      • Logo Assets
        • Horizontal logotype
        • Vertical logotype
        • Logotype Box
    • Glitter Colors
      • Backgrounds
  • Rainbow Network
    • Overview
Powered by GitBook
On this page
  • Protocol Gateway A
  • Primary/Origin Chain
  • Lock and Release Protocol
  1. Glitter Crosschain Platform
  2. Bridge Core MVP
  3. Bridge Core MVP

Sending Request

PreviousBridge RelayerNextReceiving Request

Last updated 2 years ago

Protocol Gateway A

Glitter Bridge protocol gateway allows users to interact with Blockchain A to make send requests. The smart contract receives request call data from users and sends protocol messages to the primary blockchain which the local node serves as the operability to validate the message being transmitted. The protocol verifies the native token to bridge is locked in the contract and transmit the approval message to protocol gateway B.

Primary/Origin Chain

This is a chain where users lock or request to unlock native assets and transfer native assets to bridge.

Lock and Release Protocol

One Bridge protocol executes cross transfer of assets using lock and mint smart contract functions. This makes the native token to be locked/unlock on the primary chain and the wrapped asset is minted/burnt on the secondary chain