feat: delay Curie fork on mainnet by 1 day

[Thegaram]

1. Purpose or design rationale of this PR

Delay +1 day to accommodate verifier contract timelock delay.

2. PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• feat: A new feature

3. Deployment tag versioning

Has the version in params/version.go been updated?

• This PR doesn't involve a new deployment, git tag, docker image tag, and it doesn't affect traces
• Yes

4. Breaking change label

Does this PR have the breaking-change label?

• This PR is not a breaking change
• Yes

[colinlyguo]

interesting. the time interval is not exactly 24 * 3600 secs. Could I ask where's the small diff come from?

[Thegaram]

interesting. the time interval is not exactly 24 * 3600 secs. Could I ask where's the small diff come from?

Yeah, in hindsight, I could have just added 24 * 3600. Instead I calculated a new target date using the current timestamp and the current latest block number.

[colinlyguo]

interesting. the time interval is not exactly 24 * 3600 secs. Could I ask where's the small diff come from?

Yeah, in hindsight, I could have just added 24 * 3600. Instead I calculated a new target date using the current timestamp and the current latest block number.

this makes more sense. since the real block generation time would draft a bit later. we can always make the expected diff smaller.