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 tactical support for non-native tokens as txn fees #4641

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

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

ameten opened this issue Oct 8, 2024 · 0 comments

Comments

@ameten
Copy link
Contributor

ameten commented Oct 8, 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.

Support only TIA and ATOM as transaction fees.

https://neutron.celat.one/neutron-1/txs/3cb9086829d44af45e914c335c877b17fe70234ab1515d128a0486ff8c47db91
https://neutron.celat.one/neutron-1/txs/d16d6ce85b4b4d30cfd25d8313607f8e24fcf04f282cbe484aaf7b38552cf069
https://neutron.celat.one/neutron-1/txs/d3a2bc17bf7dec51a2c7710e013a9af5d704676f5c872541836f7ef3159acdec

Tasks

  1. Hardcode ibc/<ids>, token names and denominations for tokens seen in the Neutron chain as transaction fees Scraper has to process.
  2. Add conversion of non-native tokens into 10^-18.
  3. Add column into transaction table with identifier of the token for fees.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

1 participant