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

getTransactionDetails details API if not showing block confirmations dynamically #12

Open
4 tasks done
vivekteega opened this issue Mar 31, 2023 · 1 comment
Open
4 tasks done
Assignees
Labels
bug Something isn't working

Comments

@vivekteega
Copy link
Member

vivekteega commented Mar 31, 2023

The block confirmation time doesn't change on Floscout's token system transactions. Make them dyanmic

https://ranchimall.github.io/floscout/#/transaction/e6338071b4247003e16aae50e2696d42f42df116b928122bd94c3c718fbd70bc

  • Why are the block confirmation numbers stored into the database different for each transaction? some have 1 as static, some have 2236509 as static number
  • Calculate the block confirmations on the API side dynamically everytime you give out transaction information
  • CREATE A STANDARD FUNCTION FOR THE POINT ABOVE
  • Make the changes available in both version 1 and version 2 of the API
@vivekteega vivekteega self-assigned this Mar 31, 2023
@vivekteega vivekteega added the bug Something isn't working label Mar 31, 2023
@vivekteega
Copy link
Member Author

vivekteega commented Apr 3, 2023

Fix in version 1 - 5c91f76

Fix in version 2 - ab84bca

  • Why are the block confirmation numbers stored into the database different for each transaction? some have 1 as static, some have 2236509 as static number

For the above be more specific, which txs? Write down the txhashes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant