ERC721Proxy

October 28, 2019 ยท View on GitHub

Transferring ERC-721 tokens

The ERC721Proxy is responsible for transferring ERC-721 tokens. Users must first approve this contract by calling the approve or setApprovalForAll methods on the token that will be exchanged. setApprovalForAll is highly recommended, because it allows the user to approve multiple tokenIds with a single transaction.

transferFrom

This contract may transfer an ERC-721 token if its transferFrom method is called from an authorized address.

/// @dev Transfers assets. Either succeeds or throws.
/// @param assetData Byte array encoded for the respective asset proxy.
/// @param from Address to transfer asset from.
/// @param to Address to transfer asset to.
/// @param amount Amount of asset to transfer.
function transferFrom(
    bytes assetData,
    address from,
    address to,
    uint256 amount
)
    external;

Logic

Calling ERC721Proxy.transferFrom will perform the following steps:

  1. Decode erc721TokenAddress and tokenId from assetData
  2. Call ERC721Token(erc721TokenAddress).transferFrom(from, to, tokenId)
  3. Revert if the call was unsuccessful

Errors

The transferFrom method may revert with the following errors:

ErrorCondition
StandardError("SENDER_NOT_AUTHORIZED")msg.sender has not been authorized
StandardError("INVALID_AMOUNT")The amount does not equal 1
StandardError("TRANSFER_FAILED")The ERC721Token.transferFrom call failed for any reason (likely insufficient balance/allowance)

Encoding assetData

This contract expects ERC-721 assetData to be encoded using ABIv2 with the following function signature. The id of this contract is 0x02571792, which can be calculated as the 4 byte function selector of the same signature.

/// @dev Function signature for encoding ERC-721 assetData.
/// @param tokenAddress Address of ERC-721 token contract.
/// @param tokenId Id of ERC-721 token to be transferred.
function ERC721Token(
    address tokenAddress,
    uint256 tokenId
)
    external;

In Solidity, this data can be encoded with:

bytes memory data = abi.encodeWithSelector(
    0x02571792,
    erc721TokenAddress,
    tokenId
);

NOTE: The ERC721Proxy does not enforce strict length checks for assetData, which means that extra data may be appended to this field with any arbitrary encoding. Any extra data will be ignored by the ERC721Proxy but may be used in external contracts interacting with the Exchange contract. Relayers that do not desire this behavior should validate the length of all assetData fields contained in orders before acceptance.

Authorizations

The ERC721Proxy has the following interface for managing which addresses are allowed to call this contract's transferFrom method. These authorization functions can only be called by the contract's owner (currently, the ZeroExGovernor contract).

contract IAuthorizable {

    /// @dev Gets all authorized addresses.
    /// @return Array of authorized addresses.
    function getAuthorizedAddresses()
        external
        view
        returns (address[]);

    /// @dev Authorizes an address.
    /// @param target Address to authorize.
    function addAuthorizedAddress(address target)
        external;

    /// @dev Removes authorizion of an address.
    /// @param target Address to remove authorization from.
    function removeAuthorizedAddress(address target)
        external;

    /// @dev Removes authorizion of an address.
    /// @param target Address to remove authorization from.
    /// @param index Index of target in authorities array.
    function removeAuthorizedAddressAtIndex(
        address target,
        uint256 index
    )
        external;
}

The contracts that are currently authorized to call the ERC20Proxy contract's transferFrom method are: