Add "full" and "none" indexing modes #112
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
n8maninger
force-pushed
the
nate/index-mode
branch
from
657df7d
to
a9db8b9
Compare
n8maninger
force-pushed
the
nate/index-mode
branch
from
884b7ac
to
dc8604d
Compare
ChrisSchinnerl
previously approved these changes
May 7, 2024
n8maninger
force-pushed
the
nate/index-mode
branch
from
39f573f
to
7a945d4
Compare
n8maninger
force-pushed
the
nate/index-mode
branch
from
146c2af
to
7a945d4
Compare
ChrisSchinnerl
approved these changes
May 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds "Full" and "None" indexing modes. The indexing mode can only be set once and cannot be changed since it changes how the state tree is stored.
"Partial" is the default. It only stores the state and events for addresses that are connected to a wallet.
"Full" will store the entire state of the blockchain regardless of addresses loaded into the wallet. It will also throw an error if the user attempts to trigger a scan with
/wallet/scan"None" will not process chain updates and treat the chain state as read-only. This isn't particularly useful now, but it will be nice when networked databases are supported.