feat(hardhat): Sync Updated Contracts from Consensus Repository to Hardhat Node in Genlayer-Studio

[mpaya5]

Description

Recent changes have been pushed to the main branch of the contracts repository in the consensus project. These updates are not yet reflected in the Hardhat node used by the genlayer-studio project. This mismatch could lead to inconsistencies between the deployed contracts in the consensus system and the contracts used for development and testing in genlayer-studio.

Solution

1. Sync the updated contracts from the main branch of the consensus repository.
2. Deploy the updated contracts to the Hardhat node in the genlayer-studio project to ensure consistency.
3. Update any related configuration or deployment scripts in genlayer-studio if necessary.

Benefits

• Ensures consistency between the consensus repository and the genlayer-studio development environment.
• Prevents potential issues caused by discrepancies in contract versions.
• Maintains alignment for accurate development and testing.

Acceptance Criteria

• Fetch the latest changes from the main branch of the contracts repository in the consensus project.
• Redeploy the updated contracts to the Hardhat node in the genlayer-studio project.
• Verify that the deployed contracts in Hardhat match the versions in the consensus repository.
• Test the integration to ensure no breaking changes.

Additional Context

• Ensure that all changes are thoroughly tested to prevent any unforeseen issues in the genlayer-studio development environment.
• Communicate with the consensus team if there are any breaking changes or updates requiring clarification.

Technical Considerations

• Verify compatibility of the updated contracts with the existing deployment scripts and configurations in genlayer-studio.
• Ensure Hardhat scripts are updated if new contract methods or parameters are introduced.