Skip to content

Conversation

@rjan90
Copy link
Contributor

@rjan90 rjan90 commented Jan 13, 2026

Related Issues

filecoin-project/go-f3#1054

Proposed Changes

fix: update F3-calibnet name and epoch

Checklist

Before you mark the PR ready for review, please make sure that:

fix: update F3-calibnet name and epoch
@rjan90 rjan90 self-assigned this Jan 13, 2026
@rjan90 rjan90 added the skip/changelog This change does not require CHANGELOG.md update label Jan 13, 2026
@github-project-automation github-project-automation bot moved this to 📌 Triage in FilOz Jan 13, 2026
@github-project-automation github-project-automation bot moved this to Todo in F3 Jan 13, 2026
"BootstrapEpoch": 2081674,
"NetworkName": "calibrationnet",
"BootstrapEpoch": 3385534,
"NetworkName": "calibrationnet2",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe InitialPowerTable field needs to be unset as well.

fix: unset `InitialPowerTable`
@Kubuxu
Copy link
Contributor

Kubuxu commented Jan 13, 2026

This also needs to change:

gpbftTopic := manifest.PubSubTopicFromNetworkName(in.F3Config.BaseNetworkName)

I think we can completely remove the BaseNetworkName concept at this point. Given that we are not running multiple different networks in Lotus anymore.

Remove BaseNetworkName from lf3.Config and use the manifest's NetworkName
directly for pubsub topic filtering. This was the only remaining use of the
Filecoin-to-F3 network name mapping, which is no longer needed now that the
F3 network name is explicitly defined in the manifest.
@rjan90 rjan90 changed the title fix: update F3-calibnet name and epoch fix: update F3-calibnet name and bootstrap epoch Calibnet Jan 13, 2026
@rjan90
Copy link
Contributor Author

rjan90 commented Jan 13, 2026

Opening for review. Depends on: filecoin-project/go-f3#1061. Needs sanity testing on both Calibnet and Mainnet nodes, before merge. And depending on time before merging, bootstrap epoch might need a update.

@rjan90 rjan90 marked this pull request as ready for review January 13, 2026 13:39
@rjan90 rjan90 moved this from 📌 Triage to ⌨️ In Progress in FilOz Jan 15, 2026
@rjan90 rjan90 moved this from Todo to In progress in F3 Jan 15, 2026
@github-project-automation github-project-automation bot moved this from In progress to In review in F3 Jan 15, 2026
@github-project-automation github-project-automation bot moved this from ⌨️ In Progress to ✔️ Approved by reviewer in FilOz Jan 15, 2026
chore: bump go-f3 version to v0.8.11
Added a check for the availability of the F3 manifest before importing F3 data into the datastore. If the manifest is not available, a warning is logged, and the import is skipped, allowing the chain import to continue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip/changelog This change does not require CHANGELOG.md update

Projects

Status: In review
Status: ✔️ Approved by reviewer

Development

Successfully merging this pull request may close these issues.

4 participants