-
Notifications
You must be signed in to change notification settings - Fork 19
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
Parachain Development - Section One #110
Conversation
When we refer to blocks being stored, it almost **always** meaning that the **header** of the block is stored. Doing so would cause a lot of on-chain bloat, especially considering the state of other parachains, where each parachain may have varying amounts of data per block. | ||
|
||
The same goes for parablocks within relay chain blocks - it's **paraheaders** being stored within the relay chain block, not the actual state transition themselves. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not exactly. Relaychain stores candidate receipts https://medium.com/polkadot-network/the-path-of-a-parachain-block-47d05765d7a
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, interesting discussion here https://forum.polkadot.network/t/pre-rfc-discussion-candidate-receipt-format-v2/3738/7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I can add more detail on the PoV in a separate PR, it could be a very valuable reading for the developer!
Section one of the intro to Parachain development guide: #107