Skip to content

Trade API: next steps #61

@cgewecke

Description

@cgewecke

⚠️ Actively edited. ⚠️

Several things have been raised by the #60 review that should be addressed in subsequent PRs

  • Service is can easily fail if one of the (many) external resource calls fails
  • Gas price oracles
    • Use fallbacks? e.g gasNow and EthGasStation ?
  • CoinGecko token list: especially bad for polygon which makes 4 external calls to compose a list.
    • (from review) In a follow up, we should make this fault tolerant to CoinGecko API failures, return default values for things like estimated USD value, and return some kind of error that indicates CoinGecko failed.

    • Pricing seems pretty time sensitive... perhaps we can have redundancy via another service?
    • Could also maintain our own token list (for metadata) and generate in a CI chron job / publish to github?
    • fallback on the dynamic generation if that fails?

Resolved in #60

  • Currently formats prices as dollar strings.
  • Should this be configurable, e.g pick your national currency
  • Should formatting be delegated to quote consumer?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions