This Week in Lotus - Week 21

👋 Hey everyone and welcome to This Week in Lotus!

This week´s update is filled with a massive amount of new upcoming features!! We have seen some great PRs from community members this week, so a big thanks for all the contributions 💙

NV16 Updates:

• FIP0030, FIP0031, and FIP0032 have passed out of Last Call status and are now accepted! 🎉🚀🔥 These FIPs, which jointly support the introduction of the non-programmable Filecoin Virtual Machine, are now ready for implementation.
• The nv16 upgrade has undergone testing on the Caterpillar network this week, and numerous bugs have been surfaced and fixed. We will continue the testing on the Butterfly network next week.
• The network upgrade is expected late June/early July; for more information, see HERE.

Bugfixes for common issues

• The lotus-miner proving compute window-post <Deadline> command lets you manually trigger a window-post computation, even on deadlines/partitions that are faulty.
• Aliases to the Discover method have been re-added which should fix the rpc.discover not found issue.
• PoSt-workers now check the proof parameter on startup.

New Features

• A new simpler worker assigning logic has been enabled in the configuration file. The new spread configuration allows you to ignore worker utilization, and rather spread the tasks to as many eligible workers for that task as possible.
• On top of the above PR, there is now an option to DisallowRemoteFinalize in the configuration file. When set to true it will force all Finalize tasks to run on workers with local access to both long-term storage and the sealing path containing the sector.
• And as if that was not enough, Magik 🪄 has created another big scheduler improvement: Now you can set a per worker maximum concurrent task count limit without tweaking the cpu/memory resource numbers. Just set it with this resource environment variable: [short task type]_[sector size]_MAX_CONCURRENT=[limit].
• The lotus-gateway now also supports OpenRPC.
• Ever wanted to benchmark just a single sealing task without running the whole sealing pipeline?👨‍🔬👩‍🔬 lotus-bench simple is now a thing, and it lets you benchmark the performance of a single task. It supports all tasks you want to benchmark: AP, PC1, PC2, C1, C2, windowPoSt, winningPoSt, RU, PRU1, PRU2. It is currently in review, so you can expect it to be merged into the code soon.

Do you want to clean up your environment variables a bit and have FIL_PROOFS_MAXIMIZE_CACHING in your variables list? This variable can be discarded as it isn´t a thing anymore, and has not been for a while. 🧹

For storage providers in the community: We have created a dedicated discussion for Lotus Task Benchmarks. We would love to see more storage providers share their numbers, so add your benchmarks following the template if you want to contribute 😄

That’s it for the week! Have a great weekend! ☀️