Here is the @claude analysis of the CI failures:

Analysis Summary

PR #13304 is failing CI checks because the actor bundle update from v16.0.1 to v17.0.0-dev1 introduces new miner creation deposit requirements that the existing test configurations don't satisfy.

Root Cause

The failing tests all show the same error:
not enough balance to lock for create miner deposit: sent balance 0 < deposit 5937181320 (19)

This occurs during genesis miner creation for integration tests at ~/lotus/chain/gen/genesis/miners.go:179.

Key Issues

1. Actor Bundle Change: The v17.0.0-dev1 bundle now requires a ~5.937 nanoFIL deposit for miner creation
2. Test Configuration: All test setups use PowerBalance: big.Zero(), providing insufficient funds
3. Systematic Failure: This same error appears across all failing test types (itest-api, itest-eth_api, itest-fevm, etc.)

Connection to FIP-0077

While not explicitly referenced in the current lotus codebase, this deposit requirement likely implements the economic friction mechanism described in FIP-0077, which introduces mandatory deposits for miner creation to
prevent spam attacks.

Required Fix

Update test configurations in files like:

• ~/lotus/storage/sealer/mock/util.go:47
• ~/lotus/cmd/lotus-seed/main.go:208
• ~/lotus/cmd/lotus-seed/seed/seed.go:116

To set PowerBalance to at least types.NewInt(5937181320) or higher to satisfy the new miner creation deposit requirement.

This is a straightforward configuration update that should resolve all the systematic test failures once implemented.

The good news is that it looks to only be FIP-0077 related failures, which is what we're wanting to see. This will get worked on as part of #13287, with the cutoff of 2025-09-04T12:00:00Z per #fil-implementers slack discussion.

@BigLep follow-up here is to write a basic integration test in migration_test.go that straddles the NV boundary and checks that methods are gone and some other basic probes. It also might be the most logical place to put a miner creation fee test too -- one before and one after upgrade to show it not needing, and then needing a fee of appropriate size. DDO tests can go in direct_data_onboard_test.go or direct_data_onboard_verified_test.go, just extending what we have there with some fevm-copypasta code to get a contract in.

@rvagg:

follow-up here is to write a basic integration test in migration_test.go that straddles the NV boundary and checks that methods are gone and some other basic probes. It also might be the most logical place to put a miner creation fee test too -- one before and one after upgrade to show it not needing, and then needing a fee of appropriate size.

Makes sense, I assume that can come the 2025-09-04:12:00Z cutoff for getting this PR green so @TippyFlitsUK can do the Lotus 1.34.0 RC?

DDO tests can go in direct_data_onboard_test.go or direct_data_onboard_verified_test.go, just extending what we have there with some fevm-copypasta code to get a contract in.

Am I right to assume that comment is relevant for #13286 ? if so, I'll copy it there. Or is FIP-0109's inclusion in the 17.0.0-dev1 actor bundle causing CI failures in this PR as well?

#13286 is fine as is, not blocking this PR and shouldn't result in breakage.

@TippyFlitsUK : I'll work on resolving conflicts now (unless you're already on it).