You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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?
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.
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
andestimated_outbound
values in sip10 tokens balance request response, same as for stx balanceThe text was updated successfully, but these errors were encountered: