Author: shaolinfry 2017-03-12 15:47:28
Published on: 2017-03-12T15:47:28+00:00
The author of BIP9 has proposed an extension to the existing protocol that introduces an additional activation parameter for soft forks. The new parameter, called "activationtime", specifies a minimum median time past of a block at which the deployment should transition to the locked-in state. This allows full nodes to coordinate synchronized activation based on a median past time using the BIP9 state machine. The state transition workflow is the same as in BIP9 except when the activation time is greater than zero, in which case the workflow will be DEFINED -> STARTED -> PRE_LOCK_IN -> LOCKED_IN -> ACTIVE. The guidelines suggest setting the activation time to some date in the future and must be less than the BIP9 timeout. A living list of deployment proposals can be found on GitHub. An optional mandatory signaling function is also included in the reference implementation.
Updated on: 2023-06-11T21:54:57.208006+00:00