Expand description
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.
- Versionbits
Cache - RFC0000 allows multiple soft forks to be deployed in parallel. We cache per-epoch state for every one of them. */
Enums§
- Active
Mode - 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.
- Deployment
Pos - Soft fork deployment
- Threshold
State - 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§
- Versionbits
Condition Checker - Trait that implements versionbits threshold logic, and caches results.
- Versionbits
Indexer - VersionbitsIndexer