Skip to content

Conversation

@mounibec
Copy link

Description

Adds VLR. It's the native token of the Velora protocol. It's a utility token allowing users to govern the protocol's DAO and capture part of its revenue in exchange for staking and liquidity provision.

Tests

Additional context

Metadata

@mounibec mounibec requested a review from a team as a code owner September 16, 2025 20:59
@wiz-inc-a178a98b5d
Copy link

Wiz Scan Summary

Scanner Findings
Vulnerability Finding Vulnerabilities -
Data Finding Sensitive Data 1 Low
Total 1 Low

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.

@fainashalts
Copy link
Contributor

Hey @mounibec this PR is failing validation - please double check that everything is correct. Thanks!

@its-everdred
Copy link

Hi @mounibec bumping this once more, please review validation failures.

@mounibec
Copy link
Author

Hi @mounibec bumping this once more, please review validation failures.

Hey, I see that failure points to a private Circle CI that needs login. Can you point me to the issue and I'll check it. Thanks

https://app.circleci.com/pipelines/github/ethereum-optimism/ethereum-optimism.github.io/1923/workflows/604265d9-9280-4683-ab28-b32db973d4ee?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-checks-link&utm_content=bottom

@its-everdred its-everdred added the base PR require review from base team label Oct 24, 2025
@its-everdred
Copy link

its-everdred commented Oct 24, 2025

@mounibec Rerunning validation shows the actual error:

Below are the results from running validation for the token changes. To re-run the validation locally run: pnpm validate --datadir ./data --tokens VLR,VLR

These errors caused the validation to fail:
VLR on chain ethereum token 0x4e107a0000db66f0e9fd2039288bf811dd1f9c74 has incorrect name. Got Velora
VLR on chain optimism token 0x4e107a0000db66f0e9fd2039288bf811dd1f9c74 has incorrect name. Got Velora
VLR on chain optimism token 0x4e107a0000db66f0e9fd2039288bf811dd1f9c74 could not fetch l2Bridge or l1Token.
                    This token most likely needs nobridge or a bridge override set.
VLR on chain base token 0x4e107a0000db66f0e9fd2039288bf811dd1f9c74 has incorrect name. Got Velora

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

base PR require review from base team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants