Skip to content

chore: fix some typos #126

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.

Sign up for GitHub

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

Open
Fibonacci747 wants to merge 3 commits into
base: integration
Choose a base branch
from
Open

chore: fix some typos #126

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
36b0097
Update DeployAndInitEspressoSequencerInboxForTest.s.sol
Fibonacci747 Sep 12, 2025
99a9c43
Update README.md
Fibonacci747 Sep 12, 2025
74efa0b
Update test-node.bash
Fibonacci747 Sep 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion espresso-tests/DeployAndInitEspressoSequencerInboxForTest.s.sol
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ contract DeployAndInitEspressoSequencerInbox is Script {
uint256 maxDataSize = vm.envUint("MAX_DATA_SIZE");
// Grab booleans we need from env
bool isUsingFeeToken = vm.envBool("IS_USING_FEE_TOKEN");
// Trick the Vm into seeing that this opcode exsists if this isn't the migration test
// Trick the Vm into seeing that this opcode exists if this isn't the migration test
if (!isMigrationTest){
bytes memory code = vm.getDeployedCode("ArbSysMock.sol:ArbSysMock");
vm.etch(0x0000000000000000000000000000000000000064, code);
Expand Down
4 changes: 2 additions & 2 deletions espresso-tests/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Espresso Migration

This document contains details surrounding the test migrating an exsisting Arbitrum Orbit chain to use the nitro-espresso-integration, and be compatible with the Espresso network.
This document contains details surrounding the test migrating an existing Arbitrum Orbit chain to use the nitro-espresso-integration, and be compatible with the Espresso network.

## Running the test

Expand All @@ -25,4 +25,4 @@ These steps can be done manually while preparing the `** Essential migration ste

## Non upgrade related steps

Steps that are not directly related to a real world example of this upgrade will be unmarked. That is comments about these steps will contain neither `** Essential migration step **` or `* Essential migration sub step *`
Steps that are not directly related to a real world example of this upgrade will be unmarked. That is comments about these steps will contain neither `** Essential migration step **` or `* Essential migration sub step *`
2 changes: 1 addition & 1 deletion test-node.bash
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ DEFAULT_TOKEN_BRIDGE_VERSION="v1.2.2"
ESPRESSO_DEFAULT_VERSION=ghcr.io/espressosystems/nitro-espresso-integration/nitro-node:integration
: ${ESPRESSO_VERSION:=$ESPRESSO_DEFAULT_VERSION}

# Set default versions if not overriden by provided env vars
# Set default versions if not overridden by provided env vars
: ${NITRO_CONTRACTS_REPO:=$DEFAULT_NITRO_CONTRACTS_REPO}
: ${NITRO_CONTRACTS_BRANCH:=$DEFAULT_NITRO_CONTRACTS_VERSION}
: ${TOKEN_BRIDGE_BRANCH:=$DEFAULT_TOKEN_BRIDGE_VERSION}
Expand Down