7

There are eight types of costs: 1 Reading cost 2 Deserialization cost 3 Parsing cost 4 Type comparison cost 5 Interpreter cost 6 Unparsing cost 7 Serialization cost 8 Writng cost More documentation is available in this document https://gitlab.com/morley-framework/morley/-/blob/e2d3cf9197804a2cfa92715e1a4d640fe5b87af7/docs/...


6

Micheline is the concrete syntax of Michelson. https://tezos.gitlab.io/whitedoc/michelson.html The concrete syntax means that it is the part of language in which Michelson is actually written and doesn't deal with semantics (evaluation, etc.).


2

If we could do a logic schematics for this specific case, do you sirs think it could be described like this? : parameter (or (or (pair %addCustomer (pair (mutez %balance) (string %id)) (pair (string %name) (nat %phoneNumber))) (string %removeCustomer)) (or (pair %transfer (mutez %amount) (pair (string %idFrom) (string %idTo))) (pair %updateBalance (mutez %...


2

I fixed the problem just know, the thing here was that i didn't realize until i noticed how i was receiving the balance of the contract that i had to send the atomized value of the amount in tez. So basically the conversion is quite simple ... You want the atomized value: value(int/float) * 1 000 000 You want the int/float value instead of the atomized ...


1

This occured because the Michelson in the parameter was ill written and the fee was to low. So these were the changes i made to the function ... -Before: eztz.contract .send( "KT18qHvhEZUwiawA8QEURwuK8RGJj184725L", "tz1ddb9NMYHZi5UzPdzTZMYQQZoMub195zgv", keysextracted, 5, "RIGHT LEFT UNIT", 1000, 400000, 10000 ) -After: eztz.contract ...


1

Extracting an answer from the comments (kudos to @Klassare) That the private key (keysext.sk) is passed as an argument when eztz expects a keys object (keys = {pkh: string, sk: string, pk: string}) is one problem. Just pass the whole keys object instead. eztz.contract.send( "KT18qHvhEZUwiawA8QEURwuK8RGJj184725L", keysext.pkh, keysext, 5, "RIGHT LEFT UNIT", ...


1

There are two ways to indicate which entrypoint you want to call: call it by its name using the --entrypoint command-line argument of tezos-client transfer or the entrypoint optional parameter of the corresponding RPCs. If you do this, you can simply pass the argument of the expected entrypoint type without the leading Lefts and Rights. call it by its ...


1

You need to follow the path to the corresponding entry point in the Michelson parameter type. ‘Left’ when you go to the left branch of a ‘or’ and ‘Right’ for the right branch.


1

With PyTezos it would be (don't mind the naming, it is wrong, will be fixed at some point): >>> from pytezos.michelson.converter import micheline_to_michelson >>> print(micheline_to_michelson({'prim': 'pair', 'args': [{'string': 'hello'}, {'int': '42'}]})) pair "hello" 42


1

Edit: I realized that I misread the question and answered it for Michelson to Micheline when you wanted Micheline to Michelon. I do not know if there is a way to do that via the command line. Regardless, it would be nice to have both supported by the tezos-client tool. Michelson to Micheline It would be nice if there was a dedicated tezos-client command to ...


Only top voted, non community-wiki answers of a minimum length are eligible