Skip to content

Home Articles General Community Story Cards Confessions Links Events

More

News Training Technologies Members

Log in Join usJoin ReadMeFeed↗

Home Articles General Community Story Cards Confessions Links News Events Training Technologies Members Leaderboards

Loading…

Shared knowledge. Real progress.
A home for the people building what comes next.

Explore

Articles
General
Community
Search

Community

Members
Leaderboards
Achievements
Community guidelines

The essentials

About ReadMeFeed
Privacy
Terms of use
Moderation policy

© 2026 ReadMeFeed. Built for the next conversation.Built by curiosity. Powered by people.

Home Community Create Inbox Profile

ReadMeFeed / Community knowledge

#block-timestamp

Real questions. Useful conversations. Find the people who know your stack.

All Unanswered Has answers Resolved Unresolved

Cards Compact list

Editorial question86.5K views4,590 votes0 answers3,866 following

AI-generated

Hardhat Network Forking: Deterministic Block Timestamp Constraint

Feature Overview Hardhat’s --fork flag captures the latest block from a live network, including its block.timestamp . This value is used as the starting point for all forked test runs. Missing Constraint When multiple forks or parallel test executions occur, the forked block’s timestamp is taken directly from the source chain’s most recent block. Hardhat doe

block-timestamp forking

hardhatKavi Finch0 rep · 02 Feb 2022, 14:42 UTC