[308] Clarification on Block Hash Usage in Transactions

[near-dx]

Title:
Clarification on Block Hash Usage in Transactions
Description:
The information could be improved.
The current block hash is not present in transaction for proving that it was created recently but rather for proving that we are running the right network. The same transaction could be taken from different network(testnet). To prove that somebody is not rerunning the transaction the recent block hash is used.
Summary:
Review feedback regarding block hash verification intent and update documentation to clarify its role in confirming network validation rather than transaction timing.

Info

Reported by: Guest (volodymyr.matselyukh@gmail.com) - Open in Gleap
Location: PL
Type: 🚨 BUG
Screenrecording link

🔗 Open share link
🌍 Open ticket in Gleap

Metadata

browserName: Chrome(133.0.0.0)
userAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36
browser: Chrome
systemName: MacOS
sessionDuration: 938
devicePixelRatio: 2
screenWidth: 1512
screenHeight: 982
innerWidth: 1512
innerHeight: 857
currentUrl: https://docs.near.org/integrations/create-transactions#constructing-the-transaction
language: en
sdkVersion: 13.7.3
sdkType: javascript
environment: prod

[near-dx]

Internal note 📝: Review feedback regarding block hash verification intent and update documentation to clarify its role in confirming network validation rather than transaction timing.