Managing Orders
Build, approve, sign, fill, cancel and save orders with the Swap SDK.
There are two ways to build orders with the 0x v4 Swap SDK,
buildOrder and buildNftAndErc20Order
buildOrder() accepts the traditional order format (specifying maker and taker assets). import { NftSwapV4 } from '@traderxyz/nft-swap-sdk';
const nftSwapSdk = new NftSwapV4(provider, signer, chainId);
const CRYPTOPUNK_420 = {
tokenAddress: '0xb47e3cd837ddf8e4c57f05d70ab865de6e193bbb', // CryptoPunk contract address
tokenId: '420', // Token Id of the CryptoPunk we want to swap
type: 'ERC721', // Must be one of 'ERC20', 'ERC721', or 'ERC1155'
};
const SIXTY_NINE_USDC = {
tokenAddress: '0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48', // USDC contract address
amount: '69000000', // 69 USDC (USDC is 6 digits)
type: 'ERC20',
};
const walletAddressUserA = '0x1eeD19957E0a81AED9a80f09a3CCEaD83Ea6D86b';
const order = nftSwapSdk.buildOrder(
nftToSwapUserA,
usdcToSwapUserB,
walletAddressUserA
);
buildNftAndErc20Order() accepts the new order format, where you specify an nft, an erc20 and a sell direction ('sell' if the maker of the trade is selling the nft, 'buy' if the maker of the trade is buying the nft)const order = nftSwapSdk.buildNftAndErc20Order(
nftToSwapUserA,
usdcToSwapUserB,
'sell',
walletAddressOfUserA
);
Approvals are required to move tokens and NFTs to and from accounts, and in general to fill orders. Before executing a trade, both parties will need to have approved the 0x v4 Exchange Contract.
To approve an asset, call the
approveTokenOrNftByAsset function.Pass it the NFT or ERC20 you need to approve
const CRYPTOPUNK = {
tokenAddress: '0xb47e3cd837ddf8e4c57f05d70ab865de6e193bbb',
tokenId: '69',
type: 'ERC721', // Must be one of 'ERC20', 'ERC721', or 'ERC1155'
};
await nftSwapSdk.approveTokenOrNftByAsset(CRYPTOPUNK, walletAddress);
Once you've built an order, for it to be valid (and for it to be able to be filled by someone) it needs to be signed. The maker of the order signs the order, and the taker will fill the signed order.
After building an order via
buildOrder or buildNftAndErc20Order dpass the order object to the signOrder function to sign and confirm your order. Once signed, this order is active and can be filled as long as it is valid.const signedOrder = await nftSwapSdk.signOrder(order);
Now that we have a signed order, another wallet can fill that order (known as 'taking' the trade).
To fill order, pass the signed order to the Swap SDK to the
fillSignedOrder function.If the transaction succeeds, the trade went through, and the user can be notified.
const fillTx = await nftSwapperMaker.fillSignedOrder(signedOrder);
const txReceipt = await fillTx.wait();
console.log('Filled order! 🎉', txReceipt.transactionHash);
To cancel an order, call the
cancelOrder function on the Swap SDK and pass it the order:await nftSwapSdk.cancelOrder(nonce, orderType);
// Where `orderType` is either 'ERC721' | 'ERC1155'
// And `nonce` is from the order object
Being able to cancel by nonce allows us to do some cool things with regard to order cancellations.
Documentation coming soon
Swap SDK offers integrators their own free, publicly hosted orderbook to use for their application. This allows developers to persist orders off-chain without having to manage any additional infrastructure. Leverage the power of off-chain orders without any of the work!
To save an order to the hosted orderbook:
await nftSwapSdk.postOrder(signedOrder);
To fetch order(s) from the orderbook, you can use the SDK.
// Search the orderbook for all offers to sell this NFT (CryptoCoven #9757)
const orders = await nftSwap.getOrders({
nftToken: "0x5180db8f5c931aae63c74266b211f580155ecac8",
nftTokenId: "9757",
sellOrBuyNft: "sell", // Only show asks (sells) for this NFT (excludes asks)
});
// Or search by unique nonce
const orders = await nftSwap.getOrders({
nonce: "0x31f42841c2db5173425b5223809cf3a38fede360",
});ype
Developers can always bring their own orderbook/order persistance infrastructure if they'd prefer. There is no lock in for using the hosted orderbook.
Last modified 9mo ago