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.

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

docs: change title number #1653

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
+4 −4
Open

docs: change title number #1653

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
92354e2
change title number
woctocat Sep 9, 2024
7e61fb6
Merge branch 'master' into patch-1
woctocat Sep 12, 2024
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
8 changes: 4 additions & 4 deletions ...idging/bridge-tokens-programmatically/03-how-to-bridge-tokens-generic-custom.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Familiarity with [Arbitrum’s token bridge system](/build-decentralized-apps/to

We will go through all steps involved in the process. However, if you want to jump straight to the code, we have created [this script in our tutorials repository](https://github.com/OffchainLabs/arbitrum-tutorials/tree/master/packages/custom-token-bridging) that encapsulates the entire process.

## Step 0: Review the prerequisites
## Step 1: Review the prerequisites

As stated in the [token bridge conceptual page](/build-decentralized-apps/token-bridging/03-token-bridge-erc20.md#the-arbitrum-generic-custom-gateway), there are a few prerequisites to keep in mind while using this method to make a token bridgeable.

Expand All @@ -40,7 +40,7 @@ import TokenCompatibilityPartial from '../partials/_token-compatibility.md';

<TokenCompatibilityPartial />

## Step 1: Create a token and deploy it on L1
## Step 2: Create a token and deploy it on L1

We‘ll begin the process by creating and deploying on L1 a sample token to bridge. If you already have a token contract on L1, you don’t need to perform this step.

Expand Down Expand Up @@ -209,7 +209,7 @@ main()
});
```

## Step 2: Create a token and deploy it on L2
## Step 3: Create a token and deploy it on L2

We’ll now create and deploy on L2 the counterpart of the token we created on L1.

Expand Down Expand Up @@ -298,7 +298,7 @@ main()
});
```

## Step 3: Register the custom token to the generic-custom gateway
## Step 4: Register the custom token to the generic-custom gateway

Once both our contracts are deployed in their respective chains, it’s time to register the token in the generic-custom gateway.

Expand Down