-
```
owocki@local /Users/owocki/Sites/allo-v2~ % npm install
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @matterlabs/hardhat-zksync-deploy@0.1…
-
### 🐛 Bug Report
#### 📝 Description: Command failed to run: forge script deploy-scripts/DeployL2Contracts.sol --legacy --ffi --rpc-url=https://eth-holesky.g.alchemy.com/v2/gX4Bzzy0OfPTnC-SoNcdCAeXg…
-
### 🐛 Bug Report
#### 📝 Description
`web3_clientVersion` is expected to return the current client version of zkSync external node.
The value is currently hardcoded as `zkSync/v2.0` at https://g…
-
**User Story:**
This ticket has 2 goals :
#### Disabling zksync checkout during merge
**For Product @lthrift**
Currently, we have a toggle switch that would have to be set to true and the zky…
-
### 🐛 Bug Report for zkSync Era In-Memory Node
#### 📝 Description
The string returned by the `web3_clientVersion` RPC method (`zkSync/2.0`) is not compatible with [a check made by the `hardhat-n…
-
### 🌟 Feature Request for hardaht-zksync plugins
#### 💥 Plugin name
[Solidity Coverage](https://www.npmjs.com/package/solidity-coverage)
#### 📝 Description
It would be helpful to have native…
-
### 🐛 Bug Report for zkSync CLI
#### 📝 Description
I'm not at all sure if it's actually a bug. I'm probably doing something wrong but still
I'm getting this error when trying to init a project:…
-
Kalogerone
high
# CREATE opcode works differently in the zkSync chain
## Summary
`zkSync Era` chain has differences in the usage of the `create` opcode compared to the EVM.
## Vulnerability Detai…
-
**Describe the bug**
Initial deployment works fine and contracts are saved, Reruning deployments on zksync throws an error
**To Reproduce**
Steps to reproduce the behavior:
1. Rerun deployment scr…
-
pengun
high
# CREATE3 is not available in the zkSync Era.
In the current code using CREATE3 with CREATE2, but in zkSync Era, CREATE2 for arbitrary bytecode is not available, so a revert occurs in th…