You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenZeppelin's hardhat-upgrade supports temporary caching for development networks by creating manifest files in the tmp directory. The same behavior is expected for zkSync dev networks (such as the Era Test Node and local setups). Each cache file is created within the instanceId returned from the RPC hardhat_metadata. However, this functionality is currently missing in zkSync dev networks, which is blocking the feature.
🤔 Rationale
To be alligned with OpenZeppelin's hardhat-upgrade plugin.
🖼️ Mockups/Examples
If applicable, provide mockups or examples of how the feature would work.
📋 Additional Context
Add any other context or information about the feature request here.
The text was updated successfully, but these errors were encountered:
🌟 Feature Request for hardaht-zksync plugins
💥 Plugin name
hardhat-zksync-upgradable
📝 Description
OpenZeppelin's hardhat-upgrade supports temporary caching for development networks by creating manifest files in the tmp directory. The same behavior is expected for zkSync dev networks (such as the Era Test Node and local setups). Each cache file is created within the instanceId returned from the RPC hardhat_metadata. However, this functionality is currently missing in zkSync dev networks, which is blocking the feature.
🤔 Rationale
To be alligned with OpenZeppelin's hardhat-upgrade plugin.
🖼️ Mockups/Examples
If applicable, provide mockups or examples of how the feature would work.
📋 Additional Context
Add any other context or information about the feature request here.
The text was updated successfully, but these errors were encountered: