Skip to content

Fix veBAL Etherscan contract link on FAQ page - #342

Merged
gosuto-inzasheru merged 1 commit into
v3-outlinefrom
cursor/fix-vebal-etherscan-link-0d99
Aug 6, 2026
Merged

Fix veBAL Etherscan contract link on FAQ page#342
gosuto-inzasheru merged 1 commit into
v3-outlinefrom
cursor/fix-vebal-etherscan-link-0d99

Conversation

@gosuto-inzasheru

Copy link
Copy Markdown
Collaborator

Summary

  • The veBAL FAQ contract table linked the veBAL contract to an Etherscan transaction URL (/tx/...) instead of the contract address.
  • Updated the link to https://etherscan.io/address/0xC128a9954e6c874eA3d62ce62B468bA073093F25 (VotingEscrow / veBAL), matching the address already documented on the Voting page.

Test plan

  • Open the veBAL FAQ page and confirm the veBAL row links to the contract address page on Etherscan
  • Confirm the linked address matches 0xC128a9954e6c874eA3d62ce62B468bA073093F25

Slack Thread

Open in Web Open in Cursor 

The veBAL FAQ contract table linked to a transaction hash instead of
the VotingEscrow contract address.

Co-authored-by: gosuto.eth <gosuto-inzasheru@users.noreply.github.com>
@cursor

cursor Bot commented Aug 6, 2026

Copy link
Copy Markdown

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

@vercel

vercel Bot commented Aug 6, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs-v3 Ready Ready Preview Aug 6, 2026 1:58pm

Request Review

@EndymionJkb EndymionJkb left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM!

@gosuto-inzasheru
gosuto-inzasheru merged commit 3e60874 into v3-outline Aug 6, 2026
2 checks passed
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