docs(base-contracts): OptimismMintableERC20Factory mainnet address inconsistency and incorrect footnote
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- documentation
Research direction
Open docs/base-chain/network-information/base-contracts.mdx and compare the L2 table with the OP Stack predeploy specification linked in the issue. Resolve whether the mainnet entry is outdated or a legacy/wrapper contract, then update the address and the footnote so they agree. Confirm the table clearly reflects the chosen explanation.
Written by the indexing model from the issue text.
Description
Problem
File: docs/base-chain/network-information/base-contracts.mdx
The L2 contract address table lists different addresses for OptimismMintableERC20Factory on mainnet vs testnet:
- Mainnet:
0xF10122D428B4bc8A9d050D06a2037259b4c4B83B - Testnet:
0x4200000000000000000000000000000000000012
According to the OP Stack specification, the canonical predeploy address for OptimismMintableERC20Factory is 0x4200000000000000000000000000000000000012 on all OP Stack chains (both mainnet and testnet).
Additional issue
The footnote at the bottom of the L2 table states:
L2 contract addresses are the same on both mainnet and testnet.
This is contradicted by the table itself, since the two OptimismMintableERC20Factory addresses differ.
Expected behavior
Either:
- Update the mainnet
OptimismMintableERC20Factoryaddress to0x4200000000000000000000000000000000000012if the current entry is outdated, OR - Add a clarifying note explaining that the mainnet entry is a legacy/wrapper contract, and update the footnote to reflect the exception.
References
- OP Stack predeploys: https://specs.optimism.io/protocol/predeploys.html
- Dominant language
- JavaScript
- Stars
- 337
- Forks
- 798
- Avg merge
- 7h 24m
- Merged PRs (30d)
- 51
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from base/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·
-
client-controller-update ta-bot-triage team-money-movement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MetaMask/metamask-mobile#36594 ·