Calibration network genesis should have a faucet account for tokens and datacap

[aarshkshah1992]

Checklist

• [X] This is not brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on the lotus forum and select the category as Ideas.
• [X] I have a specific, actionable, and well motivated feature request to propose.

Lotus component

• [ ] lotus daemon - chain sync
• [ ] lotus fvm/fevm - Lotus FVM and FEVM interactions
• [ ] lotus miner/worker - sealing
• [ ] lotus miner - proving(WindowPoSt/WinningPoSt)
• [ ] lotus JSON-RPC API
• [ ] lotus message management (mpool)
• [ ] Other

What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.

Caliberation network genesis should have a faucet account for tokens and datacap.

Describe the solution you'd like

Only migrate the f090 Actor to a keyless Actor if it is a multisig.

Describe alternatives you've considered

No response

Additional context

No response

[BigLep]

Related butterfly issue (https://github.com/filecoin-project/lotus/issues/12160 ), which links to Slack thread with more info.

[f8-ptrk]

isn't the FIPs implementation wrong if this gets done on a non multisig f090 in the first place?

the fip explicitly says that it only applies to a multisig f090 actor.

Convert f090 actor type from a multisig to account type

this should not need network specific implementations.

The new account actor should be keyless, like f099

this branch should never been reached if its not a multisig f090

[aarshkshah1992]

@f8-ptrk

The implementation now ensures that f090 is a multisig before doing the migration. Please see https://github.com/filecoin-project/go-state-types/pull/281.

[rjan90]

We will keep the ticket open until the Calibration upgrade has happened.

[f8-ptrk]

@aarshkshah1992 my worries were non public networks here that would have needed adjustment too if this would have been solved via a calib/butterfly specific fix