Amaru - Demo content discussion MoM (17th June)

[Dam-CZ]

What already works (and can be demoed)

• Preprod OK; Preview implementation ongoing (protocol parameters check) and mainnet soon tm - Julien
• Running simulation in Rust: What traces? - Stevan/Arnaud

Showcase the scope of the simulation and showing what we can do with the current environment
Like get a bug inside the pipeline and find it out
Chain selection unwired > can introduce a bug there

What requires a bit of effort

• Making "golden test vectors" reusable for any nodes > make sure it's standardized > Joshy presenting (work done by Ethan)

One way of testing shared across all nodes
Canonical ledger state representation

• Version of the node that displays the ledger rules (with a checkmark of what passes) "hey here we are" - Joshy / Simon / Matthias

Make a sexy statement about "this is where we are, and we know what's left" show the validations DONE and NOT DONE
Show the traces and how we are able to analyze (comprehensible traces for showcasing what happens), find gaps and help with the overall progress of the other "interfaced scopes"
Check validation time and knowing how the time spent is spread across the "stage" (parsing, validation, context creation, storage)
Show what we have and the parameters that come together
Jaeger + Anchor points + showcase buildup

• Show 1st a waterfall for a single node (show all the piece put together) - Arnaud

Connect X Amaru nodes together (yeay) Disclaimer: networking: node to node static topology
Highlight a trace that demonstrates the adoption time across nodes
With standardized tracing you can use a tool to correlate sync time across node
Use Amaru to power other services (going through Dolos for example)
Connecting Dolos & Amaru > with Santi (Treasury portal (dashboard) powered by Dolos > pointing to an Amaru node?)

• Overview of "things to measure" from running an Amaru node (SPOs feedback)

Show a first taste of it: Prometheus & Jaeger should have the info (wiring the metrics with the sources)

• Storing block on disk? > can we show improvements based on this? (RAM? CPU? Time to sync?)

Has to be done in specific epochs (disclaimer of the boundaries of the demo)
If we fix, no need to disclaim

Bonus: compiling Amaru into a docker Image (the environment of the demo)

For next demo?

• Ledger: Governance actions ratification (state of the rules necessary, stake management),

• Transaction validation debugger with visual troubleshooting tool (graphic version of debugging)

• How to we reference issues / bugs ?

Staying alive timing: identify the transactions that crashes and see how we can work around or solve it
Example: Memory leak because we have only specific epochs we cover

• Amaru doctor?

• Release content disclaimer

• Rule level traces viewable ?