diff options
| author | James O'Beirne <james.obeirne@pm.me> | 2022-03-09 12:37:19 -0500 |
|---|---|---|
| committer | James O'Beirne <james.obeirne@pm.me> | 2022-09-09 11:47:27 -0400 |
| commit | 00eeb31c7660e2c28f189f77a6905dee946ef408 (patch) | |
| tree | 9632e7eb98a9abf93706a7da1bd11910670a1da5 /doc/design | |
| parent | 37095c7dc4a85155c35e2473b6a20a53ae413cea (diff) | |
scripted-diff: rename CChainState -> Chainstate
-BEGIN VERIFY SCRIPT-
sed -i 's/CChainState/Chainstate/g' $(git grep -l CChainState ':(exclude)doc/release-notes*')
-END VERIFY SCRIPT-
Co-authored-by: MacroFake <falke.marco@gmail.com>
Diffstat (limited to 'doc/design')
| -rw-r--r-- | doc/design/assumeutxo.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/design/assumeutxo.md b/doc/design/assumeutxo.md index 2726cf779b..c353c78ff8 100644 --- a/doc/design/assumeutxo.md +++ b/doc/design/assumeutxo.md @@ -41,7 +41,7 @@ be of use. Chainstate within the system goes through a number of phases when UTXO snapshots are used, as managed by `ChainstateManager`. At various points there can be multiple -`CChainState` objects in existence to facilitate both maintaining the network tip and +`Chainstate` objects in existence to facilitate both maintaining the network tip and performing historical validation of the assumed-valid chain. It is worth noting that though there are multiple separate chainstates, those @@ -53,7 +53,7 @@ data. ### "Normal" operation via initial block download -`ChainstateManager` manages a single CChainState object, for which +`ChainstateManager` manages a single Chainstate object, for which `m_snapshot_blockhash` is null. This chainstate is (maybe obviously) considered active. This is the "traditional" mode of operation for bitcoind. |