BEP-520: Short Block Interval Phase One: 1.5 seconds

[buddh0]

Description

BEP-520: Short Block Interval Phase One – 1.5 Seconds

bytecode change for ValidatorContract can refer feat: Short Block Interval Phase One – 1.5 Seconds for BEP-520

Rationale

tell us why we need these changes...

Example

add an example CLI or API response...

Changes

1. Add support for Millisecond Representation in Block Header, allowing users to retrieve the new milliTimestamp field via RPC.
2. Increase the epoch length from 200 to 500. The transition occurs at the first block where Number % 500 == 0 after the Lorentz hard fork.
3. Increase initialBackOffTime
4. Adjust GasLimitBoundDivisor from 256 to 1024.
5. Double Blob MinBlocksForBlobRequests and introduce MinTimeDurationForBlobRequests to determine whether blob data is needed.
6. Trigger distributeFinalityReward every 200 blocks instead of every epoch.
7. update bytecode for ValidatorSetContract
8. Increase cache sizes for headerCacheLimit, tdCacheLimit, and inMemorySnapshots.

[buddh0]

force push from dd24c3d to 487b67d just rebase develop to pass Nancy CI, no code changes.