Page Comparison

Resources

• Validator Incentives and Casper

Paragraph 2Discussion about time: wall clock and block times

• Concern proposing at any time is a major DoS attack vector

• Notion of time

  • A notion of time is a way to mitigate against some attacks (ex long-range attacks relying on social coordination)

  • Ways to create a sense of time

    • Simulated time based on number of blocks

    • Simulated time based on accumulated REV

    • Polkadot approach

    • Non-empty block (as described in paragraph 2)

  • Idea that
    

• • Should we assume we are going to layer in a notion of time?

    • It is a desired property of the system is that we have a stable sense of block time

      • Mitigates some attack vectors

      • Benefits users who want to know when to anticipate the next block

      • Current protocol doesn’t guarantee or incentivize this

    • DECISION - yes, we agree we need a notion of time

      • Recommendation to implement a time slot approach to validation instead of a validator can propose at any time (Phil)

      • Concern this may take more implementation effort than we can afford at the moment (Kent)

• Suggestion: Could we add a constraint that validators must allow another validator to propose to prevent a single validator filling up an epoch?

• What is the maximum block size a validator can propose?

  • TODO we need to pick this (see action item below)