cache data tries between blocks

[BeniaminDrasovean]

Reasoning behind the pull request

Proposed changes

Testing procedure

Pre-requisites

Based on the Contributing Guidelines the PR author and the reviewers must check the following requirements are met:

• was the PR targeted to the correct branch?
• if this is a larger feature that probably needs more than one PR, is there a feat branch created?
• if this is a feat branch merging, do all satellite projects have a proper tag inside go.mod?

[Copilot]

Pull request overview

This PR aims to cache account data tries across block commits by avoiding full resets of the data-tries holder and instead tracking which cached tries were modified (“dirty”) between commits.

Changes:

• Extend common.TriesHolder with a MarkAsDirty([]byte) method to explicitly flag cached tries as modified.
• Update AccountsDB.saveDataTrie to mark an already-cached trie as dirty instead of re-inserting it, and stop resetting dataTries during commit().
• Enhance dataTriesHolder to support MarkAsDirty and add additional trace logging around cache/eviction behavior.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
testscommon/trie/triesHolderStub.go	Adds MarkAsDirty to the test stub.
state/triesHolder/triesHolder.go	Adds no-op MarkAsDirty for the simple holder implementation.
state/triesHolder/dataTriesHolder.go	Implements MarkAsDirty and adds trace logs for cache operations/evictions.
state/accountsDB.go	Marks cached data tries as dirty and keeps cached tries across commits.
common/interface.go	Extends TriesHolder interface with MarkAsDirty.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.