Caller of the method must attach a deposit of at least 1 yoctoⓃ for
security purposes
Contract MAY require caller to attach larger deposit, to cover cost of
storing approver data
Contract MUST panic if called by someone other than token owner
Contract MUST panic if addition would cause nft_revoke_all to exceed
single-block gas limit
Contract MUST increment approval ID even if re-approving an account
If successfully approved or if had already been approved, and if msg is
present, contract MUST call nft_on_approve on account_id. See
nft_on_approve description below for details.
Arguments:
token_id: the token for which to add an approval
account_id: the account to add to approvals
msg: optional string to be passed to nft_on_approve
Returns void, if no msg given. Otherwise, returns promise call to
nft_on_approve, which can resolve with whatever it wants.
Caller of the method must attach a deposit of at least 1 yoctoⓃ for
security purposes
Contract MAY require caller to attach larger deposit, to cover cost of
storing approver data
Contract MUST panic if called by someone other than token owner
Contract MUST panic if addition would cause nft_revoke_all to exceed
single-block gas limit
Contract MUST increment approval ID even if re-approving an account
If successfully approved or if had already been approved, and if msg is
present, contract MUST call nft_on_approve on account_id. See
nft_on_approve description below for details.
Arguments:
token_id: the token for which to add an approval
account_id: the account to add to approvals
msg: optional string to be passed to nft_on_approve
Returns void, if no msg given. Otherwise, returns promise call to
nft_on_approve, which can resolve with whatever it wants.
Caller of the method must attach a deposit of at least 1 yoctoⓃ for
security purposes
Contract MAY require caller to attach larger deposit, to cover cost of
storing approver data
Contract MUST panic if called by someone other than token owner
Contract MUST panic if addition would cause nft_revoke_all to exceed
single-block gas limit
Contract MUST increment approval ID even if re-approving an account
If successfully approved or if had already been approved, and if msg is
present, contract MUST call nft_on_approve on account_id. See
nft_on_approve description below for details.
Arguments:
token_id: the token for which to add an approval
account_id: the account to add to approvals
msg: optional string to be passed to nft_on_approve
Returns void, if no msg given. Otherwise, returns promise call to
nft_on_approve, which can resolve with whatever it wants.
Check if a token is approved for transfer by a given account, optionally
checking an approval_id
Arguments:
token_id: the token for which to revoke an approval
approved_account_id: the account to check the existence of in approvals
approval_id: an optional approval ID to check against current approval ID for given account
Returns:
if approval_id given, true if approved_account_id is approved with given approval_id
otherwise, true if approved_account_id is in list of approved accounts
Returns the number of non-fungible tokens owned by given account_id as
a string representing the value as an unsigned 128-bit integer to avoid JSON
number limit of 2^53.
receiver_id: the valid NEAR account receiving the token
token_id: the token to transfer
approval_id: expected approval ID. A number smaller than
2^53, and therefore representable as JSON. See Approval Management
standard for full explanation.
memo (optional): for use cases that may benefit from indexing or
providing information for a transfer
receiver_id: the valid NEAR account receiving the token
token_id: the token to transfer
approval_id: expected approval ID. A number smaller than
2^53, and therefore representable as JSON. See Approval Management
standard for full explanation.
memo (optional): for use cases that may benefit from indexing or
providing information for a transfer
receiver_id: the valid NEAR account receiving the token
token_id: the token to transfer
approval_id: expected approval ID. A number smaller than
2^53, and therefore representable as JSON. See Approval Management
standard for full explanation.
memo (optional): for use cases that may benefit from indexing or
providing information for a transfer
Transfer token and call a method on a receiver contract. A successful
workflow will end in a success execution outcome to the callback on the NFT
contract at the method nft_resolve_transfer.
You can think of this as being similar to attaching native NEAR tokens to a
function call. It allows you to attach any Non-Fungible Token in a call to a
receiver contract.
Requirements:
Caller of the method must attach a deposit of 1 yoctoⓃ for security
purposes
Contract MUST panic if called by someone other than token owner or,
if using Approval Management, one of the approved accounts
The receiving contract must implement ft_on_transfer according to the
standard. If it does not, FT contract's ft_resolve_transfer MUST deal
with the resulting failed cross-contract call and roll back the transfer.
Contract MUST implement the behavior described in ft_resolve_transfer
approval_id is for use with Approval Management extension, see
that document for full explanation.
If using Approval Management, contract MUST nullify approved accounts on
successful transfer.
Arguments:
receiver_id: the valid NEAR account receiving the token.
token_id: the token to send.
approval_id: expected approval ID. A number smaller than
2^53, and therefore representable as JSON. See Approval Management
standard for full explanation.
memo (optional): for use cases that may benefit from indexing or
providing information for a transfer.
msg: specifies information needed by the receiving contract in
order to properly handle the transfer. Can indicate both a function to
call and the parameters to pass to that function.
Transfer token and call a method on a receiver contract. A successful
workflow will end in a success execution outcome to the callback on the NFT
contract at the method nft_resolve_transfer.
You can think of this as being similar to attaching native NEAR tokens to a
function call. It allows you to attach any Non-Fungible Token in a call to a
receiver contract.
Requirements:
Caller of the method must attach a deposit of 1 yoctoⓃ for security
purposes
Contract MUST panic if called by someone other than token owner or,
if using Approval Management, one of the approved accounts
The receiving contract must implement ft_on_transfer according to the
standard. If it does not, FT contract's ft_resolve_transfer MUST deal
with the resulting failed cross-contract call and roll back the transfer.
Contract MUST implement the behavior described in ft_resolve_transfer
approval_id is for use with Approval Management extension, see
that document for full explanation.
If using Approval Management, contract MUST nullify approved accounts on
successful transfer.
Arguments:
receiver_id: the valid NEAR account receiving the token.
token_id: the token to send.
approval_id: expected approval ID. A number smaller than
2^53, and therefore representable as JSON. See Approval Management
standard for full explanation.
memo (optional): for use cases that may benefit from indexing or
providing information for a transfer.
msg: specifies information needed by the receiving contract in
order to properly handle the transfer. Can indicate both a function to
call and the parameters to pass to that function.
Transfer token and call a method on a receiver contract. A successful
workflow will end in a success execution outcome to the callback on the NFT
contract at the method nft_resolve_transfer.
You can think of this as being similar to attaching native NEAR tokens to a
function call. It allows you to attach any Non-Fungible Token in a call to a
receiver contract.
Requirements:
Caller of the method must attach a deposit of 1 yoctoⓃ for security
purposes
Contract MUST panic if called by someone other than token owner or,
if using Approval Management, one of the approved accounts
The receiving contract must implement ft_on_transfer according to the
standard. If it does not, FT contract's ft_resolve_transfer MUST deal
with the resulting failed cross-contract call and roll back the transfer.
Contract MUST implement the behavior described in ft_resolve_transfer
approval_id is for use with Approval Management extension, see
that document for full explanation.
If using Approval Management, contract MUST nullify approved accounts on
successful transfer.
Arguments:
receiver_id: the valid NEAR account receiving the token.
token_id: the token to send.
approval_id: expected approval ID. A number smaller than
2^53, and therefore representable as JSON. See Approval Management
standard for full explanation.
memo (optional): for use cases that may benefit from indexing or
providing information for a transfer.
msg: specifies information needed by the receiving contract in
order to properly handle the transfer. Can indicate both a function to
call and the parameters to pass to that function.
Remove whitelisted account. If account is removed, the number of tokens left in returned.
allow
["::admins", "::owner"]
Parameters
args: { account_id: string }
account_id: string
Optional options: ChangeMethodOptions
Returns Action
start_presale
start_presale(args: { presale_price?: string; public_sale_start?: number }, options?: ChangeMethodOptions): Promise<boolean>
Override the current presale start time to start presale now.
Most provide when public sale starts. None, means never.
Can provide new presale price.
Note: you most likely won't need to call this since the presale
starts automatically based on time.
allow
["::admins", "::owner"]
Parameters
args: { presale_price?: string; public_sale_start?: number }
Optional presale_price?: string
Optional public_sale_start?: number
Optional options: ChangeMethodOptions
Returns Promise<boolean>
start_presaleRaw
start_presaleRaw(args: { presale_price?: string; public_sale_start?: number }, options?: ChangeMethodOptions): Promise<FinalExecutionOutcome>
Override the current presale start time to start presale now.
Most provide when public sale starts. None, means never.
Can provide new presale price.
Note: you most likely won't need to call this since the presale
starts automatically based on time.
allow
["::admins", "::owner"]
Parameters
args: { presale_price?: string; public_sale_start?: number }
Optional presale_price?: string
Optional public_sale_start?: number
Optional options: ChangeMethodOptions
Returns Promise<FinalExecutionOutcome>
start_presaleTx
start_presaleTx(args: { presale_price?: string; public_sale_start?: number }, options?: ChangeMethodOptions): Action
Override the current presale start time to start presale now.
Most provide when public sale starts. None, means never.
Can provide new presale price.
Note: you most likely won't need to call this since the presale
starts automatically based on time.
allow
["::admins", "::owner"]
Parameters
args: { presale_price?: string; public_sale_start?: number }
Add a new admin. Careful who you add!
["::admins", "::owner"]