Skip to content

docs: Fix incorrect contract address link for Base Sepolia #115

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

Closed
wants to merge 1 commit into from

Conversation

mdqst
Copy link

@mdqst mdqst commented Jan 21, 2025

I noticed a typo in the Base Sepolia section of the contracts table. The link for the Registry address was pointing to the Base Mainnet instead of Base Sepolia. I've corrected the link to ensure it points to the correct address on Base Sepolia.

Before:

| Registry | [0x1493b2567056c2181630115660963E13A8E32735](https://basescan.org/address/0xb94704422c2a1e396835a571837aa5ae53285a95) |

After:

| Registry | [0x1493b2567056c2181630115660963E13A8E32735](https://sepolia.basescan.org/address/0x1493b2567056c2181630115660963E13A8E32735) |

This ensures the documentation accurately reflects the correct network.

Fix incorrect contract address link for Base Sepolia Registry
@cb-heimdall
Copy link
Collaborator

cb-heimdall commented Jan 21, 2025

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

@mdqst
Copy link
Author

mdqst commented Jan 21, 2025

@brendan-defi @wbnns Hey! Could you please review my corrections?
I hope I was able to help in some way.

Based!

@stevieraykatz
Copy link
Collaborator

Dupe of #122

@mdqst
Copy link
Author

mdqst commented Apr 14, 2025

Dupe of #122

I was the one who reported the issue first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants