Open hjorthjort opened 3 years ago
Focus now: finish the semantics/clean up, be able to run basic tests, produce reports. Update the elrond-wasm-rs dependency.
Next step: investigate source mapping. What can we do, how well do existing source mapping tools work for our purposes.
2021-02-09
Completed
finish
andsignalError
for ending callsIssues:
Memory problem
Semantics can't build, require too much time an memory. Likely due to configuration compostions.
Actions:
Discussion
What are next steps? What would be cool tools.
Everyone agree that symbolic execution, verification, and automatic test case generation would all be great. They are long-term, though.
Andrei suggested we should plug ElrondWasm into their regular CI when it's done, to test Arwen against the K semantics.
We could also make the Elrond semantics a more complete documentation document, like the jello paper.
Once we can generate a report for the Multisig contract we will give that to @virgil-serbanuta and other devs on the Elrond side for feedback and ideas on how it should become more useful.
Right now, the default approach is: