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
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
Run 'lotus-miner info'
Check 'Available'
The value is not same to any block explorer like fliscan
Describe the Bug
Run 'lotus-miner info'
Check 'Available'
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
The text was updated successfully, but these errors were encountered:
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~
Checklist
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.Lotus component
Lotus Version
Repro Steps
Describe the Bug
Logging Information
The text was updated successfully, but these errors were encountered: