# Bridge

The bridge module supports multi-chain deployment and configuration of Inception smart contracts. It manages addresses, proxy deployments, and environment-specific parameters for interacting across networks like BSC and Arbitrum.

It does not define a protocol-specific bridging mechanism (i.e., token bridges or messaging layers), but instead organizes deployment metadata and configuration files needed to operate Inception’s infrastructure in a multi-chain environment.

## Components

#### 1. **Deployment Metadata (`.openzeppelin/`)**

* JSON files like `bsc.json`, `arbitrum-one.json` store proxy deployment states for OpenZeppelin upgradeable contracts.
* These files are required to maintain upgrade logic across environments.

#### 2. **Config Addresses (`config/addresses/`)**

* Directory structure by category:
  * `assets/`: Token address mappings per network
  * `bridges/`: Addresses of third-party bridges (if applicable)
  * `factory/`: Vault and adapter factory addresses
  * `rate_providers/`, `ratios/`: Oracle and pricing feed configurations
* Used during deployments and scripts for resolving environment-specific variables.

#### 3. **Audits (`audits/`)**

* Contains two security reports:
  * `InceptionBridge_Halborn.pdf`
  * `InceptionBridge_Veridise.pdf`
* These cover upgradeability, access control, and configuration risk.

#### 4. **Hardhat Scripts and Config**

* `hardhat.config.js`: Hardhat project base setup.
* Likely paired with `scripts/` folder to deploy or verify bridge-related contracts.

#### 5. **README.md**

* Project-level context and installation info.

## Notes

* There is no single `Bridge.sol` contract or dedicated on-chain bridge logic in this repo.
* The module is primarily responsible for managing multi-network infrastructure and deployment references.
* All deployments rely on OpenZeppelin's upgradeable proxy model.


---

# 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.inceptionlrt.com/developers/modules/bridge.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.