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
  • Core Implementation Approach
  • Emitter
  • Controller Smart Contract
  • Vault & Escrow
  1. Glitter Crosschain Platform
  2. Bridge Core MVP
  3. Bridge Core MVP

Core Concept

PreviousBridge Core MVPNextBridge Relayer

Last updated 2 years ago

Core Implementation Approach

The Glitter Bridge consists of two completely separated deployments in Frontend and Backend with no direct communication or even having a notion of each other.

The Frontend is responsible for sending requests to each side of bridge related blockchain as well as waiting for the status finalization on the other side by listening for smart-contract program updates or checking the associated wallet's local state (depending on the chain mechanism and functionalities).

Emitter

On the backend nodes, emitter (PubSub design pattern) agents are listening to smart contracts on each chain waiting for new approvals to emit them to the other side's subscriber agent, and then the other side's node would use an oracle transaction to update the smart contract states and give back an ACK message to the publisher on originating side.

Controller Smart Contract

On frontend, bridge process fulfillment will be followed through listening to smart contract transactions finalization with associated specific signatures of the exact bridging process started by the very same frontend instance.

Vault & Escrow

For token mechanisms in place, it also varies depending on the chains. For Algorand LOCK/RELEASE is used while on Solana MINT/BURN is being utilized.