nimbus-eth1/nimbus/TODO-TRACER.md

The `handlers_tracer` driver from the `CoreDb` module needs to be re-factored.

This module will slightly change its work modus and will run as a genuine
logger. The previously available restore features were ill concieved, an
attempt to be as close as possible to the legacy tracer. If resoring is
desired the tracer will need to run inside a transaction (which it does
anyway.)
Aristo uses pre classified tree types (#2385) * Remove unused `merge()` functions (for production) details: Some functionality moved to test suite Make sure that only `AccountData` leaf type is exactly used on VertexID(1) * clean up payload type * Provide dedicated functions for merging accounts and storage trees why: Storage trees are always linked to an account, so there is no need for an application to fiddle about (e.e. creating, re-cycling) with storage tree vertex IDs. * CoreDb: Disable tracer functionality why: Must be updated to accommodate new/changed `Aristo` functions. * CoreDb: Use new `mergeXXX()` functions why: Makes explicit vertex ID management obsolete for creating new storage trees. * Remove `mergePayload()` and other cruft from API, `aristo_merge`, etc. * clean up merge functions details: The merge implementation `mergePayloadImpl()` does not need to be super generic anymore as all the edge cases are covered by the specialised functions `mergeAccountPayload()`, `mergeGenericData()`, and `mergeStorageData()`. * No tracer available at the moment, so disable offending tests 2024-06-18 11:14:02 +00:00			The `handlers_tracer` driver from the `CoreDb` module needs to be re-factored.

			`This module will slightly change its work modus and will run as a genuine`
			`logger. The previously available restore features were ill concieved, an`
			`attempt to be as close as possible to the legacy tracer. If resoring is`
			`desired the tracer will need to run inside a transaction (which it does`
			`anyway.)`