IronVestAdminRequried this is the same contract as our audited iron…

[SibghatUllah1997]

• In these contracts emergencyWithdrawal can withdraw any tokens regardless of condition

• IronVestAdminRequried: This is the same contract as our audited ironvest, but the difference is that we are now going to deploy the contract using the factory pattern. In the previous implementation, the deployer was the default admin, but here we have to take it as a parameter. This contract file and name are separated from the audited one.

• There is a contract with the name of IronVestDeployer. By using this contract, we can deploy IronVestAdminRequried and our extended version of the contract.

• There is a contract named IronVestExtended.sol (in a separate directory), which is supposed to have the functionality of updating the beneficiary address. This contract is inheriting another contract named IronVestPreCheck.sol. This contract is a read-only contract, and we only need to deploy it once. We can use it as many times as we want. This contract is supposed to check some preconditions for executing a function.

• Lastly, for IronVestExtended.sol deployment, we need to activate optimization of 200 points.
  ```ct with the name of IronVestPreCheck.sol this contract is read only contract we just need to deploy this contract once and we can use it as many time as we want this contract supposed to check some preCondition for executing a function

• Laslty for IronVestExtended.sol deployment we need to active optimization of 200 points