chore: remove Ternoa chain from agglayer token list#837
Merged
Conversation
Ternoa has spun down their CDK chain, so it is being retired from the agglayer token list. Removes the Ternoa chain entry (chainId 752025, networkId 13) from the chains metadata along with its 11 chain-resident token entries. Removing the chain and its tokens together avoids leaving orphaned tokens that reference a chain no longer present in the list, which is the case that would break consumers such as agglayer-ui. No token on any other chain references Ternoa as an origin/wrapped target, so no cross-chain mappings are affected.
py-zoid
force-pushed
the
chore/remove-ternoa-chain
branch
from
d4f2b1e to
fbbea76
Compare
shan8851
approved these changes
Jul 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Ternoa has spun down their CDK chain, so it is being retired from the agglayer token list.
chainId 752025,networkId 13) fromsrc/metadata/agglayer.json.chainId 752025) fromsrc/tokens/agglayer.json.Built
agglayer.tokenlist.jsonnow has 10 chains / 147 tokens, with no Ternoa references.Why remove the tokens too, not just the chain
Removing the chain entry while leaving tokens that reference
chainId 752025would leave orphaned tokens pointing at a chain no longer present in the list — the case most likely to break consumers (e.g. a UI doingchains.find(c => c.chainId === token.chainId)). Removing both together keeps the list internally consistent.Verified no token on any other chain references Ternoa as an origin/wrapped target (
originTokenNetwork: 13/eip155:752025→ 0 matches), so no cross-chain mappings are affected.agglayer-ui impact
Confirmed this does not break agglayer-ui:
agglayer.tokenlist.json— it simply stops offering Ternoa as a bridge option.ternoareference in agglayer-ui (wagmiConfig.ts,wallet.tsx) is an independent viem/wagmi/chainschain definition, unrelated to the token list; a follow-up cleanup PR there can drop it to fully retire Ternoa.Verification
npm run buildsucceedsnpm testpasses (3/3)Out of scope
The
mapped,popular, and*Staginglists still reference Ternoa (networkId 13); those feed the classic PoS/zkEVM bridge, not agglayer-ui, and can be handled separately if full retirement is desired.