@@ -95,10 +95,10 @@ function nft_transfer(
95
95
// purposes
96
96
// * Contract MUST panic if called by someone other than token owner or,
97
97
// if using Approval Management, one of the approved accounts
98
- // * The receiving contract must implement `ft_on_transfer ` according to the
99
- // standard. If it does not, FT contract's `ft_resolve_transfer ` MUST deal
98
+ // * The receiving contract must implement `nft_on_transfer ` according to the
99
+ // standard. If it does not, FT contract's `nft_resolve_transfer ` MUST deal
100
100
// with the resulting failed cross-contract call and roll back the transfer.
101
- // * Contract MUST implement the behavior described in `ft_resolve_transfer `
101
+ // * Contract MUST implement the behavior described in `nft_resolve_transfer `
102
102
// * `approval_id` is for use with Approval Management extension, see
103
103
// that document for full explanation.
104
104
// * If using Approval Management, contract MUST nullify approved accounts on
@@ -153,9 +153,9 @@ The following behavior is required, but contract authors may name this function
153
153
// `sender_id`
154
154
//
155
155
// Arguments:
156
- // * `sender_id`: the sender of `ft_transfer_call `
157
- // * `receiver_id`: the `receiver_id` argument given to `ft_transfer_call `
158
- // * `token_id`: the `token_id` argument given to `ft_transfer_call `
156
+ // * `sender_id`: the sender of `nft_transfer_call `
157
+ // * `receiver_id`: the `receiver_id` argument given to `nft_transfer_call `
158
+ // * `token_id`: the `token_id` argument given to `nft_transfer_call `
159
159
// * `approved_token_ids`: if using Approval Management, contract MUST provide
160
160
// set of original approved accounts in this argument, and restore these
161
161
// approved accounts in case of revert.
0 commit comments