-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support end-to-end flow with Bonsai in forge test and local deployment #29
Conversation
Remaining work is to update and test the local deployment script. If it is ready, I will also integrate the updated relay with the ability to plumb through SNARK proofs from the Bonsai proving service. |
Depends on additions to the Bonsai libraries in risc0/risc0#712 |
@capossele, I've now added a more complete deploy script and run the local deployment. The local environment example doesn't work yet because the Relay does not support the |
This reverts commit f35f995.
…victor/update-bonsai-libs
7928bd0
to
769d5ff
Compare
7f677d1
to
d446165
Compare
517e509
to
091b3da
Compare
Replaced by #45 |
This PR ports the modifications and improvements I worked on for the Governance showcase back to the
template. Included changes are:
forge test
, optional request a SNARK from the Bonsai proving service and provide it to authenticate the callback, using the real SNARK verifier implementation (BonsaiRelay
). This flow is enabled whenRISC0_DEV_MODE=false
is set and uses the full implementations of all components except the Bonsai Relay.cargo run --bin bonsai-ethereum-relay-cli -- run
, developers can launch the Bonsai relay. With this, they can either target a a local Ethereum node withanvil
or a public Ethereum network like Sepolia. This supports both local and testnet deployment of the developers's application.Additionally:
github.com/risc0/risc0
as a dependency and use the contained Bonsai libraries.Resolves #26
Resolves #27
Resolves #28