Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update BlockHashCount in Transaction Mortality section #4309

Merged
merged 2 commits into from
Jan 16, 2023
Merged

Update BlockHashCount in Transaction Mortality section #4309

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bfffae6
Updated the BlockHashCount
Imod7 Jan 16, 2023
d10470a
Fetching value from chain
Imod7 Jan 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/build/build-protocol-info.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -203,8 +203,8 @@ valid. If the extrinsic is not included in a block within this validity window,
from the transaction queue.

The chain only stores a limited number of prior block hashes as reference. You can query this
parameter, called `BlockHashCount`, from the chain state or metadata. This parameter is set to 2400
blocks (about four hours) at genesis. If the validity period is larger than the number of blocks
parameter, called `BlockHashCount`, from the chain state or metadata. This parameter is set to {{ polkadot: <RPC network="polkadot" path="consts.system.blockHashCount" defaultValue={4096}/> :polkadot }}
blocks (about seven hours) at genesis. If the validity period is larger than the number of blocks
stored on-chain, then the transaction will only be valid as long as there is a block to check it
against, i.e. the minimum value of validity period and block hash count.

Expand Down