Background

Right now users have to call ft_transfer_call through the near contracts flow. For example:

$ near contract call-function as-transaction wrap.testnet ft_transfer_call file-args ft_transfer_call.json prepaid-gas '100.0 Tgas' attached-deposit '1 yoctoNEAR' sign-as frolik.testnet network-config testnet sign-with-keychain send

We can probably simplify it to:

$ near tokens frolik.testnet send-ft-call wrap.testnet omni.n-bridge.testnet '1 wNear' memo '' msg '{\"recipient\":\"base:0xCF6462b9fcE5aF3E6c660c83453ECa18Ff468773\",\"fee\":\"0\",\"native_token_fee\":\"0\"}' network-config testnet sign-with-keychain send

msg field should be provided as a string, but maybe adding file-args option just like in contract call-function as-transaction flow is a good idea

User Story

Users who often send ft_transfer_calls (e.g to bridge tokens) might need this feature

Acceptance Criteria

Supported ft_transfer_call call in tokens subcommand that matches the flow specified in Background section

Resources & Additional Notes

https://github.com/near/NEPs/blob/master/neps/nep-0141.md#ft_transfer_call