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.

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

moves content to transactions page #101

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
33 changes: 32 additions & 1 deletion polkadot-protocol/basics/blocks-transactions-fees/blocks.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,35 @@
---
title: Blocks
description: TODO
---
---
<!--######This is a WIP page#######-->

<!--
# Blocks

## Introduction



## What is a Block?

In the Polkadot SDK, a block consists of a header and an array of transactions. The header contains the following properties:

- **Block height** - the number of blocks that have been created in the chain
- **Parent hash** - the hash of the previous block in the chain
- **Transaction root** - a cryptographic digest of the transactions in the block
- **State root** - a cryptographic digest of the state after executing the transactions
- **Digest** - a list of additional information that can be included in the block

All transactions are bundled together as a series to be executed as defined in the runtime. You'll learn more about transaction ordering in the [Transactions Lifecycle](/polkadot-protocol/protocol-components/transactions/transactions-lifecycle/){target=\_blank} documentation. The transaction root is a cryptographic digest of this series. This cryptographic digest serves two purposes:

- It prevents any alterations to the series of transactions after the header has been built and distributed
- It enables light clients to succinctly verify that any given transaction exists in a block given only knowledge of the header

## Where to Go Next

Now that you are familiar with the information that constitutes a block, you can explore the following topics to learn more:

- [**Block reference**](https://paritytech.github.io/polkadot-sdk/master/sp_runtime/traits/trait.Block.html){target=\_blank} - learn more about the block structure in the Polkadot SDK runtime

-->
257 changes: 255 additions & 2 deletions polkadot-protocol/basics/blocks-transactions-fees/transactions.md

Large diffs are not rendered by default.

This file was deleted.

This file was deleted.

Loading