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
Run simulations for different orders of magnitude of throughput scenarios, providing network and CPU usage events and/or metrics useful for calculating running node costs. Compare data to the high-level cost estimator tool.
Demonstrate adherence to the Short Leios protocol, also with the help of the formal specification.
Within reason, incorporate new protocol variations from research workstream.
We believe the next two would be valuable goals, but we would like some feedback 📢
Document mini-protocols design and solicit review from the Cardano Networking team.
Build confidence in simulation results by comparison to an idealized diffusion model: we would see how close the simulation gets by disabling features the model ignores, and then measure the impact of re-enabling each feature.
Definition of done
Numbered to match the goals:
Simulation trace contains events for the CPU usages of interest (cryptography operations and block validation) as specified in configuration, and also events for messages exchanged between nodes.
Simulation trace contains Node activity events that can be compared to the state transitions of the formal specification, and conformance can be demonstrated through analysis and/or testing.
Ongoing task.
Draft of technical report comparable to mini-protocols section of the report for the current cardano-node.
Written report describing the idealized diffusion model and the sources of discrepancy with the simulation.
The text was updated successfully, but these errors were encountered:
Saizan
changed the title
Generation of Node Resource Usage Data from Validated Haskell Prototype
Generation of Leios node resource usage data from validated Haskell prototype
Jan 20, 2025
This sounds like a very sensible and valuable approach. Creating idealised models helps with general socialisation as well as establishing reasonable 'stretch goals' during development.
Sharing the mini-protocols with the network team would be a good source of peer review
Goals
We believe the next two would be valuable goals, but we would like some feedback 📢
Definition of done
Numbered to match the goals:
The text was updated successfully, but these errors were encountered: