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

[lotus-miner]The Available value in "lotus-miner info" seems not right #11951

Open
5 of 11 tasks
OneilYang opened this issue May 1, 2024 · 3 comments
Open
5 of 11 tasks
Labels
kind/bug Kind: Bug

Comments

@OneilYang
Copy link

Checklist

  • This is not a security-related bug/issue. If it is, please follow please follow the security policy.
  • I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
  • I am running the Latest release, the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
  • I did not make any code changes to lotus.

Lotus component

  • lotus daemon - chain sync
  • lotus fvm/fevm - Lotus FVM and FEVM interactions
  • lotus miner/worker - sealing
  • lotus miner - proving(WindowPoSt/WinningPoSt)
  • lotus JSON-RPC API
  • lotus message management (mpool)
  • Other

Lotus Version

lotus-miner -v
lotus-miner version 1.26.3+mainnet+git.560826d5c.dirty

Repro Steps

  1. Run 'lotus-miner info'
  2. Check 'Available'
  3. The value is not same to any block explorer like fliscan

Describe the Bug

  1. Run 'lotus-miner info'
  2. Check 'Available'
  3. The value is not same to any block explorer like fliscan

Logging Information

1. Run 'lotus-miner info'
2. Check 'Available'
3. The value is not same to any block explorer like fliscan
@OneilYang OneilYang added the kind/bug Kind: Bug label May 1, 2024
@beck-8
Copy link
Contributor

beck-8 commented May 11, 2024

Please submit evidence.

@beck-8
Copy link
Contributor

beck-8 commented May 11, 2024

image
It is just because StateMinerAvailableBalance also takes into account the locked positions to be released, types.BigAdd(abal, vested)

@OneilYang
Copy link
Author

Hi beck,

Yes, as you said, the available should be: yesterday's value+released vesting.
for example, if today avalilable = 1.23;
and if no reward and no withdraw happened, tomorrow the avaliable still = 1.23; (it should be 1.23+released vest, more than 1.23)

v1.25 seems good and only 1.26.3 found this problem;

(And I heard someone found other bugs like this one in the chat group, the winningreward and withdraw will trigger the update )

if anything unclear please feel free to let me know, thanks~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Kind: Bug
Projects
None yet
Development

No branches or pull requests

2 participants