add polkatool jam-service support #176
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Rather than hand assemble https://gist.github.com/sourabhniyogi/5e44600216af117169384a51ab389c8d we would like to demonstrate how a JAM service written in Rust using #[polkavm_import(index = 0)] can be compiled into JAM-ready PVM and include "ecalli {0..22}" calls; By "JAM-ready" we mean the "0/5/10/15" entry points for is_authorized/refine/accumulate/transfer. TODO: (1) Get toolchain instructions sufficient to get above Rust compiled into PVM with (a) ecalli 16/17/3 in place of import/export (refine) + write (accumulate) (b) entrypoints 0/5/10/15 going into is_authorized/refine/accumulate/on_transfer (2) get polkatool to output .pvm byte code with (1b) streamlined
sourabhniyogi
force-pushed
the
jamfib
branch
from
001755e
to
bbf4c11
Compare
|
@koute Thank you for your super friendly and critically useful hints! Based on your advice, we successfully built a "polkatool jam-service" to take a "cargo build" compiled Rust JAM Service like We added a README showing the steps and the disassembly. We will build a small battery of actually useful services to test this out further, covering many of the other host functions. To make these JAM Services into JAM-ready toplevel service blobs (as defined in equation 241 in A.7 in GP v0.3.8) we will prepend a header in |
sourabhniyogi
changed the title
sourabhniyogi
force-pushed
the
jamfib
branch
from
bbf4c11
to
57b9bcf
Compare
Sample execution: (after cargo build of jam-service-fib) ./target/release/polkatool jam-service ~/polkavm/guest-programs/jam-service-fib/target/riscv32ema-unknown-none-elf/release/jam-service-fib
sourabhniyogi
force-pushed
the
jamfib
branch
from
57b9bcf
to
706c34a
Compare
sourabhniyogi
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 WIP PR sets up:
refine(entry point 5) imports a 12-byte segment with [n, fib(n), f(n-1)] and exports the next segment in the same way [n+1, fib(n+1), fib(n)].accumulate(entry point 10) reads a 12-byte segment and writes to service storage key "0"is_authorized(entry point 0) andon_transfer(entry point 15) are just stubs right nowpolkatool jam_service [binary]to run @koute recommended code/approach to be "JAM-ready". By "JAM-ready" we mean having the "0/5/10/15" entry points for is_authorized/refine/accumulate/transfer.Rather than hand assemble PVM byte code like this using @koute's assembler we would much rather use Rust. The sample code includes a first attempt to get at 23 functions from GP Appendix B and teases a few others.