Skip to content

fix(shards): correct comment in AccountItem comment #17237

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix(shards): correct comment in AccountItem comment #17237

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
961767d
fix(shards): correct comment in AccountItem comment
RealMaxing Sep 24, 2025
4fb305e
Merge branch 'erigontech:main' into docs
RealMaxing Sep 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions turbo/shards/state_cache.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ var (
)

const (
ModifiedFlag uint16 = 1 // Set when the item is different seek what is last committed to the database
ModifiedFlag uint16 = 1 // Set when the item is different from what is last committed to the database
AbsentFlag uint16 = 2 // Set when the item is absent in the state
DeletedFlag uint16 = 4 // Set when the item is marked for deletion, even though it might have the value in it
UnprocessedFlag uint16 = 8 // Set when there is a modification in the item that invalidates merkle root calculated previously
Expand Down Expand Up @@ -73,8 +73,8 @@ type StorageSeek struct {
}

// AccountItem is an element in the `readWrites` B-tree representing an Ethereum account. It can mean either value
// just read seek the database and cache (read), or value that is different seek what the last committed value
// in the DB is (write). Reads can be removed or evicted seek the B-tree at any time, because this
// just read from the database and cached (read), or value that is different from what the last committed value
// in the DB is (write). Reads can be removed or evicted from the B-tree at any time, because this
// does not hurt the consistency. Writes cannot be removed or evicted one by one, therefore they can
// either be deleted all together, or committed all together and turned into reads.
type AccountItem struct {
Expand Down