Return to Answer

"Skip-block" isn't mentioned in any Ethereum specifications or documentation.

Basically the only reference to it is the sole article mentioned in the question. What the article means by a "skip-block" is an empty/skipped slot.

At each slot, an optimal validator will always make an attestation. If it sees a block for the slot, it will attest to that block. If the validator does not see or receive the block in time, it should make an attestation that the slot is empty/skipped: it does this by attesting to the last block it has seen. For example for Slot 1 and 2, a validator attesting to block B for both slots, implies that the validator did not see a block for Slot 2.

A slot can be skipped for various reasons. For example, the block proposer for the slot may be offline. Or the block proposer waited too long before broadcasting the block to the network. Or the block that was proposed took too long to reach a majority of the validators that attested for that slot.

"Skip-block" isn't mentioned in any Ethereum specifications or documentation.

Basically the only reference to it is the sole article mentioned in the question. What the article means by a "skip-block" is an empty/skipped slot.

Each slot has a committee of validators assigned to attest to that slot. At each slot, an optimal validator (in the committee) will always make an attestation. If it sees a block for the slot, it will attest to that block. If the validator does not see or receive the block in time, it should make an attestation that the slot is empty/skipped: it does this by attesting to the block it thinks is the head of the chain.

A slot can be skipped for various reasons. For example, the block proposer for the slot may be offline. Or the block proposer waited too long before broadcasting the block to the network. Or the block that was proposed took too long to reach a majority of the committee validators that attested for that slot.

"Skip-block" isn't mentioned in any Ethereum specifications or documentation.

Basically the only reference to it is the sole article mentioned in the question. What the article means by a "skip-block" is an empty/skipped slot.

At each slot, an optimal validator will always make an attestation. If it sees a block for the slot, it will attest to that block. If the validator does not see or receive the block in time, it should make an attestation that the slot is empty/skipped: a so-called "skip-block".

A slot can be skipped for various reasons. For example, the block proposer for the slot may be offline. Or the block proposer waited too long before broadcasting the block to the network. Or the block that was proposed took too long to reach a majority of the validators that attested for that slot.

The article does explain:

Moreover, if for a given slot a validator didn’t see the block being produced, or the block was produced on a chain that the validator doesn’t see as the current chain, the validator is encouraged to attest to a so-called “skip-block”. This way an honest validator is expected to attest to exactly one block each time slot, either the actual block produced by a proposer, or a “skip-block”.

...

If an attester doesn’t receive a block for a particular slot, they attest to a skip-block for that time slot. It is up for the attester to decide how far into the time slot they wait until they decide to stop waiting for the block and attest to the skip block.

"Skip-block" isn't mentioned in any Ethereum specifications or documentation.

Basically the only reference to it is the sole article mentioned in the question. What the article means by a "skip-block" is an empty/skipped slot.

At each slot, an optimal validator will always make an attestation. If it sees a block for the slot, it will attest to that block. If the validator does not see or receive the block in time, it should make an attestation that the slot is empty/skipped: it does this by attesting to the last block it has seen. For example for Slot 1 and 2, a validator attesting to block B for both slots, implies that the validator did not see a block for Slot 2.

A slot can be skipped for various reasons. For example, the block proposer for the slot may be offline. Or the block proposer waited too long before broadcasting the block to the network. Or the block that was proposed took too long to reach a majority of the validators that attested for that slot.

"Skip-block" isn't mentioned in any Ethereum specifications or documentation.

Basically the only reference to it is the sole article mentioned in the question. What the article means by a "skip-block" is an empty/skipped slot.

At each slot, an optimal validator will always make an attestation. If it sees a block for the slot, it will attest to that block. If the validator does not see or receive the block in time, it should make an attestation that the slot is empty/skipped: a so-called "skip-block".

The article does explain:

Moreover, if for a given slot a validator didn’t see the block being produced, or the block was produced on a chain that the validator doesn’t see as the current chain, the validator is encouraged to attest to a so-called “skip-block”. This way an honest validator is expected to attest to exactly one block each time slot, either the actual block produced by a proposer, or a “skip-block”.

...

If an attester doesn’t receive a block for a particular slot, they attest to a skip-block for that time slot. It is up for the attester to decide how far into the time slot they wait until they decide to stop waiting for the block and attest to the skip block.

"Skip-block" isn't mentioned in any Ethereum specifications or documentation.

Basically the only reference to it is the sole article mentioned in the question. What the article means by a "skip-block" is an empty/skipped slot.

At each slot, an optimal validator will always make an attestation. If it sees a block for the slot, it will attest to that block. If the validator does not see or receive the block in time, it should make an attestation that the slot is empty/skipped: a so-called "skip-block".

A slot can be skipped for various reasons. For example, the block proposer for the slot may be offline. Or the block proposer waited too long before broadcasting the block to the network. Or the block that was proposed took too long to reach a majority of the validators that attested for that slot.

The article does explain:

Moreover, if for a given slot a validator didn’t see the block being produced, or the block was produced on a chain that the validator doesn’t see as the current chain, the validator is encouraged to attest to a so-called “skip-block”. This way an honest validator is expected to attest to exactly one block each time slot, either the actual block produced by a proposer, or a “skip-block”.

...

If an attester doesn’t receive a block for a particular slot, they attest to a skip-block for that time slot. It is up for the attester to decide how far into the time slot they wait until they decide to stop waiting for the block and attest to the skip block.