> For the complete documentation index, see [llms.txt](https://info.zehnafzar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://info.zehnafzar.com/bridge.md).
# Bridge
Bestarz Cross Chain Bridge
**Bestarz** cross chain bridge has something to do with enabling some sort of transfers between **binance smart chain** and **ethereum** blockchains.
How Does **Bestarz** Cross-Chain Bridge Functions Work:
To ensure that you get a clear understanding of how a **Bestarz** cross-chain bridge works, we’ll use the image below.
The icons of a paper with a pencil represent smart contracts. Furthermore, we have four smart contracts, two with a stack of coins (the cylinders with horizontal lines) and two with a bridge.
We have the “main chain” as Binance Smart Chain (if you have an existing token, you already have that).
For instance, when users want to transfer tokens from the main chain over to the side chain, they are first locked using the bridge contract on the main chain. We have a bridge contract on each side to ensure that the token transfer is done safely and sends a signal to the relay which then triggers the gateway to mint the locked amount of tokens on the side chain using the stylike child token contract.
When the transfer goes from the side chain back to the main chain, the process happens in reverse. This means that the tokens on the side chain (using a side chain bridge contract) are burned, and the ones on the main chain are unlocked simultaneously.
**Cross chain bridge : Stylike Governance Token :**
#### Binance smart chain Contracts
**Stylike Governance Token :**
some information about fees
info about sync prices in two chain
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://info.zehnafzar.com/bridge.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.