transfer
instruction is used to transfer Tezis to an account.coder
is a role
variable.transfer
instruction. Say for example you want to call the add_value
entry point of the following contract:transfer ... to ... call ...
instruction:c
does not provide an entry point annotated %add_value
my_add_value
entry point; it is possible to call it from another entry point with the following instruction:getter
keyword used to declare an entry point to the contract called "getBar"; the Michelson version of this entry actually takes a callback function (a setter) used to set/use the bar
value in another contract. It is syntactic sugar equivalent to the following entry declaration:contract
type is used to declare the callback type; it is parametrized by the signature of the callback, represented as the tuple of argument types.getter
and entry
versions of the getBar
entry above is that the callback argument is anonymous in the getter
version.entrypoint
function may be used to build a contract
value from the name and the address. It returns an option value of contract type, so that it is possible to handle the case when the entry point does not exist.require_entrypoint
function builds a contract and fails with error message if contract is invalid. The above inspector contract may be rewritten as:view
keyword to declare such a view; as for entry points, views may have arguments. Use the return
keyword to return any value to the calling contract.callview
operator to call a contract view; parameters are:< ... >
getValueMby2
defined above:callview
returns an option of value that requires to be handled. It returns none
when:articles
for a presentation.event
keyword declaration. An event may possess several fields, like a record.HighestBidIncreased
event with two fields bidder
and amount
:event
operation
big_map
asset
contract
ticket
sapling_state
emit
instruction to emit an event: