NFT Transfer

The nftTransfer() function creates a user operation for transferring NFTs. This function initiates the process of transferring an NFT by encoding the necessary parameters into a User Operation, which can then be signed and executed using the OktoClient.

Available on

Ethereum

Polygon

Avalanche

Arbitrum

BSC

Fantom

Linea

Metis

Optimism

Base

Polygon Amoy

To enable these chains for your application, please configure them in the Okto Dashboard.

Not available on

Base Sepolia

HyperEVM Testnet

There are two ways to implement NFT transfers:

Abstracted Flow: A simplified approach where the user operation is automatically created, signed, and executed in a single step. Perfect for most applications.
UserOp Flow: A granular approach where you manually control the creation, signing, and execution of the user operation. Useful for custom implementations or advanced use cases.

Example

import { nftTransfer } from "@okto_web3/core-js-sdk"; 
 
async function handleNFTTransfer() {
    try {
        const transferParams = { 
            caip2Id: "eip155:1", // Ethereum Mainnet 
            collectionAddress: "0x23581767a106ae21c074b2276D25e5C3e136a68b", 
            nftId: "123", // NFT token ID 
            recipientWalletAddress: "0x742d35Cc6634C0532925a3b844Bc454e4438f44e", 
            amount: 1, 
            nftType: 'ERC721'
        }; 
        
        // Execute the transfer
        const jobId = await nftTransfer(oktoClient, transferParams); 
        console.log('Transfer jobId:', jobId);
    } catch (error) {
        console.error('Error in NFT transfer:', error);
    }
}

Note

For error handling:

Use the error code to debug issues. Check out the SDK errors and warnings documentation
For help, navigate to the troubleshooting guide to contact support

Method Overview

Method	Description
_async `nftTransfer`	Create a user operation for NFT transfer

NFT Transfer

_async nftTransfer(oktoClient: OktoClient, data: NFTTransferIntentParams) creates a user operation for transferring NFTs.

Parameters

Parameter	Type	Description	Required
`oktoClient`	`OktoClient`	Instance of OktoClient	Yes
`data`	`NFTTransferIntentParams`	Parameters for the NFT transfer	Yes

Where NFTTransferIntentParams contains:

Field	Type	Description	Required
`caip2Id`	`string`	The network identifier, formatted as a CAIP network ID	Yes
`collectionAddress`	`Address`	The address of the NFT collection	Yes
`nftId`	`string`	The unique identifier of the NFT	Yes
`recipientWalletAddress`	`Address`	The wallet address of the recipient	Yes
`amount`	`number \| bigint`	The amount of NFTs to transfer, typically "1"	Yes
`nftType`	`'ERC721' \| 'ERC1155'`	The type of NFT standard	Yes

Response

Success Response

Field Name	Type	Description
`result`	`Promise<string>`	Returns the jobId for the NFT transfer

NFT Transfer

Example

Usage

Sample Response

Suggested Post Implementation

Corresponding jobId Response

Method Overview

NFT Transfer

Parameters

Response

Response Type

On this page