# Introduction The Glitter Crosschain Platform - a crosschain base layer, for layer-1s and crosschain DeFi. ### The Glitter Bridge offers easy to use liquidity movement across multiple blockchains. It also allows users to invest in cross chain DeFi seamlessly. ### **Briefly on Glitter Finance** Glitter Finance is a base layer technology focused on interoperability, liquidity movement and ease of use. The bridge provides an interoperability solution that serves as a base layer for layer-1 networks and DeFi protocols across multiple blockchain networks. It thrives by linking disparate ecosystems and simplifying the usage and investment process across chains. Glitter bridge powers cross-chain transfer of assets between Non-EVM and EVM supported networks bidirectionally, the first being the Algorand and Solana blockchain networks. It allows for easy integration with supported blockchain smart contracts, protocols, decentralized exchanges (DEX), and wallets to enable liquidity movement across various blockchain networks ### **Platform Components** Glitter Finance offers an advanced interoperability platform. Glitter is a hybrid platform which is composed of and combines multiple cross-chain technologies under one roof, which creates a never-before-seen flexibility in moving assets between multiple, supported blockchains. What are the technologies? 1. **Glitter Wrapped Token Bridge** - this is a highly audited cross-chain platform which enables the creation of wrapped tokens via our Developer Portal. The exact mechanics of this product can be seen in the sections of these documents following this one. 2. **Glitter USDC Crosschain Swaps** - The Glitter USDC Crosschain Swaps allow for a seamless and frictionless transfer of native to native USDC between multiple blockchains. In most instances, the transfers take no more than 1 minute, does not involve the creation of any wrapped assets, do not involve the usage of liquidity pools (either within the bridge structure or on a DEX), and do not involve any stablecoins being held inside the bridge vault.\ ***NOTE**: As the Polygon USDC is a bridged version of USDC and not native, the transactions with Polygon take, on an average, 20 minutes. Transactions with Ethereum may take 10 minutes, depending on the network congestion.* 3. **Glitter Software Development Kit (SDK)** - This product allows any protocol to use Glitter’s interoperability solutions in their protocol’s architecture, with no development time. This is open and free technology, developed by Glitter. 4. **Glitter Arbitrage and Liquidation Bot** - this is a custom-made product which allows for crosschain arbitrage as well as crosschain asset liquidation when working with crypto lenders. 5. **Glitter Explorer** - This explorer allows one to use advanced analytics to see any transactions happening on the Glitter platform, crosschain. 6. **XGLI Crosschain Swap** - Our crosschain swap uses the XGLI, a crosschain currency which connects Solana, Algorand, and Ethereum. This is not a wrapped-token product as the XGLI is native to all the blockchains it connects. The XGLI provides a simple, cheap, and seamless way to bridge value across multiple ecosystems. More information regarding the XGLI may be found in [dao.glitterfund.org](https://www.dao.glitterfund.org/). 7. **Glitter Widget** - The Glitter Widget allows for the simplest integration of the Glitter Crosschain Platform for a partner protocol. It features a more tradition crosschain UI design. ### **Glitter Bridge has the following value propositions:** * Our ethos revolves around creating a balanced ecosystem by mixing both EVM and top non-EVM blockchains. Further, we strive to work with not just the most popular blockchains but with blockchains whose technology we believe in. * We offer a seamless DeFi accessibility for the mainstream public who might find navigating other DeFi platforms too abstract to use and plan to integrate DeFi pools directly into the bridge if users choose to use them. These are all embedded with a user-centric interface designed to facilitate easy and intuitive interaction for both novice users and cross-chain innovation * We strive to enhance the current crosschain possibilities. To do this, we are adding cross-chain DeFi into our ecosystem which complements the bridging technology we have developed. Further, we are adding algorithmic trading and automation to our platform, which is meant to help cross-chain and DeFi to scale, and reach a more mainstream audience. # Disclaimer ## The Glitter Finance Users Your use of the Glitter Finance protocol involves various risks, including, but not limited to, losses while digital assets are being supplied to the Glitter Finance protocol and losses due to the fluctuation of prices of tokens in a trading pair or liquidity pool. Before using the Glitter Finance protocol, you should review the [Terms and Conditions](https://www.glitterfinance.org/terms-and-conditions), as well as all disclaimers provided on both the [glitterfinance.org](https://www.glitterfinance.org/) as well as on [bridge.glitterinance.org](https://bridge.glitterfinance.org/) to understand how the Glitter Finance protocol works. The Terms and Conditions along with all Disclaimers provided in all of the Glitter Finance official domains form a binding agreement between you and Glitter Finance (Glitter Finance, UAB and Glitter Finance, OU). You are responsible for doing your diligence on the risks involved. AS DESCRIBED IN THE GLITTER FINANCE PROTOCOL TERMS AND CONDITIONS ([Link](https://www.glitterfinance.org/terms-and-conditions)), THE GLITTER FINANCE PROTOCOL IS PROVIDED "AS IS", AT YOUR OWN RISK, AND WITHOUT WARRANTIES OF ANY KIND. Although Rainbow Network FZCO developed much of the initial code for the Glitter Finance bridge protocol, as well as other various products under the Glitter Finance brand, it does not provide, own, or control the Glitter Finance bridge protocol nor any other products from the Glitter Finance brand, all of which are within the domain of DeFi or Open Finance, which are all run by smart contracts deployed on the Algorand and Solana blockchains. Accordingly, no developer, employee of Rainbow Network FZCO or entity involved in creating the Glitter Finance protocol will be liable for any claims or damages whatsoever associated with your use, inability to use, or your interaction with other users of the Glitter Finance protocol, including any direct, indirect, incidental, special, exemplary, punitive or consequential damages, or loss of profits, cryptocurrencies, tokens, or anything else of value. Please be aware, the [Terms and Conditions](https://www.glitterfinance.org/terms-and-conditions), as supplied on [glitterfinance.org](https://www.glitterfinance.org/), form a binding agreement between you and Glitter Finance, UAB as well as Glitter Finance, OU. Your consent to agree to these [Terms and Conditions](https://www.glitterfinance.org/terms-and-conditions) is given from the moment you connect your wallet. # Avoiding Crypto Scams Glitter Finance staff and team members will NEVER ask for your seed phrase, nor host a website that provides you with a seed phrase. Never share the seed phrase of your wallet with anyone. If you are ever unsure about the authenticity of staff accounts, please use the team verification portal at this address: Further verification information can be found by emailing us via , or reaching out to us via our Telegram messenger customer portal: # Glitter Finance Links Below you can find links for current apps of Glitter Finance Glitter Bridge App - [link](http://bridge.glitterfinance.org) Developer portal for the SDK/bridge integration and token listing - [link](http://portal.glitterfinance.org) Widget - [link](http://widget.glitterfinance.org) Bridge analytics - [link](http://explorer.glitterfinance.org) # Glitter Finance Community Bug Bounty Program Glitter is committed to delivering the safest line of products possible. To achieve our aim, we have an ongoing bug bounty program. We feel having this program will not only allow us to prevent technological vulnerabilities but will also allow us to build true camaraderie with our community. As such, here are the guidelines and payouts available in case of a problem found within any products on public testnet or mainnet released by our protocol: * Low critical UI issues: 100-250 USD * Medium critical UI issues: 200-400 USD * High critical UI issues: 500-1000 USD * Low critical Smart Contract issues: 300-500 USD * Medium critical Smart Contract issues: 500-1000 USD * High critical Smart Contract or Backend issues: 3000-10000 USD Please report the issues via email to: Via telegram by posting in the Glitter group:\ Or send directly to [@defibuilder1](https://t.me/DeFiBuilder1) via a telegram dm. # Bridge FAQ In this section you can find FAQs, instructions, tutorials and other detailed information about how to interact with Glitter Finance and our products. # General Bridge Questions
What are the transaction links shown on finalized bridge diaogue? The bridge works via two transaction groups. One group on Algorand and the other on Solana. Both main transactions groups will be shown in the final bridge dialogue in order to confirm/check on AlgoExplorer and SolScan by the user if desired.
What should I do if I face issues? Please take a screenshot and contact us via our telegram group. You can also reach us by sending an email to
What if it takes too long in some cases? Is there a condition under which my transactions are not confirmed? Network congestion does occur on Solana. We have built in a sensor tool into the bridge which tells you the state of the Solana network. If your transaction fails and you need to be refunded please contact us via our telegram group of send an email to
Is there a server connection to which the frontend communicates? No! The bridge architecture is designed to have front and back ends detached, and they do not directly communicate. They are only connected via blockchain transactions. This way, the need for extra or third-party verifiers gets omitted and the verification consensus is exactly the blockchain's validation consensus and nothing more. We use oracles to do the heavy lifting, of this absent direct communication between front and back ends, and provide more robust security for bridge operations.
# Algorand
What is the minimum for bridging with Algo? The minimum amount for bridging with Algo is 5 Algo. You can bridge as much as you like once you met the minimum requirements set by the bridge.
What is xAlgo? xAlgo is a wrapped Algo token on the Solana network. When you bridge Algos from Algorand to Solana, you receive xAlgo on the destination chain (Solana).
What is ATA and why should I create it prior to bridging Algo to Solana? ATA stands for Associated Token Account, and it is based on the Solana network's architecture that requires an associated account to be generated for every non-native token (Asset) in a user's wallet so that the user is able to send and receive that token (asset). The create ATA button will take care of that process for you, when the app detects that you do not have an associated account for xAlgo on Solana. Please note that the Solana Asset ID for xAlgo is 'HMx8h6yJf7kEMYzrVcgcvLSihrZkLeoXpX6SKrMaNKVK'
What is the minimum USDC balance required to start bridging from/to Algorand? 1 USDC when bridging from Algorand and 1 USDC balance when bridging to Algorand (but 10 USDC if bridging from Ethereum).
What wallets I can use for Algorand? The following wallets are supported on Algorand: * MyAlgo * Pera * Defly * Exodus
# Solana
What is the minimum Sol balance required to start using the bridge? 0.05 Sols when bridging from Sol and non-zero Sol balance when bridging to Sol
What is xSol? xSol is the wrapped Sol token on the Algorand network. When you bridge Sol from Solana to Algorand, you receive xSol on the destination chain (Algorand).
What is Optin and why should I do it prior to bridging Sol to Algorand? On Algorand, before you are able to receive an Asset, you need to optin to it. This will be handled by the system via the optin button. You will get an optin alert when the app detects that you are not opted-into xSol asset on Algorand. Be informed that Algorand Asset ID for xSol is (75394438).
What is the minimum USDC balance required to start bridging from/to Solana? 1 USDC when bridging from Solana and 1 USDC balance when bridging to Solana (but 10 USDC if bridging from Ethereum).
What wallets I can use for Solana? The following wallets are supported on Solana: * Phantom * Solflare
# Ethereum
What is the minimum USDC balance required to start bridging from/to Ethereum? 10 USDC when bridging from Ethereum (plus some ETH for gas fees) and 20 USDC balance when bridging to Ethereum.
What wallets I can use for Ethereum? The following wallets are supported on Ethereum: * Metamask * Coin98 Wallet
# Avalanche
What is the minimum USDC balance required to start bridging from/to Avalanche? 1 USDC when bridging from Avalanche (plus some AVAX for gas fee) and 1 USDC balance when bridging to Avalance.
What wallets I can use for Avalanche? The following wallets are supported on Avalanche: * Metamask * Coin98 Wallet
# Polygon
What is the minimum USDC balance required to start bridging from/to Polygon? 1 USDC when bridging from Polygon (plus some MATIC for gas fee) and 1 USDC balance when bridging to Polygon.
What wallets I can use for Polygon? The following wallets are supported on Polygon: * Metamask * Coin98 Wallet
# Tron
What is the minimum USDC balance required to start bridging from/to Tron? 1 USDC when bridging from Tron (plus some TRX for gas fee) and 1 USDC balance when bridging to Tron.
What wallets I can use for Tron? The following wallets are supported on Tron: * TronLink
# New Interface Overview ## [bridge.glitterfinance.org](https://bridge.glitterfinance.org/) - Interface Overview The Bridge.glitterfinance.org interface is designed for novice users. It simplifies the current cross-chain bridging interface models currently used. ### 1. All bridge steps are separated, step-by-step. The first step needs to be complete, which triggers step two, etc.
### 2. The "Trade" tab allows one to have easy access to the links leading to DEXs where the bridge-created assets are tradeable.
### 3. Clicking on the green circle near the "Services" tag will bring you to the [services status page](https://explorer.glitterfinance.org/status). This page is there to help you identify possible system problems and to create a safer bridging experience. If the circle is any color except green, please hold any further activity.
### 4. At the top, the "Home" button will lead you to [glitterfinance.org](https://www.glitterfinance.org/).
### 5. "APP" button is to come back to [bridge.glitterfinance.org.](#bridge.glitterfinance.org-interface-overview)
### 6. The "Widget button will lead you to [widget.glitterfinance.org](https://widget.glitterfinance.org/). This is the interface we built for users that like the more conventional, cross-chain bridging interface. You can read more about the Glitter Widget here ([Link](https://widget.glitterfinance.org/)).
### 7. "Develop" will lead you to [portal.glitterfinance.org](https://portal.glitterfinance.org/). This portal will allow projects to list their tokens on the Glitter Token Bridge, and to become cross-chain. Listing your token will create wrapped tokens.
### 8. "Documents" will lead you to [docs.glitterfinance.org](https://docs.glitterfinance.org/) and to all of our tutorials.
### 9. "Explorer" will lead you to [explorer.glitterfinance.org](https://explorer.glitterfinance.org/), our advanced analytics tool. Here, you will find full bridge: statistics, analytics tools, full bridge transaction history, as well as access to links within the individual chain scan pages.
### 10. Wallet connection tab, in the top, right-hand corner, will confirm your connected wallets from both the starting chain and the destination chain. The wallets will continue to be connected until you click on the tab to disconnect them, allowing you to perform multiple bridging operations.
### 11. Transaction tab on the bottom reads your wallet and will tell you the status of all of your transactions.
For a more comprehensive record please go to: [explorer.glitterfinance.org](https://explorer.glitterfinance.org/) # Bridging Tutorials How to use Glitter Bridge ## Guide on How to Bridge Assets Cross-Chain **At first, you’re to visit** [**Glitter Bridge**](https://bridge.glitterfinance.org/) **portal**\ **Ensure the url is the same as** [**https://bridge.glitterfinance.org/**](https://bridge.glitterfinance.org/) **to begin the transfer.**
# Algorand to Solana Algorand to Solana Bridging Process ### **1.1 Select Network & Asset** Select Algorand chain in "Choose Chain" section:
### 1.2 **Connect Wallet** Choose a wallet to connect it to the Bridge (you may connect Pera Wallet, DeFly or Exodus) and click the preferred icon:
### 1.3 Example for Pera Wallet (Web): Fill in your password and press the “Connect” button or click on "Connect with Pera Mobile" if you want to use Pera Mobile wallet app:
### 1.4 Choose ALGO token by click on it:
### 1.5 Confirm the chain and connect your Solana wallet:
### 1.6 Confirm the asset for your bridging (right now the only option is xALGO in Solana):
### **1.7 Input Amount** Select the amount of assets you want to bridge:
### **1.8 Review and Confirm Request** Confirm the bridging by pressing "BRIDGE" button:
### 1.9 Sign the transaction in your Algorand wallet and wait a bit to complete the bridging (usually it takes around 20 seconds) :
### **1.10 Bridging Completed** Congratulations! Your bridging has been successfully completed!
### 1.11 Transaction tab on the bottom reads your wallet and will tell you the status of all of your transactions.
### 1.14 Now that you have successfully bridged, use the Trade Tab in User Interface to direct your asset to our partner protocols for trading:
# Solana to Algorand Solana to Algorand Bridging Process ### **1.1 Select Network & Asset** Select Solana chain in "Choose Chain" section:
### 1.2 **Connect Wallet** Choose a wallet to connect it to the Bridge (you may connect Phantom or Solflare wallet) and click the preferred icon:
### 1.3 Example for Solflare Wallet (Web): Fill in your password and press the “Connect” button:
### 1.4 Choose SOL token by click on it:
### 1.5 Confirm the chain and connect your Algorand wallet:
### 1.6 Confirm the asset for your bridging (right now the only option is xSOL in Algorand):
### **1.7 Input Amount** Select the amount of assets you want to bridge:
### **1.8 Review and Confirm Request** Confirm the bridging by pressing "BRIDGE" button:
### 1.9 Sign the transaction in your Algorand wallet and wait a bit to complete the bridging (usually it takes around 20 seconds) :
### **1.10 Bridging Completed** Congratulations! Your bridging has been successfully completed!
### 1.11 Transaction tab on the bottom reads your wallet and will tell you the status of all of your transactions.
### 1.14 Now that you have successfully bridged, use the Trade Tab in User Interface to direct your asset to our partner protocols for trading:
# USDC: Swap Tutorial On Algorand to Avalanche Example ### **1.1 Select Network & Asset** Select needed chain in "Choose Chain" section (Currently supported chains are Algorand, Solana, Ethereum, Avalanche, Polygon and Tron):
### 1.2 **Connect Wallet** Choose a wallet to connect it to the Bridge (you may connect Pera Wallet, DeFly or Exodus) and click the preferred icon:
### 1.3 Example for Pera Wallet (Web): Fill in your password and press the “Connect” button or click on "Connect with Pera Mobile" if you want to use Pera Mobile wallet app:
### 1.4 Choose USDC token by click on it:
### 1.5 Confirm the destination chain and connect your wallet (we are using Avalanche with Metamask for example):
### 1.6 Confirm the asset for your bridging (USDC will be automatically chosen):
### **1.7 Input Amount** Select the amount of assets you want to bridge:
### **1.8 Review and Confirm Request** Confirm the swap by pressing "SWAP" button:
### 1.9 Sign the transaction in your Algorand wallet and wait a bit to complete the bridging (usually it takes around one minute, but can be up to 20 minutes for Ethereum and Polygon):
### **1.10 Bridging Completed** Congratulations! Your bridging has been successfully completed! \ **Please note**: *Depending on destination chain you'll receive your tokens in a few minutes. Swap can be proceed in up to 20 minutes for Ethereum and Polygon because of network usage (high network load).*
### 1.11 Transaction tab on the bottom reads your wallet and will tell you the status of all of your transactions.
# USDC and EUROC Transfer Cross-Bridge Native USDC and EUROC ## Introduction #### Description of the service: Glitter Finance provides a DeFi, permissionless and direct mode of bridging (bridging-as-a-service) native USDC between all blockchains that support native USDC. Glitter Finance reserves the right to cap the transaction amounts going through the Glitter Bridge in the interest of AML and at the request of law enforcement. All transactions are visible on [explorer.glitterfinance.org](https://explorer.glitterfinance.org). The bridge fee for all USDC and EUROC transactions will be 0.5%. The minimal executed amount per transaction is 1 USDC. #### Advantages of the Glitter USDC Bridge: * Only native to native USDC and EUROC transfer. Glitter Finance does not wrap the USDC and EUROC; * Supporting all the native USDC blockchains. We do not bridge USDC where USDC is bridged; * No liquidity pools, which means no wait time to bridge. #### The Glitter Finance USDC and EUROC Bridge lowers cross-chain risks. * USDC which is swapped is not held inside the Bridge Vault. As such, there is a significantly reduced risk of hacking. * By not wrapping tokens, we do not create derivatives which can depeg during a bear market or through the shorting of the derivative. * By not using integrated liquidity pools to bridge stable coins we do not create a case of stagnant liquidity sitting in a liquidity pool and potentially depreciating with the bear market. * Further, the end-user does not have to wait for a liquidity pool to have liquidity in order to bridge the stable coin. #### USDC Crosschain Swap - Supported Networks: * Ethereum, Algorand, Solana, Tron, Avalanche, Polygon #### EUROC Crosschain Swap - Supported Networks: * Ethereum, Avalanche This accomplishes our aim, which is frictionless, cross-chain, stable-coin bridging. **Find the audit of the USDC swap** [**here**](https://drive.google.com/file/d/19wg7q60i6Z5eZyjA6BPos3Dk6AG1kVad/view?usp=sharing) {% hint style="warning" %} This page documentation is currently in progress. Contact Us [here](https://www.glitterfinance.org/contact-us) in case you have any question {% endhint %} # Supported Wallets The platform currently supports the following wallets:
Algorand
  • MyAlgo
  • Pera
  • Exodus
  • Defly
Solana
  • Phantom
  • Solflare
Ethereum
  • Metamask
  • Coin98 Wallet
Avalance
  • Metamask
  • Coin98 Wallet
Polygon
  • Metamask
  • Coin98 Wallet
Tron
  • TronLink
Sollet was supported on Solana but is no longer in use by the Solana ecosystem. # Wallets Compatibility / Mapping Here you can see information about wallet pair that will work for different scenarios. ### How to use: 1. From tabs below select destination chain tab. 2. Find a Row with your source chain and wallet. 3. Match it with Columns for supported wallets on destination chain. If you have "Yes" in a matching cell - such combination will work for swapping. If "No" - unfortunately this option is still under development and most probably will be added in nearest updates. ### For Mobile: {% tabs %} {% tab title="To Ethereum" %} | From \ To | Eth-Metamask | Eth-Coin98 | Eth-WalletConnect | | ------------------ | ------------ | ---------- | ----------------- | | AVAX-Metamask | No | No | No | | AVAX-CoreApp | No | No | No | | AVAX-WalletConnect | No | No | Yes | | | | | | | Algo-Defly | No | No | Yes | | Algo-Pera | No | No | Yes | | ALgo-Exodus | No | No | Yes | | | | | | | Solana-Phantom | No | No | No | | Solana-Solflare | No | No | Yes/ Broswer | | {% endtab %} | | | | {% tab title="To Avalanche" %} | From \To | AVAX-Metamask | AVAX-CoreApp | AVAX-WalletConnect | | ----------------- | ------------- | ------------ | ------------------ | | Eth-Metamask | No | No | No | | Eth-Coin98 | No | No | No | | Eth-WalletConnect | No | No | Yes | | | | | | | Algo-Defly | No | No | Yes | | Algo-Pera | No | No | Yes | | ALgo-Exodus | No | No | Yes | | | | | | | Solana-Phantom | No | No | No | | Solana-Solflare | No | No | Yes/ Broswer | | {% endtab %} | | | | {% tab title="To Algorand" %} | From \To | Algo-Defly | Algo-Pera | ALgo-Exodus | | ------------------ | ------------ | ---------------------------------------- | ---------------------------------------- | | Eth-Metamask | No | No | No | | Eth-Coin98 | No | No | No | | Eth-WalletConnect | Yes | No/ it distracts and opens pera for sign | No/ it distracts and opens pera for sign | | | | | | | AVAX-Metamask | No | No | No | | AVAX-CoreApp | No | No | No | | AVAX-WalletConnect | Yes | No/ it distracts and opens pera for sign | No/ it distracts and opens pera for sign | | | | | | | Solana-Phantom | No | No | No | | Solana-Solflare | Yes/ Broswer | Yes/ Broswer | Yes/ Broswer | | {% endtab %} | | | | {% tab title="To Solana" %} | From \To | Solana-Phantom | Solana-Solflare | | ------------------ | -------------- | --------------- | | Eth-Metamask | No | Yes/ Broswer | | Eth-Coin98 | No | Yes/ Broswer | | Eth-WalletConnect | No | Yes/ Broswer | | | | | | AVAX-Metamask | No | Yes/ Broswer | | AVAX-CoreApp | No | Yes/ Broswer | | AVAX-WalletConnect | No | Yes/ Broswer | | | | | | Algo-Defly | No | Yes/ Broswer | | Algo-Pera | No | Yes/ Broswer | | ALgo-Exodus | No | Yes/ Broswer | | {% endtab %} | | | | {% endtabs %} | | | ### For Desktop: {% tabs %} {% tab title="To Ethereum" %} | From \To | Eth-Metamask | Eth-Coin98 | Eth-WalletConnect | | ------------------ | ------------ | ---------- | ----------------- | | AVAX-Metamask | Yes | No | Yes | | AVAX-CoreApp | No | No | Yes | | AVAX-WalletConnect | Yes | Yes | Yes | | | | | | | Algo-Defly | Yes | Yes | Yes | | Algo-Pera | Yes | Yes | Yes | | ALgo-Exodus | Yes | Yes | Yes | | | | | | | Solana-Phantom | Yes | Yes | Yes | | Solana-Solflare | Yes | Yes | Yes | | {% endtab %} | | | | {% tab title="To Avalanche" %} | From \To | AVAX-Metamask | AVAX-CoreApp | AVAX-WalletConnect | | ----------------- | ------------- | ------------ | ------------------ | | Eth-Metamask | Yes | No | Yes | | Eth-Coin98 | No | No | Yes | | Eth-WalletConnect | Yes | Yes | Yes | | | | | | | Algo-Defly | Yes | Yes | Yes | | Algo-Pera | Yes | Yes | Yes | | ALgo-Exodus | Yes | Yes | Yes | | | | | | | Solana-Phantom | Yes | Yes | Yes | | Solana-Solflare | Yes | Yes | Yes | | {% endtab %} | | | | {% tab title="To Algorand" %} | From \To | Algo-Defly | Algo-Pera | ALgo-Exodus | | ------------------ | ---------- | --------- | ----------- | | Eth-Metamask | Yes | Yes | Yes | | Eth-Coin98 | Yes | Yes | Yes | | Eth-WalletConnect | Yes | No | No | | | | | | | AVAX-Metamask | Yes | Yes | Yes | | AVAX-CoreApp | Yes | Yes | Yes | | AVAX-WalletConnect | Yes | No | No | | | | | | | Solana-Phantom | Yes | Yes | Yes | | Solana-Solflare | Yes | Yes | Yes | | {% endtab %} | | | | {% tab title="To Solana" %} | From \To | Solana-Phantom | Solana-Solflare | | ------------------ | -------------- | --------------- | | Eth-Metamask | Yes | Yes | | Eth-Coin98 | Yes | Yes | | Eth-WalletConnect | Yes | Yes | | | | | | AVAX-Metamask | Yes | Yes | | AVAX-CoreApp | Yes | Yes | | AVAX-WalletConnect | Yes | Yes | | | | | | Algo-Defly | Yes | Yes | | Algo-Pera | Yes | Yes | | ALgo-Exodus | Yes | Yes | | {% endtab %} | | | | {% endtabs %} | | | # Bridging Security ### Disclaimer for the Systems Status Page This [status page](https://explorer.glitterfinance.org/status) shows the state of our backend services. If there are any issues with our server performance and responsiveness, they will be shown here. While we do our best to make any service disruption transparent, there are a number of issues that can still occur when the status of a service is green. When a service is up and running, there is no guarantee that a transaction will still go through immediately. Failed simulations, errors or RPC issues with the blockchains can cause transaction disruptions. Our goal is to make all of our services as robust as possible to eliminate each and every one of these issues, but as we grow and expand our services, some of these transaction disruptions can still occur until they are fully diagnosed and patched. Please use this tool in conjunction with [explorer.glitterfinance.org](https://explorer.glitterfinance.org/) to check the status of both the backend servers and the status of any individual transactions. For support, please write to: \ Go to our Discord channel and report the issue: \ Report in our telegram group: ### Bridging Security The Glitter team has built in multiple sensors into our platform to make sure that all transactions happening on the Glitter platform are safe and secure for the user. 1\. We have built in a Health status page which all users of the Glitter platform should consult when doing bridging or swapping on the platform. The system’s Health notification is located in the top, right-hand corner of bridge.glitterfinance.org, as well as in the same location in [explorer.glitterfinance.org](https://explorer.glitterfinance.org/).
Please note the color of the Health symbol. Any color outside of green should prompt the user to click on the symbol, and take a look at the Services Status page for information on the status of all services. **To get to the Service Status page, please click directly on the colored circle.** The Services Status page can be seen here: **Please note: any color outside of GREEN should prompt a halt in bridging.** 2\. Information about the Audits for the various Glitter Platform components will be shared in the sections following this one. # Audits Glitter Bridge is fully Audited by Ackee Blockchain, Certik, RD Auditors ## **MVP Audits:** 1. Bridge penetration and Load Tests [**Here**](https://www.rdauditors.com/wp-content/uploads/2022/06/Glitter-Finance-Penetration-and-Load-Testing-Summary-Report.pdf) 2. Certik Algorand Audit [**Here**](https://www.dropbox.com/s/nqzsd88tw1h769z/certik_glitter_finance_algorand_audit.pdf?dl=0) 3. Certik Algorand Addendum [**Here**](https://www.dropbox.com/s/figklngtevy99go/certik_glitter_finance_algorand_addendum.pdf?dl=0) 4. Certik Solana Audit [**Here**](https://www.dropbox.com/s/7j8bjlmaxdp1apn/certik_glitter_finance_solana_audit.pdf?dl=0) 5. RD Auditors Solana Audit Report [**Here**](https://www.dropbox.com/s/evyz8fzt8ktb09w/RD_Audit.pdf?dl=0) ## **USDC Swap Audits:** 1. Audit Report for USDC Swap [**Here**](https://drive.google.com/file/d/19wg7q60i6Z5eZyjA6BPos3Dk6AG1kVad/view) ## Token Bridge v2: 1. EVM Contract Audit [**Here**](https://docsend.com/view/4ypv7h8c3xbffrr9) 2. Backend Audit [**Here**](https://docsend.com/view/rc9bcpzdedudiwed) # Incorrect/Failed Transactions When bridging from one chain to another we attach data to the transactions on both chains which include: * Source address; * Destination address; * Chain names; * Amounts. Failed deposits are bridge transactions initiated by anyone/end-user but either with incomplete information of any one of the above data, or incorrect or malicious information. Incomplete Information: this means that they don't provide a destination address. Another example of incorrect Information: the user specified that the destination chain is Solana but provided us destination address of Algorand. Malicious information: This means they transfer a small amount and try to bridge a large amount (attack vector). On the other hand, failed transfers are valid in the sense that all data we need for bridging is available to us and correct. However, during the process of bridging some error occurred which can be things like network congestion on any of the networks or any of the API routes failing. # Bridge Core MVP # Disclaimer and Key Terms ### Disclaimer All digital assets (“tokens”) which are affiliated with Rainbow Network FZCO and our platform/brand Glitter Finance ([glitterfinance.org](https://www.glitterfinance.org/)) are intended for users who are located in countries that treat tokens as utilities. Users in any countries that treat digital assets as securities are strictly prohibited from participating. As we are a decentralized (“DeFi”) and permissionless platform, we are not responsible for any violations of local laws or regulations by users who participate in our platform or trade any tokens associated with our platform, in spite of our legal warnings, and who break the Terms and Conditions on [glitterfinance.org](https://www.glitterfinance.org/). By using our website, you acknowledge and agree to comply with all applicable laws and regulations in your jurisdiction as well as our [Terms and Conditions](https://www.glitterfinance.org/terms-and-conditions). ### Wrapped token A wrapped token is a derivative of a native token. Wrapped tokens are created when a user locks the original token as collateral inside the bridge vault in blockchain 1, and then what the bridge releases is a wrapped token (or a derivative of the locked collateral) on blockchain 2. Currently, the two wrapped tokens that the Glitter Bridge produces are: * **XSOL** - this is a wrapped Solana on the Algorand Network. * **XALGO** - a wrapped Algo on the Solana Network. ### Native Crosschain Stablecoin Swap A native swap is different from a wrapped token in that no derivative is being produced. Instead, Glitter swaps a stablecoin, such as **USDC**, and what is actually being swapped is the blockchain, instead of a token. This is because Glitter works with stablecoins native to the blockchains between which the crosschain swap happens. As such, one can swap USDCs on Solana for a USDCa on Algorand. # Bridge Core MVP # Core Concept ## **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.
# Bridge Relayer The Glitter Finance Bridge Relayer will serve as a relay protocol for the Glitter Bridge across supported chains to pass validation messages and requests across the bridge smart contract. The Bridge Relayer provides decentralized messaging protocols for bridge operations across all supported chains. The Bridge Relayer on IBC protocol will help create messages to be relayed from one ledger to another by monitoring “relayer processes”. These relayers continuously scan the state of ledgers that implement the IBC protocol and relay packets when these packets are present. This enables transaction execution on connected ledgers when outgoing packets relayed over have been committed. The implementation of the Glitter Bridge Protocol is based on lock and release and the standard mint and burn bridging mechanism which will be communicated across the bridge networks using Bridge Relayer. The Glitter Bridge Decentralized Protocol will provide the following benefits: * Decentralized bridge operations and validation * Decentralize Glitter bridge messaging services to increase reliability and security * Keep an immutable record of all bridge transactions to increase transparency The use of the relay chain protocol will set in motion the full decentralization of the Glitter Bridge. Glitter Finance is to be as transparent and decentralized as possible and in keeping with the ethos of blockchain, Glitter Finance will take our decentralized approach a step further through its Bridge Relayer. # Sending Request ### **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
# Receiving Request ### **Protocol Gateway B** The gateway protocol B (contract) receives an approval message from gateway A and the validator node on the secondary chain verifies the message and initiates the mint contract to create (mint) the wrapped equal amount of the locked asset on the target chain.
Wrapped token can be redeemed to native token on the primary chain through the glitter bridge. The secondary chain smart contract sends a request to unlock locked assets on the primary chain which the oracle protocol certifies the existence of the wrapped asset and the collateralized locked asset. Equal amount of the native asset is unlocked on native chain and the equal of the wrapped asset is burnt and completely removed from circulation. ### **Secondary/Destination Chain** This is the chain where a minted token will be received by the user or burnt after a bridge transfer action that lock/unlock token on the primary chain has been executed.
### **Mint and Burn** Glitter Bridge protocol uses the mint and burn protocol smart contract function to mint wrapped token on destination chain and burn wrapped token when unwrapping the asset. This allows the Glitter bridge to ensure wrapped tokens do not get circulated without the peg of native assets.
# Glitter Bridge Protocol The Glitter Bridge protocol enables cross-chain transfer of assets from layer 1 blockchains to another layer 1 blockchain seamlessly. The Glitter Bridge runs distributed self-approving cross-chain nodes hosting the blockchain network nodes and oracle protocols to validate transaction requests and operations that verify the authenticity of bridging activity. The Glitter Bridge operation uses a hosted node that certifies token lockup deposits on one chain in order to mint / unlock wrapped tokens on the other, and vice versa. The local node expresses high performance based on the bridging networks which allows high-speed bridge transactions with a reliable and secure protocol for enhanced security. The Glitter Bridge implementation functions by transmitting protocol messages across Algorand to Solana in a bidirectional fashion while bridging. The bridge cross-chain protocol is designed for easy integration of more blockchain networks to provide robust asset transfer across multiple chains.
The powering technology allows bridging transactions to be executed fast across all bridged networks. A dependency that amounts to delayed transactions is on the primary blockchain and secondary blockchain to transfer assets and receive assets, also their network congestion conditions. If these two chains express a fast network TPS, the bridging transfer of assets will be completed simultaneously. The overall average of one bridging session to fulfill correctly and completely is measured to be under 40 seconds so far. # Relaying Request ### **Relayer** Asset transfer across chains is based on the consensus among the local nodes which serve as the validators on Glitter Bridge. Protocol A and protocol B of both primary and secondary chain must arrive at a consensus from each side of the chain smart contract and oracle request to successfully approve the mint and burn request across two chains that assets have been transferred. The Glitter Bridge smart contract allows these two chains to communicate request and approval messages from each respective node via a Relayer.
# Token Bridge v2 ## Glitter Bridge Node Validator The `glitter-bridge-token-node` is a blockchain network validator connected to multiple chains and providing functionality for bridging assets across them, by interacting with smart contracts on individual chains.
# Infrastructure Glitter Node Validator is a node application deployed to multiple running instances that are communicating through a shared database. Each validator owns an account for each blockchain network configured and secretly stored in the vault. Each validator has an internal scheduler for jobs to perform periodically: * create release transactions, * sign release transactions, * execute signed transactions, * delete old done transactions. In case any of the jobs fails, the error is logged and the validator continues with the next job in the row. All validators are connected to the smart programs on configured blockchain networks that are processing multi-signature release requests on the target network. Each validator represents one unit in the multi-signature process which is accepted by the network only if the configured amount of validators signed the requested transaction. ### EVM Networks A multi-signature process on the Ethereum Virtual Machine compatible chains is provided and secured by the [Safe Global](https://safe.global/) infrastructure. Smart contract operating on the EVM chain accepts release requests signed by configured Safe account. Validators are storing transaction data on the Safe Global and approving the transaction execution. Once the transaction execution request is accepted, Safe validates the signatures and executes the transaction. This process was tested on these networks: * Ethereum * Arbitrum * Polygon * Avalanche * Binance Smart Chain * Polygon zkEVM * Optimism ### Solana Release transactions executed on Solana are signed using the deployed instance of [coral-xyz/multisig program](https://github.com/coral-xyz/multisig). Similar to the EVM networks, the smart program on Solana performing the release transaction is expecting only the Multisig program signature. Validators have configured multi-signature accounts with the specified threshold. During the release transaction creation, transaction data are stored in the account on the chain. Once all validators approve the transaction using the Multisig program, the transaction is executed. After signature validation, Mutlisig program signs the transaction data and executes the transaction by calling the smart program. # Lifecycle of the validator A user of the Glitter Bridge starts the bridging process by creating a deposit transaction on the origin network with a smart program. This transaction contains routing information about the target chain, target wallet, and information about bridged tokens and their amount. Each validator periodically checks for the new deposit transactions on all configured chains with Glitter SDK Scroller. Validator first exclusively claims the latest scroller cursor for the available blockchain network from the shared database. This cursor is locked for other validators until the scrolling process is finished. The retrieved transactions from Glitter SDK are validated against the validator's configuration including database settings of all existing tokens for each chain. Invalid transactions are stored in the `error_transactions` working as a dead letter queue for further investigation and possible retry mechanism (not implemented yet). If the transaction passes the validation process, the validator creates and signs a release transaction on the target chain and saves the serialized transaction blob in the `multisig_transactions` table. Other validators are periodically checking the database for release transactions that are waiting for their signature. These transactions are picked up by the validator from the database, signed with the chain-specific mechanism, and the validator appends its id to the list of the signers stored in the database together with the transaction blob. Once the multi-signature threshold is achieved, the release transaction is picked up by a random validator and executed on the specific chain.
# Potential issues ### Parameters: * `TRANSACTION_RETENTION_TIME`: The time after which we can remove data of the processed transactions * `CURSOR_CLAIM_TIMEOUT`: Maximum time we are willing to block accepting of the deposit transactions on a single network (after the timeout, the same page starts being processed again by available worker) ### **Validator didn't finish scrolling the deposits** Failing to process the deposit transactions batch from the scroller results in failing to advance the scrolling cursor. The remaining data is not lost and will be eventually picked up (see `Cursor not released`) again by the next validator or the same validator in the next job cycle. This can lead to creating identical transactions in the database, which is discussed in `Transaction duplicated when in progress` and `Transaction duplicated when finished`. ### **Transaction is duplicated when being processed** Transactions in progress are always stored in the database and the repository makes sure that duplicate release transactions (duplications by the id of the relevant deposit transaction) are not created. ### **Transaction is duplicated when finished** When the release transaction is performed on the chain, it is still stored in the transactions queue with the finished state. The finished transactions are eventually removed from the database after `TRANSACTION_RETENTION_TIME`. Validator doesn't allow to create transaction when `TRANSACTION_RETENTION_TIME` elapsed since claiming the scrolling cursor. If the time already passes, the validator continues the loop (same as if it errored), leaving the scrolling cursor locked. ### **Cursor not released** If a validator errors before releasing the cursor or the processing of the transaction takes too long, the cursor remains locked. After safe timeout `CURSOR_CLAIM_TIMEOUT` the cursor is considered released and other validators can claim the cursor again. The errored validator doesn't update the cursor if `CURSOR_CLAIM_TIMEOUT` has passed since claiming the cursor. ### **Updated before saving** Read + update steps in a concurrent environment can result in lost updates (A reads, B reads, B updates, A updates -- B's update is lost). This means validators can fetch the transaction to be signed, try to sign it and their update of the transaction in the database will be lost by the write operation of the concurrent validator or the signature update can fail (conditioned that the state is unchanged from the read). If the failure occurs or the update is lost, the worker will try re-signing in the next round which will result in correcting the database state. ### **Transaction is sent again** Due to the unreliable state (see `Marking as completed fails`), there must be a step to prevent duplicate transaction execution. ### **Solana** The Multisig program is not allowing multiple executions of the same transaction and fails with `The given transaction has already been executed.` ### **EVM** All the release transactions are created and called with Safe Global, where no duplicate transaction executions are allowed, transactions fail with `Already known` ### **Transaction is rejected** If the transaction is rejected, the transaction is moved to the dead letter queue, if this process fails, the next validator will perform the same operation. ### **Marking as completed fails** The transaction execution and change in the database cannot be performed in a transaction-safe manner, we must assume this step will fail. The execution needs to handle the duplicates (see `Transaction is sent again`) and if the duplicate is detected, the state of the transaction needs to be corrected. # Supported Networks, Token Bridge v2 ### Supported Networks, Token Bridge v2: * Ethereum * Arbitrum * Optimism * Polygon * Avalanche * BNB * zkEVM #### Future integrations: Casper, Sei, Algorand, Solana # Supported Networks, Token Bridge MVP v1 ### Supported Networks, Token Bridge MVP v1 * Algorand * Solana # Glitter SDK ### Glitter Software Development Kit (SDK) The Glitter team has developed a SDK which allows any protocol to instantly become interoperable and to bridge tokens cross-chain, via the Glitter Bridge. The integration would allow our partner protocols to use their branding on top of Glitter technology and would entail a revenue-sharing partnership model. The Glitter team is there to assist any parties interested in using our open SDK. The current version of the SDK is an MVP, and we are open to suggestions regarding improvements and enhancements. Here are some links for the SDK: ### Github: * ### Npm: * * ### Examples: * ### SDK-Docs: * Please send any questions to: # Glitter Widget ## Glitter Widget The Glitter Widget is built on the idea of making the user experience more flexible. Here are the use cases for the Glitter Widget: * It functions as a more convenient bridging UI for mobile bridging. * It allows partner protocols to use our frontend and backend in a flexible way seamlessly. * It is a UI with a format more familiar to the native crypto user, giving options to the bridge user experience. * The code on the bottom allows for the simplest possible integration of the Glitter Token Bridge and USDC Swap Protocol.
Find the Glitter Widget here: [widget.glitterfinance.org](https://widget.glitterfinance.org) # Supported Tokens ### Tokens Currently Supported: * **Algorand**: ALGO, USDC, xSOL (wrapped Solana) * **Solana**: SOL, USDC, xALGO (wrapped Algorand) * **Ethereum**: USDC, EUROC, NOSEC, XGLI * **Avalanche**: USDC, EUROC * **Tron**: USDC * **Polygon**: USDC * **Arbitrum**: xNOSEC, XGLI * **BNB**: xNOSEC # Glitter Bridge Explorer ### **Glitter Bridge Explorer** The Glitter Bridge Explorer ([explorer.glitterfinance.org](https://explorer.glitterfinance.org)) is an advanced, open analytics tool which allows anyone to examine all transactions going through the Glitter Bridge. All transactions going through [explorer.glitterfinance.org](https://explorer.glitterfinance.org) are fully visible there. This includes all multi-chain USDC and any other stablecoin transactions. Bridge transaction events will be powered by an open protocol that provides a public url source view of all bridging activities; Lock, Mint, Unlock, Burn, Sent Address, Receive address and time of event to access the public records of all bridge transactions. View the bridge explorer [here](https://glitter-finance-explorer-frontend.pages.dev/) {% hint style="warning" %} This document is constantly updated and the content therein are subject to change either as a whole or with minor modifications {% endhint %} # Glitter Bridge Explorer Guide The instruction how to use Glitter Bridge Explorer At first you’re welcome to visit to use Explorer: ![](/files/yp8Y66tge0Pv07iDlCvo) ## Explorer’s interface ### 1.1. **Search bar** This is the main bar of the Explorer. You may use it to search by keyword (such as 'Ethereum'), by transaction ID (TX), wallet address or even two wallet addresses (the further info below). Just write down the info you’re looking for and press ‘Search’ button or ‘Enter’ ![](/files/dMKzDyYSj47GqosKr2ER) ### 1.2. Bridge Activity The first section of the Explorer gives full analytics as to the bridge activity.
### 1.3. **Latest transactions** The list of recent transactions via the Bridge. You may use special icons to have a look at the transaction on Algoexplorer (1) or Solscan (2). By pressing the ‘View all transactions’ (3) button you may see the full list of transactions with the navigation buttons. ![](/files/HNuii1BFvbctZnAM0gNG) ### 1.4. **Bridge Transactions History** The second page gives access to more comprehensive bridge transaction history.
### 1.5. **Transaction Details** You can click on the highlighted transaction to have access to more complete details.
All addresses, as well as the transaction hash are clickable and will lead you to results within the individual chain's scan page.
## Search Options ### 2.1. **Search by TX** 2.1.1. Paste the TX ID into the search bar and press ‘Search’ button or ‘Enter’ ![](/files/nif5QIwR0BINeh1lQ6gS) 2.1.2. Examine the information about transaction ![](/files/maKCuVvJzxtMPV5YsTbA) ### 2.2. **Search by Wallet** 2.2.1. Paste the wallet address into the search bar and press ‘Search’ button or ‘Enter’ ![](/files/sfhouqouT8h6LnXV1aXP) 2.2.2. You shall see the list of all transactions made via the Bridge with a chosen wallet ![](/files/3BOkVZM9w7iuqXEoYtGI) ### 2.3. **Search by Two Wallets** 2.3.1 Paste the two (2) wallets used for bridging (Algorand and Solana) into the search bar and press the ‘Search’ button or ‘Enter’. (!) Use a comma between the wallet addresses. ![](/files/6kPcI5sMgwWcDJV0xAAO) 2.3.2. You shall see the list of all transactions made via the Bridge with the chosen wallets #1 and #2 ![](/files/7bbAH0sRJaLi5cTj0Xf6) ### 2.4. Search by Status You can search for transactions in the explorer via status. To do this click on the 3-bar sign, near the Status header.
Green color next to a transaction implies a **successful** transaction:
Red implies a **failed** transaction:
Yellow color and the word ‘**Pending**’ next to a transaction implies the bridge is processing the transaction:
Blue color with the word ‘**Refund**’ implies that the bridge transaction failed and the bridge issued a refund:
**Gas Ratio** - this means that the transaction did not have enough value sent from one chain to another to pay for the gas fee and for the the rest of the amount to be delivered (the gas fee having eaten all the amount sent).
**DevTest** - This implies that the underlying transaction was performed by ecosystem developers to test the new technology being deployed, or to fix existing technical bugs.
**No Deposit** - means that no deposit was submitted when the transaction was initiated.
**Not Opted In** - The Algorand blockchain requires the receiving wallet to be opted into an asset before receiving it. Should the user try to bridge to Algorand without your wallet being opted in, the bridging will fail. In this instance, the explorer will show this message.
### 2.5. Search by Network You can filter your search by network. Click on the three-line-bar sign:
Choose network:
### 2.6. Search by Amount If you click on the arrow next to the ‘Amount’ header, and the button is facing down, you will be able to search by the biggest amounts that have been passed through the bridge, from the very top of the explorer transaction review. If the arrow is facing up, then you are viewing the smallest amounts from the top of the search in the explorer.
### 2.7. Search by Time Period When the arrow is facing down next to the “Time Ago” header, the explorer will show the latest transactions. When the arrow is facing up it will show the transactions recorded from the beginning of bridge operations.
## Export Results ### 3.1. Export Results To export full bridge transaction data to Excel, please click here:
# Deep Analytics **The Deep Analytics allow for deep data analysis of all the platform transactions. These include both the USDC Protocol and the Token Bridge.** To enter the Deep Analytics click here:
Click on an individual graph to enlarge to a more detailed screen:
Data in complex graphs is layered, so clicking the different boxes on top will allow you to see more complex data layers:
# Glitter Arbitrage Bot ## Glitter Arbitrage Bot The Glitter team has developed an Arbitrage Bot which allows for automated cross chain arbitrage across a variety of cryptocurrencies and protocols. This is accomplished as follows: 1. Connect to configured Algorand and Solana accounts for executing arbitrage operations. 2. Choose one of 6 potential Arbitrage Strategies (at random) with a random amount that is between 5 and 25% of the balance of the Algorand or Solana accounts for a given currency. 3. Simulate the arbitrage strategy by obtaining quotes from every bridge or exchange step along the arbitrage loop\*. At this point no arbitrage or transactions are committed. 4. Using the stimulation at step 3, the Bot evaluates if a profit is generated from the arbitrage loop. If there is a profit to be gained that is above a configured threshold, the bot executes that specific arbitrage loop. The bot then stores any profits gained in its associated accounts to fund future arbitrage. # What are Arbitrage Loops? Arbitrage loops can be thought of as chained loops that execute configured sequences of cross-chain bridging via the [Glitter SDK](https://docs.glitterfinance.org/bridge-core-and-dev-tools/glitter-sdk) and subsequent swap operations over the SDKs of decentralised exchanges. These loops are configured to execute every few minutes and in essence this enables operations to execute using strategies like the following: 1. Bridge from a cryptocurrency on a given network (such as ALGO on Algorand) to a wrapped token on another network (such as xALGO on Solana) via the Glitter SDK. 2. Swap the wrapped token from the previous step (e.g. xALGO) for a given network’s primary currency (such as SOL on Solana) in a liquidity pool via an exchange SDK (such as the Raydium SDK). 3. Bridge the token (e.g. SOL) received at the previous step via the Glitter SDK to obtain another network’s wrapped currency (in this case xSOL on Algorand). 4. To complete the loop, swap the wrapped token (i.e xSOL on Alogrand) for a network’s primary currency (ALGO) using an exchange SDK (such as the Tinyman SDK). We have deemed loops like the one above the “Wrapped Token Arbitrage” strategy of performing token arbitrage, and aim to explore and develop upon this initial approach going forward. Further strategies and protocols are coming soon! # State of the Project ## Glitter Arbitrage Bot It is also worth noting that a goal of this project is not only to generate revenue via the successful arbitrage of popular cryptocurrencies, but also to help stabilise the exchange networks and products offered by Glitter and its various partners. The current state of the Arbitrage Bot is an MVP and we are open to suggestions regarding improvements and enhancements of it. Here are some links/partners for it: ## Github: {% embed url="" %} ## Cryptocurrency Support: * ALGO (Algorand) * SOL (Solana) * xALGO (Solana) * xSOL (Algorand) * USDC (Algorand/Solana) * xGLI (Solana) ## Exchange and Liquidity Pool Support: * [Tinyman](https://tinyman.org/) (Algorand) * [HumbleSwap](https://app.humble.sh/pool) (Algorand) * [Raydium](https://raydium.io/) (Solana) # Logo Example of usage of our Logotype:

Correct example

# Clearspaces ### Free space - at least half the size of the box - logo:
### Free space only box - at least a quarter of the size of the box - logo:
# Logo Dont's ### Don't add shadows behind the logo:
### Don't add strokes:
### Don't change the colors of the logo:
### Don't pull the logo:
### Don't use a bad quality logo:
# Logo Assets ## In this section you can find ready-to-use assets for our logotype. # Horizontal logotype

Horizontal logotype

Horizontal logotype download: {% file src="/files/agYh041Gn4qyZuIXt1Cl" %} {% file src="/files/MGTbFaqay95air2qp73j" %} # Vertical logotype Vertical logotype download: {% file src="/files/my4wtv0HwNmDG50H3Yig" %} {% file src="/files/G2G0CxQGMTgQdK6JAPVa" %} # Logotype Box Logotype Box download: {% file src="/files/be4Za3GtLIf2JJ7nL4wV" %} {% file src="/files/wjtoUGKyBlpjotr0s3Lc" %} # Glitter Colors ### Below you can find Glitter Brand Colors:

F66FC0

30E2E4

A56DF4

### Glitter gradients usage examples:

Blue gradient

Purple gradient

# Backgrounds ## Glitter Brand Backgrounds:

Dark Background

White Backgroung

You can download ready-to-use images: {% file src="/files/xVx1gMexAaGAAuadLhSv" %} {% file src="/files/HOZumpiI2yzPu50PyTKQ" %} # Overview A Complete Cross-Chain Financial Ecosystem Built on Cosmos ## Rainbow Network The Rainbow Network is a Cosmos-based blockchain, using the Tendermint consensus, which is the next stage of the growth and evolution of Glitter. Glitter and Rainbow are sister protocols, which together optimize the cross-chain space, and work together to maximize cross-chain liquidity. As discussed in previous sections, Glitter is a base layer which creates interoperability by using interoperability technologies to facilitate movement of assets across blockchain networks. These include: wrapped tokens, stablecoin cross-chain swaps, etc. However, once this cross-chain liquidity is created it must be stored and directed into the appropriate investment mechanisms to be put to proper use and to create an ease-of-use for the inexperienced DeFi user. This is where the Rainbow Network comes in. Built on Glitter, Rainbow has the advantage of being highly interoperable from the very onset of its existence. Moreover, Rainbow allows Glitter to have a home base for its cross-chain liquidity, and optimizes the implementation of this liquidity. For our partner protocols, Rainbow creates instant interoperability with all supported blockchains upon the launch of a partner protocol on Rainbow. Taken together, Glitter and Rainbow form a comprehensive ecosystem which creates a highly-liquid and optimized, cross-chain ecosystem. For more information on Rainbow please see: [docs.rainbownetwork.io](http://docs.rainbownetwork.io) As well as these links: * Website: * Discord: * Telegram: * Twitter: [@RBWNetwork ](https://twitter.com/RBWNetwork) * LinkedIn: * Github: * Youtube: * Medium: