feat: state.SnapshotTree
interface for drop-in replacement
#77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why this should be merged
Allows for a drop-in replacement of
snapshot.Tree
(i.e. one that uses block hashes instead of state roots). This is intended as a temporary solution while we investigate having the state root affected by the block hash to remove path ambiguity.How this works
Introduction of:
state.SnapshotTree
interface to match methods required onsnapshot.Tree
as used bystate.StateDB
; andstateconf
package for variadic options plumbed byStateDB.Commit()
through toSnapshotTree.Update()
.Although variadic (to maintain function call-signature compatibility) only the
stateconf.WithUpdatePayload(any)
is expected to be used. Recipients of the options can access the payload withstateconf.ExtractUpdatePayload()
.How this was tested
Unit test demonstrating propagation of
stateconf.UpdateOption
payload.