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
Copy file name to clipboardExpand all lines: README.md
+71Lines changed: 71 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,6 +100,7 @@ The `AaveStewardsInjector` contract also introduces an `EXPIRATION_PERIOD` to di
100
100
101
101
```sh
102
102
cp .env.example .env
103
+
yarn
103
104
forge install
104
105
```
105
106
@@ -113,6 +114,76 @@ forge test
113
114
114
115
<br>
115
116
117
+
## Instructions and FAQ's
118
+
119
+
### How to I use the generator tooling to bootstrap the update?
120
+
121
+
Run `yarn generate` on your terminal in order to start the generator. The generator is a CLI tool which will generate the required helper contract which can be then run to submit updates to the risk steward. The generator will generate the helper contract in the `src/contracts/updates` directory.
122
+
123
+
To get a full list of available commands run `yarn generate --help`
124
+
125
+
```sh
126
+
yarn generate --help
127
+
yarn run v1.22.19
128
+
$ tsx generator/cli --help
129
+
Usage: proposal-generator [options]
130
+
131
+
CLI to generate aave proposals
132
+
133
+
Options:
134
+
-V, --version output the version number
135
+
-f, --force force creation (might overwrite existing files)
The generator generates the scripts for doing the updates in `src/contracts/updates` directory.
174
+
175
+
The script can be executed by running: `make run-script network=mainnet contract_path=src/contracts/examples/EthereumExample.sol:EthereumExample broadcast=false` where the bool inside the `broadcast=` determines if the calldata should be sent to safe. The script also emits the calldata for doing the update in the console which can be used on the safe manually as well.
176
+
177
+
### Before I will submit anything to sign, how do I test out the update, or get visibility from what will happen?
178
+
179
+
Running the script generated on the contracts in `src/contracts/updates` directory with `broadcast=false`, there will files written into the diffs directory, which will show the params changed for the asset by the update, with before and after values which can be validated with what update is expected.
180
+
181
+
### Once I have full assurance it looks correct, how do I submit to Safe?
182
+
183
+
Once the script on the comments of the generated contract has been run with `broadcast=false`, there will be calldata emitted on the console with the contract to call. Please copy the calldata and the contract to execute it on (i.e RiskSteward) from the console and input it on the [gnosis safe UI](https://app.safe.global/) transaction builder.
184
+
185
+
If you wish to not use the UI and send the update directly please put `broadcast=true` when running the script to directly broadcast the tx using the gnosis safe.
0 commit comments