v1.18.0 #9653
jennijuju
announced in
Announcement
v1.18.0
#9653
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is the final release of the upcoming MANDATORY release of Lotus that introduces Filecoin network v17,
codenamed the Shark upgrade. Shark upgrade delivers a wave of protocol refinements that will allow for useful smart contracts to be written using the FVM (eg. programmable markets, lending contracts, etc.).
The Filecoin mainnet is scheduled to upgrade to nv17 at epoch 2383680, on Nov 30th on 2022-11-30T14:00:00Z. All node operators, including storage providers, must upgrade to this release before that time. Storage providers must update their daemons, miners, market and worker(s)/boost.
The Shark upgrade introduces the following FIPs, delivered in actors v9:
PublishStorageDeals
/ProveCommit(Aggregate)
/ProveReplicaUpdates
message that includes verified deals will see a gas usage increase, more details can be found hereTerm
is introduced for defining how long the DataCap is assigned to a piece of data. Anyone who cares about that piece of data may extend the term, which incentives SPs to store the data longer on the network without a new deal/resealing.term_max
is alwaysdeal duration + 90 days
.❗ We highly recommend all lotus users, especially storage providers, developers and clients to read the FIPs in detail to understand the protocol changes and potential impact to network participants!
Snapshots
The #fil-infra team at PL has launched a brand new Lightweight Filecoin Chain Snapshots Service to support chain management needs for the node operators, check here for the full detail.
We are planning to switch the snapshot service listed in lotus docs to the new Lightweight Filecoin Chain Snapshots Service by EOY, and deprecate public support of the current snapshots production. We recommend all users to test and switch the new service ASAP, and if you run into any issue, please report them here and the team would be happy to support you! For the main differences between the old & the new service, checkout the FAQ section here
Migration
We are expecting a heavier than normal state migration for this upgrade due to the amount of the state changes introduced.
All node operators, including storage providers, should be aware that two pre-migrations are being scheduled. The first pre-migration will begin at 2022-11-30T12:00:00Z (120 minutes before the real upgrade), the second pre-migration will begin at 2022-11-30T13:45:00Z (7.5 minutes before the real upgrade).
The first pre-migration will take up to 1.5hr, depending on the amount of the historical state in the node blockstore and the hardware specs the node is running on. During this time, expect slower block validation times, increased CPU and memory usage, and longer delays for API queries.
We recommend node operators (who haven't enbabled splistore
universal
mode) that do not care about historical chain states, to prune the chain blockstore by syncing from a snapshot 1-2 days before the upgrade.Note to full archival node operators: you may expect a migration that takes up to 20 min upon the upgrade, during this period your node will fall out of sync and your chain service may have some disruption. However, you can expect the node to catch up soon after the migration completes.
v9 Built-in actor bundles
Bundles for all networks(mainnet, calibnet, and etc) are included in the lotus source tree (
build/actors/
) and embedded on build, for v9 actors you can find it here.Reminder: Lotus verifies that the bundle CIDs are the right ones upon build & upgrade against the values in
build/builtin_actors_gen.go
, according to the network you are building. You may also check the bundle manifest CID matches the bundle gen-ed values by runninglotus state actor-cids --network-version 17
.The manifest CID & full list of actor code CIDs for nv17 using actor v9 is:
New Features
Improvements
Dependencies
Others
lotus-market EOL notice
As mentioned in lotus v1.17.0 release notes, markets related features, enhancements and fixes is now lower priority for Lotus. We recommend our users to migrate to other deal making focused software, like boost as soon as possible. That being said, the lotus maintainers will be:
If you have any questions or concerns, please raise them in Lotus discussion!
Contributors
This discussion was created from the release v1.18.0.
Beta Was this translation helpful? Give feedback.
All reactions