use filbeam contract in terminator n correct env names #604
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
DarkLord017
requested review from
bajtos,
juliangruber and
pyropy
as code owners
pyropy
requested changes
Feb 10, 2026
Contributor
pyropy
left a comment
pyropy
left a comment
There was a problem hiding this comment.
Great work! Let's just rename the FILBEAM_CONTROLLER_PRIVATE_KEY to FILBEAM_OPERATOR_CONTROLLER_PRIVATE_KEY since the contract name is FilBeamOperator.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
fixes #362
i just found contract calls in terminate directory are subgraphs and events also supposed to be proxied ?
Also i did not push worker configuration , was that supposed to be pushed ?
pls review @pyropy