Skip to content

[Dev Hub] Add VOLATILE to Linea token list - #285

Closed
VGau wants to merge 1 commit into
mainfrom
add/volatile
Closed

[Dev Hub] Add VOLATILE to Linea token list#285
VGau wants to merge 1 commit into
mainfrom
add/volatile

Conversation

@VGau

@VGau VGau commented Feb 6, 2026

Copy link
Copy Markdown
Collaborator

Add VOLATILE to Linea token list from the Linea Developer Hub.


Note

Low Risk
Single-entry token list update with a minor version bump; risk is limited to potential downstream display/lookup issues if the new token metadata is incorrect.

Overview
Updates the Linea mainnet token shortlist by adding the VOLATILE token (native, 0x5c1bf4b7563c460282617a0304e3cde133200f70, 18 decimals, logo URI) and bumping the list version from 1.70.1 to 1.71.1.

Also leaves the JSON file without a trailing newline.

Written by Cursor Bugbot for commit f9eb0b3. This will update automatically on new commits. Configure here.

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 2 potential issues.

{
"major": 1,
"minor": 70,
"minor": 71,

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

File-level updatedAt not updated for new token

Low Severity

The file-level updatedAt field remains "2026-02-04" but the newly added VOLATILE token has createdAt and updatedAt set to "2026-02-06". The development guide explicitly states to "Update the updatedAt (and potentially createdAt) fields for the file and the token" when making changes, so the file-level updatedAt needs to reflect the actual date of this modification.

Additional Locations (1)

Fix in Cursor Fix in Web

{
"major": 1,
"minor": 70,
"minor": 71,

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Patch version not reset when minor bumped

Low Severity

The minor version was bumped from 70 to 71 (correctly, for adding a new token), but patch was left at 1 instead of being reset to 0. Per semver convention, incrementing minor requires resetting patch to 0. The Linea Sepolia token list (minor: 4, patch: 0) follows this convention correctly, making this inconsistent.

Fix in Cursor Fix in Web

@alainncls

Copy link
Copy Markdown
Collaborator

Spam/Ignored

@alainncls alainncls closed this Feb 16, 2026
@alainncls
alainncls deleted the add/volatile branch February 16, 2026 18:11
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.

2 participants