New answers tagged michelson
1
The main benefit of big_maps with respect to maps is that the gas costs of big_map operations don't depend on the number of elements stored in the big_map.
Regarding storage size, when you store a key-value mapping in a big_map, you store the value but not the key; instead you store the hash of the key. This hash always takes exactly 32 bytes.
The rest of ...
2
big_map is extremely expensive. It allows you to put as much data as you want in the contract, but you end up paying more in counterpart.
Check this example:
It produces 2 identical contacts, one uses a map and the other uses a big map.
import smartpy as sp
class MyContract(sp.Contract):
def __init__(self, **kargs):
self.init(**kargs)
@sp....
1
You have visibly found a bug in the client typechecking command. Don't hesitate to open an issue for it on https://gitlab.com/tezos/tezos. I bet that the client is confused by the storage type of the inner script ({ parameter string ; storage string ; code { CAR ; NIL operation ; PAIR } }).
0
Found a solution! I am using in both contracts michelson_pairs for the type of the entrypoint. I also added some annotations
For example:
type transfer is michelson_pair(bytes, "args1", michelson_pair(string, "args2", string, "args3"),"")
I just removed the annotations:
type transfer is michelson_pair(bytes, "&...
Top 50 recent answers are included
