Skip to content

fix: price Forma native TIA via zero-address native asset#8873

Open
jeremytsng wants to merge 4 commits into
mainfrom
fix/missing-tia-price-support-for-forma-network
Open

fix: price Forma native TIA via zero-address native asset#8873
jeremytsng wants to merge 4 commits into
mainfrom
fix/missing-tia-price-support-for-forma-network

Conversation

@jeremytsng
Copy link
Copy Markdown
Contributor

@jeremytsng jeremytsng commented May 21, 2026

Explanation

Forma (eip155:984122) is an EVM rollup whose native gas token is TIA (Celestia). assets-controllers currently requests Forma's native spot price as eip155:984122/slip44:984122, a chain-ID-derived SLIP-44 reference.

We should not invent non-canonical SLIP-44 references. SLIP-44 coin types are a registry of real, assigned coin types and are not equivalent to chain IDs (they are not 1:1 — e.g. slip44:56 is EDRCoin, while Binance Smart Chain's native is slip44:714). TIA/Celestia has no registered SLIP-44 coin type, so slip44:984122 is a made-up value, and 984122 could be assigned to another network in the future.

This change switches Forma's native token to the zero-address native conventioneip155:984122/erc20:0x0000000000000000000000000000000000000000 — the same representation already used for other non-ETH natives in SPOT_PRICES_SUPPORT_INFO (e.g. Hemi, BOB, Berachain). The Price API resolves this to the CoinGecko celestia coin via a platform mapping. No SLIP-44 reference is invented, and no chainIdToNativeTokenAddress entry is needed (zero address is the default).

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

Note

Low Risk
Low risk: a single CAIP-19 mapping change for Forma’s native asset that only affects spot price resolution for chain 984122. Potential impact is limited to Forma native pricing if downstream APIs interpret the zero-address differently.

Overview
Fixes Forma (chain 984122) native token (TIA) spot price resolution by changing its SPOT_PRICES_SUPPORT_INFO entry from slip44:984122 to the zero-address native asset (erc20:0x0000000000000000000000000000000000000000).

Adds a CHANGELOG.md Fixed entry documenting the correction.

Reviewed by Cursor Bugbot for commit 11688c7. Bugbot is set up for automated code reviews on this repo. Configure here.

Request Forma's (eip155:984122) native gas token TIA as the zero-address
native asset (erc20:0x0) instead of a non-canonical SLIP-44 reference, so
the Price API resolves it via the CoinGecko celestia platform mapping.
@jeremytsng jeremytsng marked this pull request as ready for review May 21, 2026 11:03
@jeremytsng jeremytsng requested review from a team as code owners May 21, 2026 11:03
maxime-oe
maxime-oe previously approved these changes May 21, 2026
'0xdef1': 'eip155:57073/slip44:60', // Ink Mainnet - Native symbol: ETH
'0x3dc': 'eip155:988/erc20:0x779ded0c9e1022225f8e0630b35a9b54be713736', // Stable - Native symbol: USDT0
'0xf043a': 'eip155:984122/slip44:984122', // Forma - Native symbol: TIA (Celestia)
'0xf043a': 'eip155:984122/erc20:0x0000000000000000000000000000000000000000', // Forma - Native symbol: TIA (Celestia)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This chain is not supported by price-api. I'm unsure as to why it was added here in the first place, but should be removed.

https://price.api.cx.metamask.io/v2/supportedNetworks

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