feat: skip track/status endpoints [OTE-354]

[yogurtandjam]

Blocked by: https://github.com/dydxprotocol/v4-abacus/pull/471/files

This PR adds functionality for skip's track and status endpoints.
We unfortunately need a lot of code in order to make the skip payload consumable and swappable with the existing squid code. We decided to go this route to ensure we localize all the logic into one area.

Once we remove squid completely, we can begin refactoring our skip code to be more 'true' to its API. This will likely come hand in hand with 2 other things:

• skip is going to make their API more easily consumable (likely a v3 thing)
• redesign of our status tracking widget. it's not designed to display transaction-by-transaction granularity which skip offers.

This PR also adds a lot of test code. The tests are there to ensure that through various payloads, we transform the skip payload to look functionally identical to the squid code. The doc describing the payload transformation is here: https://www.notion.so/dydx/Squid-Skip-Status-endpoint-1a15bd2cb45c4ccfbc0b095986ef4f09

---

Constants/Types

• public/configs/v1/env.json
  • adds skip endpoint param

Hooks

• src/hooks/useLocalNotifications.tsx

  • Swapped out fetchSquidStatus for fetchTransactionStatus

• src/hooks/useEndpointsConfig.ts

  • Added skip to endpoints config to allow DOS to plugin proxy server url override

• src/hooks/useNotificationTypes.tsx

  • The only place we did 'shotgun surgery'. The estimated route duration from squid is a number but skip doesn't provide one yet. So for now we're using a standard piece of text '<30 minutes' for the route duration which means we need to typecheck when rendering the notifications.

Functions

• lib/squid
  • This is where all the heavy lifting happens. We convert the payload from skip to look nearly identical to the payload from squid.
  • fetchSkipStatus - retrieves tx status from skip endpoint
  • trackSkipTx - posts to skip track endpoint to track a tx
  • fetchTransferStatus - retrieves either transfer status using either skip or squid endpoint
  • class TransactionData - consumes all relevant data necessary to create either a route status entry or a from/toChain entry. the reason why we do this
    • both objects share a good amount of data
    • why use 2 functions to retrieve 2 data forms when you can have one. why use many function when few function do same trick
    • yes, this can be a function - but i think it feels nicer having it a data class since it represents an entity of transfer data. either way this will be removed once we transition out of this dual squid/skip state.

Packages

• jsdom
  • adds jsdom package
  • necessary for testing util methods that use window

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
v4-staging	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 25, 2024 10:07pm
v4-testnet	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 25, 2024 10:07pm

[linear]

OTE-354 [v4-web] create trackSkipTransaction