mirror of
https://github.com/datahaven-xyz/datahaven
synced 2026-05-24 09:50:01 +00:00
## Summary This PR introduces support for deploying Datahaven contracts to different chains (hoodi, holesky, mainnet), as well as a new cli command to manage this deployment separately from the regular deployment, while maintaining compatibility with it. #### New CLI command - **`bun cli contracts deploy`** - Deploy contracts to supported chains (Hoodi, Holesky, Mainnet) - **`bun cli contracts status`** - Check deployment configuration and status - **`bun cli contracts verify`** - Verify contracts on block explorers - Commands need the chain parameter: `--chain <hoodi | holesky | mainnet>` - Right now only `hoodi` and `holesky` are supported ### Deployment #### Hoodi & Holesky Network Support - Added **DeployBase.s.sol** as common ground for **DeployTestnet.s.sol** (also new) and **DeployLocal.s.sol** (existing). - **Hoodi configuration** (`contracts/config/hoodi.json`) with deployed EigenLayer contract addresses to reference. - **Holesky configuration** (`contracts/config/hoodi.json`) with deployed EigenLayer contract addresses to reference. #### Contracts being deployed - **DataHaven**: ServiceManager, VetoableSlasher, RewardsRegistry - **Snowbridge**: BeefyClient, AgentExecutor, Gateway, RewardsAgent - **EigenLayer**: References existing deployed contracts (not re-deployed) #### Deployment files When the deployment is done, a new file under `contracts/deployments` is generated with the addresses of the deployed contracts, for each chain (it will be overriden per chain if run multiple times). So we would have one `anvil.json`, `hoodi.json`, `holesky.json`, etc, with the addresses of the deployed contracts for reference and for later verification. #### Todo - [x] Test compatibility with existing `bun cli launch` and `bun cli deploy` commands #### For follow-up PRs - Fix verification issue with `foundry verify-contracts` when specifying the `chain` or `chain-id` parameter, needed for hoodi (https://github.com/foundry-rs/foundry/issues/7466). - Add `redeploy` feature to only override implementation contract and leave the proxy address untouched ## Usage Examples ```bash # Deploy to Hoodi network bun cli contracts deploy --chain hoodi # Check deployment status bun cli contracts status --chain hoodi # Verify contracts on block explorer bun cli contracts verify --chain hoodi ``` <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added deployment and configuration support for new networks "hoodi" and "holesky", including new configuration and deployment files. * Introduced a CLI tool for managing contract deployments, status checks, and verification across supported chains. * Added example environment configuration and comprehensive deployment documentation. * Enabled contract verification and status reporting via the CLI with support for block explorer integration. * **Improvements** * Refactored deployment scripts for modularity, supporting both local and testnet environments. * Centralized and extended configuration loading to support additional contract addresses and network parameters. * Enhanced deployment utilities and typings to support multi-network deployments. * **Bug Fixes** * Improved input validation and error handling in CLI commands and deployment scripts. * Added explicit handling for zero address in operator strategy retrieval. * **Chores** * Updated documentation and configuration templates for easier onboarding and deployment management. * Improved logging and output formatting for deployment and verification processes. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Steve Degosserie <723552+stiiifff@users.noreply.github.com> Co-authored-by: Ahmad Kaouk <56095276+ahmadkaouk@users.noreply.github.com>
50 lines
1.6 KiB
TypeScript
50 lines
1.6 KiB
TypeScript
import {
|
|
buildContracts,
|
|
constructDeployCommand,
|
|
executeDeployment,
|
|
validateDeploymentParams
|
|
} from "scripts/deploy-contracts";
|
|
import { logger, printDivider, printHeader } from "utils";
|
|
import type { ParameterCollection } from "utils/parameters";
|
|
|
|
interface DeployContractsOptions {
|
|
chain?: string;
|
|
rpcUrl: string;
|
|
privateKey?: string | undefined;
|
|
verified?: boolean;
|
|
blockscoutBackendUrl?: string;
|
|
parameterCollection?: ParameterCollection;
|
|
skipContracts: boolean;
|
|
}
|
|
|
|
/**
|
|
* Deploys smart contracts to the specified RPC URL
|
|
*
|
|
* @param options - Configuration options for deployment
|
|
* @param options.rpcUrl - The RPC URL to deploy to
|
|
* @param options.verified - Whether to verify contracts (requires blockscoutBackendUrl)
|
|
* @param options.blockscoutBackendUrl - URL for the Blockscout API (required if verified is true)
|
|
* @param options.parameterCollection - Collection of parameters to update in the DataHaven runtime
|
|
* @returns Promise resolving to true if contracts were deployed successfully, false if skipped
|
|
*/
|
|
export const deployContracts = async (options: DeployContractsOptions) => {
|
|
printHeader("Deploying Smart Contracts");
|
|
|
|
if (options.skipContracts) {
|
|
logger.info("🏳️ Skipping contract deployment");
|
|
printDivider();
|
|
return;
|
|
}
|
|
|
|
// Check if required parameters are provided
|
|
validateDeploymentParams(options);
|
|
|
|
// Build contracts
|
|
await buildContracts();
|
|
|
|
// Construct and execute deployment
|
|
const deployCommand = constructDeployCommand(options);
|
|
await executeDeployment(deployCommand, options.parameterCollection, options.chain);
|
|
|
|
printDivider();
|
|
};
|