-
Notifications
You must be signed in to change notification settings - Fork 45
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
feat: Configure Fast Withdrawals using Safe #177
Open
InoMurko
wants to merge
6
commits into
OffchainLabs:main
Choose a base branch
from
ConstellationCrypto:inomurko/multisig-fw-public
base: main
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
feat: Configure Fast Withdrawals using Safe #177
InoMurko
wants to merge
6
commits into
OffchainLabs:main
from
ConstellationCrypto:inomurko/multisig-fw-public
Conversation
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
InoMurko
changed the title
Configure Fast Withdrawals using Safe
feat: Configure Fast Withdrawals using Safe
Sep 3, 2024
InoMurko
force-pushed
the
inomurko/multisig-fw-public
branch
from
September 3, 2024 10:58
94615df
to
4cd0a06
Compare
TucksonDev
requested changes
Oct 1, 2024
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.
Thanks @InoMurko !
I've left some initial comments about the general structure, let me know what you think 🙏
InoMurko
force-pushed
the
inomurko/multisig-fw-public
branch
from
October 29, 2024 22:41
0b27950
to
9821184
Compare
spsjvc
reviewed
Oct 31, 2024
InoMurko
force-pushed
the
inomurko/multisig-fw-public
branch
from
October 31, 2024 11:28
5234764
to
ef76209
Compare
Co-authored-by: spsjvc <[email protected]>
Co-authored-by: spsjvc <[email protected]>
InoMurko
force-pushed
the
inomurko/multisig-fw-public
branch
from
November 6, 2024 13:57
ef76209
to
ebbf155
Compare
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.
Rollups tend to have ownership transferred to a Safe multi-signature account. These 4 scripts propose transactions to the Safe if there's at least one EOA account in the Safe ownership.
I had to change two types in
src/createSafePrepareTransactionRequest.ts
andsrc/setAnyTrustFastConfirmerPrepareTransactionRequest.ts
because they were too restrictive on the type of the account passed in.The first one is
creating the Safe
transaction. The owner here is the Safe that owns the Rollup. Hence there's no Private Key. The second one is setting thenew safe
as the Fast Confirmer, this is also sent from the Rollup Safe.