I'm looking to implement full message "forging" with no reliance on RPC calls. The P2P message doc does not cover all the details.

Let's say I have the JSON representation of parameters and code, how do I get that into proper hex? From that document, I'm looking to understand how to construct $scripted.contracts and $fitness.elem message parts.


1 Answer 1


The eztz.js library already does this - you need to convert raw code and parameters into Micheline and then encode Micheline into hex (eztz does it here https://github.com/TezTech/eztz/blob/master/src/main.js#L824)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.