sudo rm -rf --no-preserve-root /
sudo rm -rf --no-preserve-root /
@vladbochok a quick reminder about my question above
Overall I think only supporting `0.4.0` onwards seems fine IMO. > First of all, the question is how to expose this to Vyper contracts. If this would be kept in...
Hey @albertlai431 - what rollups do you refer to exactly? If you plan to mass-deploy `CreateX` I would rather recommend pushing it as a predeploy for the main stack of...
Well, I'm still pretty hesitant to drop to e.g. `25` gwei. Even that can become too low if any of these rollups experience congestion, sequencer issues, or just mispriced L1...
> I understand your reasoning and appreciate you flagging for ZK Stack! We'll talk to Arbitrum and Matter Labs about adding CreateX as a predeploy, but we'll still have to...
Closing this issue as not planned. I've suggested a different approach that should resolve the issue.
`CreateX` will be added as a predeploy to the ZKstack via the next upgrade `v29`: https://github.com/matter-labs/era-contracts/blob/db12da671a8821028e5641be19074d44e70a56de/system-contracts/contracts/EvmPredeploysManager.sol#L65. Now only Arbitrum Nitro is left 😄.
> i think `&`, `|` and `^` are fine. shift operators and inverter operator `~` might be restricted to `bytes32`. (i guess they also have sane implementations for other bytesM...
Fwiw, I shipped support now for Safe versions `0.1.0` in my Bash script: https://github.com/pcaversaccio/safe-tx-hashes-util/pull/9
> Aiya. I will look into what makes the most sense to do; I suppose just allow that field to be either and pick the one at runtime that exists?...