refactor: remove legacy v1 token supports in sdk#458
Conversation
Deploying with
|
| Latest commit: |
87becf7
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://97d58d34.swim-ui.pages.dev |
| Branch Preview URL: | https://remove-legacy-v1-code-from-s.swim-ui.pages.dev |
379aead to
5d472e1
Compare
7cd2aa9 to
ea7276a
Compare
ea7276a to
4072756
Compare
wormat
left a comment
There was a problem hiding this comment.
Definitely a step in the right direction.
4072756 to
e390122
Compare
e390122 to
1587efb
Compare
| icon: USN_SVG, | ||
| isStablecoin: true, | ||
| isLp: false, | ||
| tokenNumber: 0x0102, |
There was a problem hiding this comment.
Is there anything note-worthy about removing a token project that may have allocated a token number? Is this token number re-usable?
There was a problem hiding this comment.
It would need to be changed in all the routing contracts. Not sure if that's possible. @swimivan? @swimricky?
There was a problem hiding this comment.
We never had a (test)pool for it so the SwimRouter never heard of it in the first place.
And the SwimRouter also allows reuse of token numbers, so it's doubly not an issue.
So remove away.
swimdrew
left a comment
There was a problem hiding this comment.
Reviewed for USN removal, looks good. Can also remove mention of USN in apps/scripts
4c0979b to
87becf7
Compare
| wrappedDetails: EMPTY_MAP, | ||
| }, | ||
| ], | ||
| pools: [], |
There was a problem hiding this comment.
Is the plan to add these in a later PR?
There was a problem hiding this comment.
I will see if I can include it in next pr easily, if not I will create another PR for that
Notion ticket: https://www.notion.so/exsphere/Remove-any-kind-of-legacy-support-from-the-SDK-e2bb36ec76164d2e98de8a270296e9d8
Checklist