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

Provide more granulaity for disabling F3 functionality #732

Open
Kubuxu opened this issue Nov 1, 2024 · 1 comment
Open

Provide more granulaity for disabling F3 functionality #732

Kubuxu opened this issue Nov 1, 2024 · 1 comment

Comments

@Kubuxu
Copy link
Contributor

Kubuxu commented Nov 1, 2024

Currently, we only provide LOTUS_DISABLE_F3. I propose adding two additional flags to resolve possible incidents without significantly impacting the entire F3 project.

LOTUS_DISABLE_F3_ACTIVATION=$epoch, which would disable the activation at a given epoch
LOTUS_DISABLE_F3_PASSTIVE_TESTING=1, which would disable passive testing components and leave only proper activation

@Kubuxu
Copy link
Contributor Author

Kubuxu commented Nov 19, 2024

LOTUS_DISABLE_F3_PASSTIVE_TESTING=1 was merged
LOTUS_DISABLE_F3_ACTIVATION is not yet complete.

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

No branches or pull requests

2 participants