# Deployment

This section outlines how Inception smart contracts are deployed across supported networks. The project uses Hardhat as the deployment framework and follows a structured, repeatable process for proxy-based contract deployment.

## Structure

* `hardhat.config.ts`: Main configuration file for network definitions and compiler settings.
* `.env_example`: Used to define sensitive deployment variables like private keys and RPC URLs.
* `.openzeppelin/`: Stores deployment metadata and proxy admin state (for upgradeable contracts).
* `scripts/`, `deploy/`, `deployment/`: Contain deployment logic and contract initialization scripts.

## Key Notes

* Contracts are deployed using OpenZeppelin’s upgradeable proxy pattern.
* Separate JSON config files define deployed addresses for each chain.
* Deployment automation is handled by Hardhat scripts tailored per module.
* Token address resolution and vault creation parameters are managed via environment configs and script inputs.

> This process is primarily intended for internal or development use. External contributors should consult specific module documentation or request access to network-specific deployment instructions if required.