From multi to uni

[aelmanaa]

---

Below is a summarization created by an LLM (gpt-4-turbo-2024-04-09). Be mindful of hallucinations and verify accuracy.

Why

The changes in this pull request are designed to enhance the reliability and efficiency of the deployment process for cross-chain token transfers. By adopting a split deployment architecture, we address the challenges associated with multi-RPC dependencies and streamline the deployment and configuration processes across different blockchain networks. This approach not only reduces potential points of failure but also improves the manageability and scalability of deployments.

What

This pull request introduces a new deployment and configuration strategy for handling token transfers across multiple blockchain networks, specifically targeting improvements in reliability, error recovery, and operational efficiency.

• Deployment and Configuration Changes

  • Replaced the monolithic deployment script with network-specific deployment scripts.
  • Introduced separate configuration scripts for each network to set up cross-chain relationships.
  • Added network-specific JSON files for storing contract addresses, enhancing manageability and reducing error risks.

• New Scripts and Functionalities

  • Deployment Scripts:
    • DeploySepolia.s.sol, DeployArbitrumSepolia.s.sol, DeployFuji.s.sol for deploying contracts on respective networks.
  • Configuration Scripts:
    • ConfigureSepolia.s.sol, ConfigureArbitrumSepolia.s.sol, ConfigureFuji.s.sol for setting up cross-chain configurations post-deployment.

• Contract and Configuration Management

  • Implemented BaseDeployment.s.sol and BaseConfiguration.s.sol as base classes to handle common functionalities and streamline the deployment and configuration processes.

• Testing and Validation

  • Updated test scripts BurnAndMint.s.sol, LockAndMint.s.sol, and BurnAndRelease.s.sol to use network-specific address files, ensuring they operate with the correct contract instances post-deployment.

• File System Changes

  • Modified foundry.toml to adjust file system permissions for the new network-specific JSON address files.

• Documentation and Logging

  • Updated README.md to reflect the new deployment process, benefits, and step-by-step instructions for deploying and testing the contracts.

These changes collectively aim to make the deployment process more robust, easier to manage, and scalable across multiple networks, thereby enhancing the overall reliability and efficiency of cross-chain token transfers.