Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add support for non-native tokens as txn fees #4633

Open
Tracked by #3321
ameten opened this issue Oct 7, 2024 · 0 comments
Open
Tracked by #3321

feat: Add support for non-native tokens as txn fees #4633

ameten opened this issue Oct 7, 2024 · 0 comments

Comments

@ameten
Copy link
Contributor

ameten commented Oct 7, 2024

Issue

Scraper fails to store a transaction to database if the transaction has fees expressed in a non-native token.

Introduction

Currently if transaction fees are expressed in a non-native token, Scraper won't store it into database since it is not capable to calculate gas price in this case.

Tasks

  1. Analyse how we would like to express gas price (in native token per unit, in non-native token per unit).
  2. Analyse where we shall get mapping from non-native token id (ibc/<id>) to the name of this token.
  3. Analyse where we shall get the conversion rate for gas price.
  4. Analyse how we are going to store non-native token names (symbols) in Scraper database
@ameten ameten changed the title feat: Add support for non-native cryptocurrecies as txn fees feat: Add support for non-native tokens as txn fees Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant