You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
Instead of storing the value to the DB, allow node operators to just store the length of the value (minimum needed for block execution) for keys/prefixes they don't care about.
This allows for very lightweight running of nodes and/or just consensus nodes.
This mode should also delete historical blocks (if the rpcchainvm supports this).
We could also change the canonical form of the block to not actually include values. Instead, they could be attached and fetched separately for anyone that wants to validate their correctness/serve data.
The text was updated successfully, but these errors were encountered:
After #40, we only store the minimum required amount of data to serve block queries. If we want to serve any less, it will require changes in AvalancheGo that allow a node to specify it doesn't have a certain range of blocks.
Instead of storing the value to the DB, allow node operators to just store the length of the value (minimum needed for block execution) for keys/prefixes they don't care about.
This allows for very lightweight running of nodes and/or just consensus nodes.
This mode should also delete historical blocks (if the
rpcchainvm
supports this).We could also change the canonical form of the block to not actually include values. Instead, they could be attached and fetched separately for anyone that wants to validate their correctness/serve data.
The text was updated successfully, but these errors were encountered: