The Forge Proposal Simulator (FPS) offers a framework for creating secure governance proposals and deployment scripts, enhancing safety, and ensuring protocol health throughout the proposal lifecycle. The major benefits of using this tool are standardization of proposals, safe calldata generation, and preventing deployment parameterization and governance action bugs.
For guidance on how to use the library please check FPS documentation
Add forge-proposal-simulator
to your project using Forge:
forge install https://github.com/OlympusDAO/forge-proposal-simulator.git
Update your remappings.txt to include:
@forge-proposal-simulator=lib/forge-proposal-simulator/
Create a JSON file following the standard on
Addresses. We recommend keeping the
addresses file in a separate folder, for example ./addresses/addresses.json
.
Once the file is created, be sure to allow read access to addresses.json
inside of foundry.toml
.
[profile.default]
...
fs_permissions = [{ access = "read", path = "./addresses/addresses.json"}]
Create a proposal. Choose a model that fits your needs:
Create scripts and/or tests. Check Guides and Integration Tests.
There are many ways you can participate and help build high quality software. Check out the contribution guide!
Forge Proposal Simulator is made available under the MIT License, which disclaims all warranties in relation to the project and which limits the liability of those that contribute and maintain the project. As set out further in the Terms, you acknowledge that you are solely responsible for any use of Forge Proposal Simulator contracts and you assume all risks associated with any such use. The authors make no warranties about the safety, suitability, reliability, timeliness, and accuracy of the software.
Further license details can be found in LICENSE.