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

Butterfly Network: clarify config ConsensusMinerMinPower and PreCommitChallengeDelay #12466

Open
rjan90 opened this issue Sep 16, 2024 · 0 comments

Comments

@rjan90
Copy link
Contributor

rjan90 commented Sep 16, 2024

Background

In build/buildconstants/params_butterfly.go, we have two variables which seem to be intended to be configurable for the Butterfly network:

var ConsensusMinerMinPower = abi.NewStoragePower(2 << 30)
var PreCommitChallengeDelay = abi.ChainEpoch(150)

As part of testing F3 I thought it would be useful to adjust these so that I could add participants to F3 in a very short timeframe, without having to wait on the PreCommitChallengeDelay or obtaining the current ConsensusMinerMinPower. I therefor adjusted these down to 256MiB and 10 epochs, but encountered this error when trying to submit:

Error: message ... failed: message execution failed: exit ErrForbidden(18), reason: message failed with backtrace:
00: f01006 (method 34) -- too early to prove sector (18)
(RetCode=18)

Root Cause

It appears that these parameters are actually defined in the actor bundle, not in the params_butterfly.go file. This is evidenced by the build configuration in the builtin-actors repository:
builtin-actors/actors/runtime/build.rs

Impact

The current setup is misleading, as it suggests that these parameters can be easily configured for the Butterfly network, when in reality, they require changes to the actors and generating a bundle for it.

@rjan90 rjan90 changed the title Butterfly Network: clarify config of ConsensusMinerMinPower and PreCommitChallengeDelay Butterfly Network: clarify config ConsensusMinerMinPower and PreCommitChallengeDelay Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📌 Triage
Development

No branches or pull requests

1 participant