Tezos.get_entrypoint_opt in Ligo issue

It depends on the "x"

let's say "x" is a variant (or (or (int %decrement) (unit %default)) (int %increment)) which represents entrypoints of the targeted contract.

• get_contract({address}) returns a contract(x)
• get_entrypoint_opt("%increment", {address}) returns a optional(contract(int))

Using get_entrypoint_opt function one must specify only the type of the parameter of the specified entrypoint (and not the parameter of the contract). Actually, it ensures that the contract at the given address possess an well-named entrypoint and with the expected type.

So I would say: replace the x by the right type. Find out what is expected by the entrypoint Transfer (i.e. Transfer of ...) ... I guess it must be (address * address * mutez) or in a record format .

I hope it helps

I think the entrypoint is well written ("%transfer") because if you look the generated Michelson code, the entrypoint annotations start with a low-case letter.

get_entrypoint_opt Ligo function is equivalent to CONTRACT %transfer {targeted_contract_entrypoints} in Michelson. And I reproduced this bug with a small michelson script like this one.

parameter address ;
storage bool;
code { CAR ;
       CONTRACT %increment (or (int %decrement) (int %increment)) ;
       IF_NONE { PUSH bool False } { DROP; PUSH bool True };
       NIL operation ;
       PAIR }

Notice that if you use get_contract_opt instead of get_entrypoint_opt then it generates an CONTRACT instruction without annotation.

CONTRACT  (or (int %decrement) (int %increment)) ;

and it works.

In LIGO entrypoint name corresponds to your router enum value types, not function names. So "Transfer" should start with uppercase letter.

In you case you should call it as follows: Tezos.get_entrypoint_opt("%Transfer", s.tokenAddress)