> For the complete documentation index, see [llms.txt](https://gasyard-1.gitbook.io/gasyard/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gasyard-1.gitbook.io/gasyard/overview/publish-your-docs.md).

# Bridge System

### Transaction Flow

Gasyard enables seamless cross-chain transactions through a streamlined process:

1. **Deposit Phase:**

* User initiates a bridge transaction and deposits assets.
* Gateway Contract locks the assets and generates a unique Order ID.

2. **Settlement Phase:**

* Settlement Layer fetches real-time bids from solvers.
* Optimal bid is selected, and transaction details are broadcast.

3. **Execution Phase:**

* Solver executes the transaction on the destination chain.
* Unlocks and delivers funds to the user.

#### Features:

* Average transaction time: \~8.9 seconds.
* Supports atomic operations for secure fund transfers.
* Refunds available for incomplete transactions after a timeout period.

***

### Supported Networks

Gasyard currently supports 12+ networks across EVM and non-EVM ecosystems.

* EVM Chains: Ethereum, Base, Optimism, Arbitrum, BNB Chain.
* Alt-VM Chains: Solana, Aptos, Sui, TON, Starknet.
* Future Integrations: Bitcoin, Celestia, Fuel.

***

### Asset Types

* Supported Assets:  \
  Native tokens (e.g., ETH, SOL).\
  Stablecoins (e.g., USDT, USDC).

* Upcoming Support:\
  Wrapped assets.

  Cross-chain NFTs.

***

### Fee Structure

* Platform Fee: Up to 0.25% per transaction.
* Solver Profit: Spread between input and output amounts.
* Refund Fee: 0%

***

### Bridge Security

* Multi-Signature Verification: Ensures transaction integrity.
* Emergency Controls: Pausable contracts in case of critical issues.
* Reentrancy Protection: Guards against repeated execution vulnerabilities.
* Strict Input Validation: Prevents malformed or fraudulent transactions.

***


---

# 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://gasyard-1.gitbook.io/gasyard/overview/publish-your-docs.md?ask=<question>&goal=<endgoal>
```

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