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

[Bug]: Available Balance incorrect on foundation address #925

Closed
2 tasks done
luca-moser opened this issue Dec 13, 2023 · 3 comments · Fixed by #995
Closed
2 tasks done

[Bug]: Available Balance incorrect on foundation address #925

luca-moser opened this issue Dec 13, 2023 · 3 comments · Fixed by #995
Assignees

Comments

@luca-moser
Copy link
Member

Issue description

The available balance shown at the foundation's address from the supply increase is incorrect.

https://explorer.iota.org/mainnet/addr/iota1qp8h9augeh6tk3uvlxqfapuwv93atv63eqkpru029p6sgvr49eufyz7katr?tab=Transactions

Expected behaviour

It should show the available balance stemming from the outputs which are available (not timelocked anymore)

Actual behaviour

It shows 715302.14 IOTA being available even though there are at least 4 outputs which are no longer time locked and are not yet spent amounting to a total >11266259.4 IOTAs.

Can the issue reliably be reproduced?

Yes

Steps to reproduce the issue

No response

Errors

No response

Duplicate declaration

  • I have searched the issues tracker for this issue and there is none

Code of Conduct

  • I agree to follow this project's Code of Conduct
@begonaalvarezd
Copy link
Member

@panteleymonchuk the problem seems to be on the chronicle endpoint, sigLockedBalance is not "available balance" but rather something like is_trivial_unlock which is not very useful, we are discussing with the chronicle team to decide on a solution

@begonaalvarezd
Copy link
Member

Blocked by iotaledger/inx-chronicle#1312

@panteleymonchuk
Copy link
Collaborator

panteleymonchuk commented Jan 19, 2024

Seems this issue was fixed by iotaledger/inx-chronicle#1312
Fix will be available after deploy migration.

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

Successfully merging a pull request may close this issue.

3 participants