Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds enough pieces for a (fake) end-to-end execution of the test V-App in Vanadium.
The new
common
crate will contain any common code that should be shared between the Vanadium VM and the V-App client SDK. For example, I added there the stub of theManifest
, copied from vanadium_legacy.I added two commands to the VM:
register_vapp
: gets a manifest, and returns an hmac, that for now it's conveniently always[0x42; 32]
.start_vapp
: gets a Manifest, and actually start the execution of the app. Since there is no VM, all instructions are treated as NOP, so for now it keeps moving through the code segment until it overflows and crashes :)host
is a temporary, standalone crate to make the e2e execution work. It contains the logic to parse the elf file of thetest
app, and act as the counterparty of the VM by interpreting the client commands (GET_PAGE, COMMIT_PAGE; only GET_PAGE is implemented for now, and without Merkle proofs)Also added a basic CI workflow to run the tests for the crates that can be compiled for the
x86_64-unknown-linux-gnu
target.