6

The yellow paper describes the below block header structure:

enter image description here

This includes difficulty, beneficiary, mixHash and nonce values. Presumably these will be redundant under Proof-of-Stake. How will the Block Header structure change under proof of stake? Where is this defined? If it's to be confirmed, where/when is it likely to be confirmed.

  • 3
    This is an implementation detail, and I doubt anyone has bothered to commit to a PoS block header structure. I would certainly assume that it will not be the same. – Tjaden Hess Sep 8 '16 at 3:32
-1

This includes difficulty, beneficiary, mixHash and nonce values. Presumably these will be redundant under Proof-of-Stake.

Not necessary. The header (at least its structure) can be easily the same. Proof-of-Stake may only manage the block creation and confirmation (i.e. network synchronization/stabilization), without reformatting the block structure itself.

How will the Block Header structure change under proof of stake?

If you talking about Ethereum network, then only Ethereum team knows it.

Where is this defined? If it's to be confirmed, where/when is it likely to be confirmed.

Watch news on ethereum.org, what else...

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.