Module versionbits

Versionbits defines a finite-state-machine to deploy a softfork in multiple stages.

Structs

• Cache
  Signal state cache
• Deployment
  Struct for each individual consensus rule change using soft fork.
• Versionbits
  Struct Implements versionbits threshold logic, and caches results.
• VersionbitsCache
  RFC0000 allows multiple soft forks to be deployed in parallel. We cache per-epoch state for every one of them. */

Enums

• ActiveMode
  This is useful for testing, as it means tests don’t need to deal with the activation process. Only tests that specifically test the behaviour during activation cannot use this.
• DeploymentPos
  Soft fork deployment
• ThresholdState
  RFC0043 defines a finite-state-machine to deploy a soft fork in multiple stages. State transitions happen during epoch if conditions are met In case of reorg, transitions can go backward. Without transition, state is inherited between epochs. All blocks of a epoch share the same state.

Constants

• VERSIONBITS_NUM_BITS
  Total bits available for versionbits
• VERSIONBITS_TOP_BITS
  What bits to set in version for versionbits blocks
• VERSIONBITS_TOP_MASK
  What bitmask determines whether versionbits is in use

Traits

• VersionbitsConditionChecker
  Trait that implements versionbits threshold logic, and caches results.
• VersionbitsIndexer
  VersionbitsIndexer