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

Add estimated_inbound and estimated_outbound values in sip10 tokens balances #2209

Closed
alter-eggo opened this issue Jan 28, 2025 · 3 comments
Closed

Comments

@alter-eggo
Copy link

Is your feature request related to a problem? Please describe.
Actual problem is already described in this issue
We need to do 2 requests to get available balance

Describe the solution you'd like
Solution is to add estimated_inbound and estimated_outbound values in sip10 tokens balance request response, same as for stx balance

Image

@zone117x
Copy link
Member

It doesn't look like we can do this for FTs like we can for STX transfers. A plain, non-evaluated stx-transfer type transaction in the mempool directly indicates the STX transfer amounts. However, FT transfers happen after a transaction is executed. In other words, the arbitrary contract-call and contract-deploy type txs in the mempool are opaque with regards to their eventual evaluated outcome (e.g. FT transfers).

@rafaelcr did you have any thoughts around how some way to work around this?

@rafaelcr
Copy link
Collaborator

Good point @zone117x . I don't think we're going to be able to do this without the node giving us more information about pending transactions, which would require a big change on their end.

@alter-eggo unfortunately we won't be able to build this feature.

@rafaelcr rafaelcr closed this as not planned Won't fix, can't repro, duplicate, stale Jan 30, 2025
@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in API Board Jan 30, 2025
@alter-eggo
Copy link
Author

I see, ok

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants