Skip to content

Conversation

@rv-bitgo
Copy link
Contributor

@rv-bitgo rv-bitgo commented Jan 7, 2025

@rv-bitgo rv-bitgo requested review from a team and sachushaji January 7, 2025 15:28
@rv-bitgo rv-bitgo requested review from a team as code owners January 7, 2025 15:28
@rv-bitgo rv-bitgo changed the title chore: onboard GoUSD token with eth prefix chore: onboard GoUSD token with eth prefix WIN-4114 Jan 7, 2025
@rv-bitgo rv-bitgo force-pushed the make_gousd_eth_again branch from 3816c32 to cafedba Compare January 7, 2025 15:35
TGBP = 'tgbp',
TUSDS = 'tusds',
TGOUSD = 'tgousd',
GOUSD = 'gousd',
Copy link
Contributor

Choose a reason for hiding this comment

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

why do we need to change the base to eth: gousd?, only name needs to be changed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changing base isn't required but I just follow the convention since starting and since there are no enforcing rules, I stick to prefix eth to erc20 tokens.

6,
'0xf1f6b8cc3a0d544a40f1d29909396378370e6938',
UnderlyingAsset.GOUSD
UnderlyingAsset['eth:gousd']
Copy link
Contributor

Choose a reason for hiding this comment

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

no need to change the token name with eth prefixed?

Copy link
Contributor Author

@rv-bitgo rv-bitgo Jan 7, 2025

Choose a reason for hiding this comment

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

Updated.

Copy link
Contributor

@sachushaji sachushaji left a comment

Choose a reason for hiding this comment

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

LGTM

WIN-4114

feat(statics): update symbol to use eth prefix
@rv-bitgo rv-bitgo force-pushed the make_gousd_eth_again branch from c17f913 to 14e8ce2 Compare January 7, 2025 16:30
@rv-bitgo rv-bitgo merged commit 03402e3 into master Jan 7, 2025
6 checks passed
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