Add upgradable event trigger registry #6
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These are useful for manual testing.
blockchainluffy
approved these changes
Sep 8, 2025
The new version allows explicitly specifying both contract paths and names instead of inferring one from the other. This was necessary because the event trigger registry has a slightly different path due to the version suffix. Also, we now pass the contract bytecode to abigen.
jannikluhn
force-pushed
the
event-trigger-registry
branch
from
20b96d6 to
8b0051b
Compare
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The registry is intentionally basic. It allows only the owner to register triggers, but without any restrictions. The contract is upgradable so that we can open it up, add restrictions (such as for TTL or contract addresses), and add additional features such as pricing.
There are additional helper contracts and scripts that facilitate testing beyond foundry's tests (such as manual end-to-end tests and rolling shutter's automated tests).