V3 Changes

• Update https://github.com/Synthetixio/synthetix-v3/blob/main/protocol/synthetix/cannonfile.toml#L164 to "sUSD"
• Create a new release of the synthetix package.
• Update the deployments repo to use the new release of the synthetix package.
• Update https://github.com/Synthetixio/synthetix-deployments/blob/0fd7257478517a8f8c03fe37ca8ba6b6b12f3e79/tomls/markets/spot/btc.toml#L11 to replace "snxBTC" with "sBTC" and make analogous changes to all other files in that directory.
• Run a release on the deployments repo, creating a new version of the synthetix-omnibus package.

V2 Changes

The string sUSD (and synth tickers) are used throughout the codebase, including as currencyKeys which are used in external facing functions. Presumably, we’d like to leave these as-is, and only change the return value of symbol functions.

The symbol for synths (including sUSD) is returned via the getter automatically generated by Solidity for public variables. We could change this variable to private, rename it to avoid an Identifier already declared error, and create a getter that appends the string legacy. The changes to the existing variable should not alter the storage layout and cause issues during upgrade, but this need verification from the auditors.

The implementation would look something like this:

Comments/Questions

• Note that only the symbol are being renamed in the SIP spec, not the name values. If the latter is desired, ideally this could be processed at the same time.
• Token names/symbols are found throughout the internet (e.g. token lists). Perhaps if PRs are made to update the old tokens, the new v3 tokens could be submitted simultaneously?
• Are there concerns with the timeline/sequencing of these changes, or should the Core Contributors work towards executing the changes as soon as possible? The V3 change is essentially an SCCP since the last release and typically wouldn’t require audit (though we’ll get auditor input on this entire plan). The V2 change would be a code change, so may require a little more time for audit and execution. Next week is probably realistic in any case; asking for clarification as there was talk of coordinating this with migrations, etc.