Add GenesisUnixTime and EpcohDurationInSeconds to StateGetNetworkParams

[eshon]

Checklist

• 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.
• 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.

These would be useful to have in StateGetNetworkParams to help tie epochs to IRL dates (for UX/DX)

Reference:
https://filecoinproject.slack.com/archives/CP50PPW2X/p1718780294027079?thread_ts=1714814756.768149&cid=CP50PPW2X

Describe the solution you'd like

Re-filing #12114 because it was a good idea...

Add these 2 fields to StateGetNetworkParams:

• GenesisUnixTime
• EpcohDurationInSeconds

Describe alternatives you've considered

No response

Additional context

No response

[rvagg]

This should be fairly straightforward and I think would be a nice usability improvement over what we to do now outside of lotus. Marking as good first issue.

GenesisUnixTime -> probably GenesisTimestamp would be more consistent. It's already available on ChainGetGenesis but a little tucked away:

curl -s https://api.node.glif.io/rpc/v1 -X POST -H "Content-Type": "application/json" --data '{"method":"Filecoin.ChainGetGenesis", "params":[], "id":1,"jsonrpc":"2.0"}' | jq '.result.Blocks[0].Timestamp'
1598306400

But it's also trivial to look up so could easily go in StateGetNetworkParams, GetGenesis from the ChainStore gives us that tipset, get the first block and read its Timestamp propery.

EpochDurationInSeconds should come off buildconstants.BlockDelaySecs. The only caveat with this one is that on testnets, particularly through itests, we often adjust it internally and it doesn't match that constant. We could consider making it a var for params_2k.go and adjusting it in the itest kid, but that's probably not strictly necessary, it just might be a good thing to try out so we have consistency.

[keval215]

I'd like to take this up!
Can you assign this to me

[rjan90]

Hey @keval215! Feel free to take this on, I have assigned you to the issue ticket

[rjan90]

Hey @keval215! What is the status on this ticket? Are you still up for taking this on?

[keval215]

Hey @rjan90 running a bit late, i am up for it , i'll get it done by this week

[rjan90]

@keval215 Were you able to take a look at this ticket? Was there anything unclear that we can clarify for you? No worries if you don't have the bandwidth to take it up; I just want to understand if I should still keep this ticket assigned to you.