L1 blueprints will be executable on L2 too
Within the TractorFacet, users can provide a blueprint and sign it, which basically allows any user to execute the said actions in the blueprint (only once).
However, since the chainId
is not part of the signature, any Blueprint
that is executed on L1, will also be executable on the L2 Beanstalk decides to migrate to.
As the terms might then be unfavorable for the blueprint signer, this could allow for malicious executions
Unexpected results, loss of funds
Manual review
Add chain id to the signature
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.