[feature] deployed contract address management

[kaihiroi]

Problem

Currently, deployed contract addresses are stored in environment (.env) files. This approach lacks flexibility and scalability, making it difficult to manage and retrieve contract addresses across different chain IDs efficiently.

Solution

Implement a feature that saves deployed contract addresses in a JSON file, categorized by their respective chainId. This structure enhances flexibility and scalability, allowing for easier management and access of contract addresses for each blockchain network without relying heavily on external files.

Alternatives

• Centralized Database: Use a database to store contract addresses, providing more flexibility and scalability.
• Environment Variables: Continue using environment variables, which can become unmanageable as the number of chain IDs increases.
• Hardcoded Addresses: Embed addresses directly in the Solidity code, leading to maintenance difficulties and reduced flexibility. Additionally, Solidity itself cannot modify .sol files.

Additional context

Storing contract addresses in a JSON format categorized by chainId improves maintainability and scalability, especially when dealing with multiple blockchain networks. This approach minimizes dependency on external files and simplifies the deployment and interaction processes with deployed contracts.