PIP-14: Increase Checkpoint Buffer Time

Polygon Improvement Proposals Canonical PIPs
1

Authors:

Vaibhav Jindal

Type: Core

Table of Contents:

  • Abstract
  • Motivation
  • Specification
  • Security Considerations
  • Backward Compatibility
  • Copyright
  • Abstract

This proposal describes a change to the value of the ‘Checkpoint Buffer Time’ in Heimdall, from 1000 seconds to 1500 seconds.

Currently the parameter ‘Checkpoint Buffer Time’ is used at the following two places:

  1. In the handler of ‘Checkpoint Msg’, where it checks whether ‘Checkpoint Buffer Time’ has passed since the last buffered checkpoint (if the buffered checkpoint exists), and;
  2. In the handler of ‘No Ack ‘, where it checks whether ‘Checkpoint Buffer Time’ has passed since the last stored checkpoint.

Motivation

Following ‘the Merge’ on the checkpoint rootchain (Ethereum), transaction finality time increased from approx 750 seconds to 1150 seconds. This delayed the average time between each checkpoint on Polygon PoS, commensurate with this increased delay in finality on Ethereum.

The proposed change will bring the ‘Checkpoint Buffer Time’ in line with the current average time between checkpoints.

We propose to execute this change via the Heimdall Governance Module, which would avoid the coordination overhead associated with hard forking the chain.

Specification

        {
            "subspace": "checkpoint",
            "key": "CheckpointBufferTime",
            "value": "1500000000000"
        }

Backward Compatibility

This PIP will not be backward compatible with the current implementation of Bor and Heimdall. It would therefore require a hard fork, or, synchronous upgrade via the Heimdall Governance Module.

Copyright

All copyrights and related rights in this work are waived under CC0 1.0 Universal.

4 Likes