-
Notifications
You must be signed in to change notification settings - Fork 470
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
Update BoLD Submodule and Add Newly Supported Flags to BoLD Staker #2835
Open
rauljordan
wants to merge
12
commits into
master
Choose a base branch
from
update-bold-dec-16
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
3e59f8f
update bold submodule
rauljordan da609b6
include all the new config opts
rauljordan 177b7a8
comment
rauljordan ac58023
Merge branch 'master' into update-bold-dec-16
rauljordan ffdce5c
edits
rauljordan a833234
Merge branch 'update-bold-dec-16' of github.com:OffchainLabs/nitro in…
rauljordan 9128112
Merge branch 'master' into update-bold-dec-16
rauljordan 2e8b5b7
Merge branch 'master' into update-bold-dec-16
rauljordan ddedd78
Merge branch 'master' into update-bold-dec-16
rauljordan e3aaf05
update submod
rauljordan 848b1b5
Merge branch 'update-bold-dec-16' of github.com:OffchainLabs/nitro in…
rauljordan 0908ed4
Merge branch 'master' into update-bold-dec-16
tsahee File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Submodule bold
updated
14 files
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why isn't this code also for the assertion chain? Does the assertion chain not do auto allowance? Same thing for the delegated staking, maybe I'm just not sure what's the responsibility of the challenge manager vs assertion chain.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The challenge manager spins up something called an assertion manager, and it is the assertion manager that does the auto allowance approval, auto deposit, and delegated staking on startup. The
assertion chain
is an abstraction over the Go bindings to Solidity which also do auto-deposit each time it makes a move related to the stake token. Perhaps we should unify all those responsibilities under the assertion chain?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need for now, makes sense and LGTM aside from the presumably accidental testnode change