Skip to content

f3: lotus f3 powertable commands depend on chain state #13081

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

Open
Kubuxu opened this issue Apr 29, 2025 · 3 comments
Open

f3: lotus f3 powertable commands depend on chain state #13081

Kubuxu opened this issue Apr 29, 2025 · 3 comments

Comments

@Kubuxu
Copy link
Contributor

Kubuxu commented Apr 29, 2025

Without a full chain state, the lotus f3 powertable commands will stop working.
There is also no way to fetch the values of the initial power table without the chain state.

@github-project-automation github-project-automation bot moved this to Todo in F3 Apr 29, 2025
@github-project-automation github-project-automation bot moved this to 📌 Triage in FilOz Apr 29, 2025
@BigLep
Copy link
Member

BigLep commented May 2, 2025

@Kubuxu : how much should we worry about this case of not being able to get the initial power table if we don't have the chain state? I'm trying to gauge the priority of this.

@Kubuxu
Copy link
Contributor Author

Kubuxu commented May 2, 2025

The info is there (in go-f3 module), but it is not exposed.

@rvagg
Copy link
Member

rvagg commented May 28, 2025

I had a quick look at this and I think this issue needs more information about what the actual ask is here. As far as I can tell, the --ec flag makes it look up the power table from state (F3GetECPowerTable -> GetPowerTable -> getPowerTableLotusTSK (which is dependent on chain state). But without the --ec flag it calls into go-f3 itself, F3GetF3PowerTable -> GetF3PowerTable -> go-f3 GetPowerTable. So it's already fetching the power table from go-f3 itself.

There may be a chain state dependency that I'm missing, but that's the bit that needs more clarity for this issue to be closed by someone else I think.

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

No branches or pull requests

3 participants