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
To install zksync foundry on your machine run: ./install-foundry-zksync on this repo. Please note, this will override your existing forge setup. It is possible to use zksync foundry for non-zksync stuff without much issues, by just not using the --zksync flag
general build command for zkSync: FOUNDRY_PROFILE=zksync forge test --zksync
general test command for zkSync: FOUNDRY_PROFILE=zksync forge build --zksync
zksync/*: should contain all the contracts specific to zksync.
Guide for aave proposals on zkSync:
generating proposals for zkSync can be done using the generator without any extra specific changes.
zkSync specific payloads, tests and payload deployment and registering scripts reside in zksync/src/* directory.
scripts for creating proposal and writeups (.md file), independent if it has zkSync payloads or not reside in the src/* directory and not in zksync/*.
before a proposal is created, make sure FOUNDRY_PROFILE=zksync forge build --zksync is run before, as the proposal creation script relies on the bytecodeHash generated by the zkSync compiler to predict the create2 address of the payload.
The text was updated successfully, but these errors were encountered:
General guide:
./install-foundry-zksync
on this repo.Please note, this will override your existing
forge
setup. It is possible to use zksync foundry for non-zksync stuff without much issues, by just not using the--zksync
flagFOUNDRY_PROFILE=zksync forge test --zksync
FOUNDRY_PROFILE=zksync forge build --zksync
zksync/*
: should contain all the contracts specific to zksync.Guide for aave proposals on zkSync:
zksync/src/*
directory..md
file), independent if it has zkSync payloads or not reside in thesrc/*
directory and not inzksync/*
.FOUNDRY_PROFILE=zksync forge build --zksync
is run before, as the proposal creation script relies on thebytecodeHash
generated by the zkSync compiler to predict the create2 address of the payload.The text was updated successfully, but these errors were encountered: