forked from paradigmxyz/cryo
-
Notifications
You must be signed in to change notification settings - Fork 0
P1-3: alloy migration — trace-type datasets #19
Copy link
Copy link
Closed
Labels
area/freezecryo_freeze cratecryo_freeze cratephase/1Dependency ModernizationDependency Modernizationsize/lLarge taskLarge taskstatus/blockedBlocked by a dependencyBlocked by a dependencytype/choreMaintenance, tooling, housekeepingMaintenance, tooling, housekeeping
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
area/freezecryo_freeze cratecryo_freeze cratephase/1Dependency ModernizationDependency Modernizationsize/lLarge taskLarge taskstatus/blockedBlocked by a dependencyBlocked by a dependencytype/choreMaintenance, tooling, housekeepingMaintenance, tooling, housekeeping
Roadmap task
P1-3
Problem
The trace-handling datasets use alloy trace types (
rpc::types::trace::parity/geth), which changed structurally across alloy 0.6 -> 1.x. This is the non-trivial cluster of the migration.Affected files
crates/freeze/src/datasets/:traces.rs,trace_calls.rs,contracts.rs,storage_diffs.rs,code_diffs.rs,balance_diffs.rs,vm_traces.rs,geth_*.rscrates/freeze/src/multi_datasets/as neededAcceptance criteria
cryo_testdiff vs the P1-0 baseline is empty for each affected datatype.Validation method
cargo build+cryo_testper-datatype diff against the P1-0 baseline.References & credit
ROADMAP P1-3. Depends on P1-1. References: upstream PR paradigmxyz#244 (@clouds56), paradigmxyz#240 (@mattsse).