Skip to content
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

Merge release into master #101

Merged
merged 9 commits into from
Dec 6, 2024
Merged

Merge release into master #101

merged 9 commits into from
Dec 6, 2024

Conversation

PlasmaPower
Copy link
Collaborator

These commits were all reviewed and merged in separate PRs, aside from a small merge conflict fixed in the last merge commit. I'm pretty sure these PRs were intended to target master instead of release.

Tristan-Wilson and others added 9 commits September 4, 2024 11:22
test-node.bash can now be run with --l2-anytrust which runs the l2
nodes in AnyTrust mode. It creates a committee of 2 daserver with
assumed-honest set to 1, requiring successful stores of the batch data
to both of them. Nitro nodes sync from a mirror daserver. All dasevers
use local file storage for the batch data on their own volumes.

BLS keys for the committee are automatically generated and the keyset is
activated automatically on the SequencerInbox contract.
Adjacent line changes on arbitrum DataAvailabilityCommittee and
InitialArbOSVersion, no actual conflict.
Add --l2-anytrust option to run in AnyTrust mode
@cla-bot cla-bot bot added the s label Dec 6, 2024
@PlasmaPower PlasmaPower merged commit 5986e62 into release Dec 6, 2024
27 checks passed
@PlasmaPower PlasmaPower deleted the merge-release-into-master branch December 6, 2024 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants