Skip to content

Conversation

@einat-starkware
Copy link
Contributor

No description provided.

@github-actions
Copy link

github-actions bot commented Jul 2, 2025

@reviewable-StarkWare
Copy link

This change is Reviewable

Copy link
Contributor Author

einat-starkware commented Jul 2, 2025

@einat-starkware einat-starkware marked this pull request as ready for review July 3, 2025 06:58
@einat-starkware einat-starkware force-pushed the einat/chain_info_l3_compatibility branch from 9ce0f2f to 5d86548 Compare July 3, 2025 12:04
@einat-starkware einat-starkware force-pushed the einat/chain_info_l3_compatibility branch from 5d86548 to 56b7167 Compare July 3, 2025 12:47
Copy link
Collaborator

@Yoni-Starkware Yoni-Starkware left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed all commit messages.
Reviewable status: 0 of 7 files reviewed, 2 unresolved discussions


config/sequencer/default_config.json line 126 at r1 (raw file):

    "privacy": "Public",
    "value": false
  },

This should not be a config. The value should always be false.

Code quote:

  "batcher_config.block_builder_config.chain_info.is_layer_3": {
    "description": "Whether the chain is a layer 3 chain.",
    "privacy": "Public",
    "value": false
  },

crates/blockifier/src/context.rs line 203 at r1 (raw file):

    pub chain_id: ChainId,
    pub fee_token_addresses: FeeTokenAddresses,
    pub is_layer_3: bool,

Suggestion:

    pub is_L3: bool,

@einat-starkware einat-starkware force-pushed the einat/chain_info_l3_compatibility branch 2 times, most recently from cdacf97 to 2c4e54d Compare July 6, 2025 10:43
Copy link
Contributor Author

@einat-starkware einat-starkware left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 0 of 7 files reviewed, 2 unresolved discussions (waiting on @Yoni-Starkware)


config/sequencer/default_config.json line 126 at r1 (raw file):

Previously, Yoni-Starkware (Yoni) wrote…

This should not be a config. The value should always be false.

Done.


crates/blockifier/src/context.rs line 203 at r1 (raw file):

    pub chain_id: ChainId,
    pub fee_token_addresses: FeeTokenAddresses,
    pub is_layer_3: bool,

changed to is_l3 to be consistent with snake case formatting

Copy link
Collaborator

@Yoni-Starkware Yoni-Starkware left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewed 7 of 7 files at r2, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @einat-starkware)

@einat-starkware einat-starkware force-pushed the einat/chain_info_l3_compatibility branch from 2c4e54d to 9d4edbf Compare July 8, 2025 14:04
Copy link
Contributor Author

@einat-starkware einat-starkware left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed all commit messages.
Reviewable status: 3 of 7 files reviewed, all discussions resolved (waiting on @Yoni-Starkware)

Copy link
Contributor Author

@einat-starkware einat-starkware left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 3 of 7 files at r2, 4 of 4 files at r3.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @einat-starkware)

@einat-starkware einat-starkware added this pull request to the merge queue Jul 9, 2025
Merged via the queue into main with commit 7bc2f18 Jul 9, 2025
18 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Jul 10, 2025
@einat-starkware einat-starkware deleted the einat/chain_info_l3_compatibility branch July 15, 2025 08:46
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants