# 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.

<figure><img src="/files/Dqqsp1yBq7ehao47fUGY" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.glitterfinance.org/glitter-crosschain-platform/bridge-core-mvp/bridge-core-mvp/core-concept.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.