Skip to content

feat: PR from asset-metadata-service for token onboardings - #10040

Closed
asset-metadata-bot[bot] wants to merge 4 commits into
masterfrom
ams-bot-tokens
Closed

asset-metadata-bot[bot] wants to merge 4 commits into
masterfrom
ams-bot-tokens

Conversation

@asset-metadata-bot

Copy link
Copy Markdown
Contributor

This is a token onboarding PR opened by asset-metadata-service.

@asset-metadata-bot
asset-metadata-bot Bot requested a review from a team as a code owner October 23, 2026 06:32

@claude claude 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.

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

Tip: disable this comment in your organization's Code Review settings.

@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

⚠️ Unit tests are failing on Node 26.x (Current release line, non-blocking). This is not an LTS version yet, so it does not block merge, but it signals an incompatibility to fix before Node 26.x becomes LTS.

View run

hrishikeshjain
hrishikeshjain previously approved these changes Oct 23, 2026
The AMS API token import regenerated botTokens and botOfcTokens and dropped
entries that exist on master: the base tokens hteth:WBTC, hteth:tgku and
hteth:stzamakms with their OFC variants ofchteth:WBTC, ofchteth:tgku and
ofchteth:stzamakms, and CoinFeature.STAKING on hteth:zamamock.

Restore all of them from master verbatim, at their original positions. This
fixes the ZAMA staking feature tests in @bitgo/statics.
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.

1 participant