documentation of tx simulate #119
Description
What is your idea? Provide a use case.
I think this is already part of the Q2 roadmap, but.
The form of the two other input files of aiken tx simulate are, afaics, undocumented.
My idea is that they should be documented, and perhaps a more human way to generate them.
Why is it a good idea?
Its a really cool tool. Especially with aiken-lang/aiken#1158
Be nice to know how to use it
Acceptance test 123 doesn't give too much away
What is the current alternative and why is it not good enough?
Reading the source code, and handcrafting cborhex