A standard interface for contracts that manage multiple token types. A single deployed contract may include any combination of fungible tokens, non-fungible tokens or other configurations (e.g. semi-fungible tokens).
This standard outlines a smart contract interface that can represent any number of fungible and non-fungible token types. Existing standards such as OIP-20 require deployment of separate contracts per token type. The OIP-721 standard’s token ID is a single non-fungible index and the group of these non-fungibles is deployed as a single contract with settings for the entire collection. In contrast, the OIP-1155 Multi Token Standard allows for each token ID to represent a new configurable token type, which may have its own metadata, supply and other attributes.
The _id argument contained in each function’s argument set indicates a specific token or token type in a transaction.
Tokens standards like OIP-20 and OIP-721 require a separate contract to be deployed for each token type or collection. This places a lot of redundant bytecode on the OKB Chain and limits certain functionality by the nature of separating each token contract into its own permissioned address. With the rise of blockchain games and platforms like Enjin Coin, game developers may be creating thousands of token types, and a new type of token standard is needed to support them. However, OIP-1155 is not specific to games and many other applications can benefit from this flexibility.
New functionality is possible with this design such as transferring multiple token types at once, saving on transaction costs. Trading (escrow / atomic swaps) of multiple tokens can be built on top of this standard and it removes the need to “approve” individual token contracts separately. It is also easy to describe and mix multiple fungible or non-fungible token types in a single contract.
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119. Smart contracts implementing the OIP-1155 standard MUST implement all of the functions in the OIP1155 interface. Smart contracts implementing the OIP-1155 standard MUST implement the OIP-165 supportsInterface function and MUST return the constant value true if 0xd9b67a26 is passed through the interfaceID argument.
pragma solidity ^0.5.9;
/**
@title OIP-1155 Multi Token Standard
@dev See https://OIPs.readthedocs.io/en/latest/draft/OIP-1155.html
Note: The OIP-165 identifier for this interface is 0xd9b67a26.
*/
interface OIP1155 /* is OIP165 */ {
/**
@dev Either `TransferSingle` or `TransferBatch` MUST emit when tokens are transferred, including zero value transfers as well as minting or burning (see "Safe Transfer Rules" section of the standard).
The `_operator` argument MUST be the address of an account/contract that is approved to make the transfer (SHOULD be msg.sender).
The ```_from``` argument MUST be the address of the holder whose balance is decreased.
The `_to` argument MUST be the address of the recipient whose balance is increased.
The `_id` argument MUST be the token type being transferred.
The `_value` argument MUST be the number of tokens the holder balance is decreased by and match what the recipient balance is increased by.
When minting/creating tokens, the ```_from``` argument MUST be set to `0x0` (i.e. zero address).
When burning/destroying tokens, the `_to` argument MUST be set to `0x0` (i.e. zero address).
*/
event TransferSingle(address indexed _operator, address indexed ``_from``, address indexed _to, uint256 _id, uint256 _value);
/**
@dev Either `TransferSingle` or `TransferBatch` MUST emit when tokens are transferred, including zero value transfers as well as minting or burning (see "Safe Transfer Rules" section of the standard).
The `_operator` argument MUST be the address of an account/contract that is approved to make the transfer (SHOULD be msg.sender).
The ```_from``` argument MUST be the address of the holder whose balance is decreased.
The `_to` argument MUST be the address of the recipient whose balance is increased.
The ``_ids`` argument MUST be the list of tokens being transferred.
The ``_values`` argument MUST be the list of number of tokens (matching the list and order of tokens specified in `_ids`) the holder balance is decreased by and match what the recipient balance is increased by.
When minting/creating tokens, the ```_from``` argument MUST be set to `0x0` (i.e. zero address).
When burning/destroying tokens, the `_to` argument MUST be set to `0x0` (i.e. zero address).
*/
event TransferBatch(address indexed _operator, address indexed ``_from``, address indexed _to, uint256[] `_ids`, uint256[] `_values`);
/**
@dev MUST emit when approval for a second party/operator address to manage all tokens for an owner address is enabled or disabled (absence of an event assumes disabled).
*/
event ApprovalForAll(address indexed _owner, address indexed _operator, bool _approved);
/**
@dev MUST emit when the URI is updated for a token ID.
URIs are defined in RFC 3986.
The URI MUST point to a JSON file that conforms to the "OIP-1155 Metadata URI JSON Schema".
*/
event URI(string _value, uint256 indexed _id);
/**
@notice Transfers `_value` amount of an `_id` from the ```_from``` address to the `_to` address specified (with safety call).
@dev Caller must be approved to manage the tokens being transferred out of the ```_from``` account (see "Approval" section of the standard).
MUST revert if `_to` is the zero address.
MUST revert if balance of holder for token `_id` is lower than the `_value` sent.
MUST revert on any other error.
MUST emit the `TransferSingle` event to reflect the balance change (see "Safe Transfer Rules" section of the standard).
After the above conditions are met, this function MUST check if `_to` is a smart contract (e.g. code size > 0). If so, it MUST call `onOIP1155Received` on `_to` and act appropriately (see "Safe Transfer Rules" section of the standard).
@param ``_from`` Source address
@param _to Target address
@param _id ID of the token type
@param _value Transfer amount
@param `_data` Additional data with no specified format, MUST be sent unaltered in call to `onOIP1155Received` on `_to`
*/
function safeTransferFrom(address ``_from``, address _to, uint256 _id, uint256 _value, bytes calldata `_data`) external;
/**
@notice Transfers ``_values`` amount(s) of ``_ids`` from the ```_from``` address to the `_to` address specified (with safety call).
@dev Caller must be approved to manage the tokens being transferred out of the ```_from``` account (see "Approval" section of the standard).
MUST revert if `_to` is the zero address.
MUST revert if length of ``_ids`` is not the same as length of ``_values``.
MUST revert if any of the balance(s) of the holder(s) for token(s) in ``_ids`` is lower than the respective amount(s) in ``_values`` sent to the recipient.
MUST revert on any other error.
MUST emit `TransferSingle` or `TransferBatch` event(s) such that all the balance changes are reflected (see "Safe Transfer Rules" section of the standard).
Balance changes and events MUST follow the ordering of the arrays (`_ids`[0]/`_values`[0] before `_ids`[1]/`_values`[1], etc).
After the above conditions for the transfer(s) in the batch are met, this function MUST check if `_to` is a smart contract (e.g. code size > 0). If so, it MUST call the relevant ``OIP1155TokenReceiver`` hook(s) on `_to` and act appropriately (see "Safe Transfer Rules" section of the standard).
@param ``_from`` Source address
@param _to Target address
@param `_ids` IDs of each token type (order and length must match `_values` array)
@param `_values` Transfer amounts per token type (order and length must match `_ids` array)
@param `_data` Additional data with no specified format, MUST be sent unaltered in call to the ``OIP1155TokenReceiver`` hook(s) on `_to`
*/
function safeBatchTransferFrom(address ``_from``, address _to, uint256[] calldata `_ids`, uint256[] calldata `_values`, bytes calldata `_data`) external;
/**
@notice Get the balance of an account's tokens.
@param _owner The address of the token holder
@param _id ID of the token
@return The _owner's balance of the token type requested
*/
function balanceOf(address _owner, uint256 _id) external view returns (uint256);
/**
@notice Get the balance of multiple account/token pairs
@param _owners The addresses of the token holders
@param `_ids` ID of the tokens
@return The _owner's balance of the token types requested (i.e. balance for each (owner, id) pair)
*/
function balanceOfBatch(address[] calldata _owners, uint256[] calldata `_ids`) external view returns (uint256[] memory);
/**
@notice Enable or disable approval for a third party ("operator") to manage all of the caller's tokens.
@dev MUST emit the ApprovalForAll event on success.
@param _operator Address to add to the set of authorized operators
@param _approved True if the operator is approved, false to revoke approval
*/
function setApprovalForAll(address _operator, bool _approved) external;
/**
@notice Queries the approval status of an operator for a given owner.
@param _owner The owner of the tokens
@param _operator Address of authorized operator
@return True if the operator is approved, false if not
*/
function isApprovedForAll(address _owner, address _operator) external view returns (bool);
}
Smart contracts MUST implement all of the functions in the OIP1155TokenReceiver interface to accept transfers. See “Safe Transfer Rules” for further detail.Smart contracts MUST implement the OIP-165 supportsInterface function and signify support for the OIP1155TokenReceiver interface to accept transfers. See “OIP1155TokenReceiver OIP-165 rules” for further detail.
pragma solidity ^0.5.9;
/**
Note: The OIP-165 identifier for this interface is 0x4cffff8a.
*/
interface `OIP1155TokenReceiver` {
/**
@notice Handle the receipt of a single OIP1155 token type.
@dev An OIP1155-compliant smart contract MUST call this function on the token recipient contract, at the end of a `safeTransferFrom` after the balance has been updated.
This function MUST return `bytes4(keccak256("onOIP1155Received(address,address,uint256,uint256,bytes)"))` (i.e. 0xa12d61b5) if it accepts the transfer.
This function MUST revert if it rejects the transfer.
Return of any other value than the prescribed keccak256 generated value MUST result in the transaction being reverted by the caller.
@param _operator The address which initiated the transfer (i.e. msg.sender)
@param ``_from`` The address which previously owned the token
@param _id The ID of the token being transferred
@param _value The amount of tokens being transferred
@param `_data` Additional data with no specified format
@return `bytes4(keccak256("onOIP1155Received(address,address,uint256,uint256,bytes)"))`
*/
function onOIP1155Received(address _operator, address ``_from``, uint256 _id, uint256 _value, bytes calldata `_data`) external returns(bytes4);
/**
@notice Handle the receipt of multiple OIP1155 token types.
@dev An OIP1155-compliant smart contract MUST call this function on the token recipient contract, at the end of a `safeBatchTransferFrom` after the balances have been updated.
This function MUST return `bytes4(keccak256("onOIP1155BatchReceived(address,address,uint256[],uint256[],bytes)"))` (i.e. 0xedd29e3f) if it accepts the transfer(s).
This function MUST revert if it rejects the transfer(s).
Return of any other value than the prescribed keccak256 generated value MUST result in the transaction being reverted by the caller.
@param _operator The address which initiated the batch transfer (i.e. msg.sender)
@param ``_from`` The address which previously owned the token
@param `_ids` An array containing ids of each token being transferred (order and length must match `_values` array)
@param `_values` An array containing amounts of each token being transferred (order and length must match `_ids` array)
@param `_data` Additional data with no specified format
@return `bytes4(keccak256("onOIP1155BatchReceived(address,address,uint256[],uint256[],bytes)"))`
*/
function onOIP1155BatchReceived(address _operator, address ``_from``, uint256[] calldata `_ids`, uint256[] calldata `_values`, bytes calldata `_data`) external returns(bytes4);
}
To be more explicit about how the standard safeTransferFrom and safeBatchTransferFrom functions MUST operate with respect to the OIP1155TokenReceiver hook functions, a list of scenarios and rules follows.
onOIP1155Received and onOIP1155BatchReceived MUST NOT be called on an EOA (Externally Owned Account).
Scenario#2 : The transaction is not a mint/transfer of a token.
onOIP1155Received and onOIP1155BatchReceived MUST NOT be called outside of a mint or transfer process.
Scenario#3 : The receiver does not implement the necessary OIP1155TokenReceiver interface function(s).
The transfer MUST be reverted with the one caveat below.
If the token(s) being sent are part of a hybrid implementation of another standard, that particular standard’s rules on sending to a contract MAY now be followed instead. See “Backwards Compatibility” section.
Scenario#4 :The receiver implements the necessary OIP1155TokenReceiver interface function(s) but returns an unknown value.
The transfer MUST be reverted.
Scenario#5 : The receiver implements the necessary OIP1155TokenReceiver interface function(s) but throws an error.
The transfer MUST be reverted.
Scenario#6 : The receiver implements the OIP1155TokenReceiver interface and is the recipient of one and only one balance change (e.g. safeTransferFrom called).
The balances for the transfer MUST have been updated before the OIP1155TokenReceiver hook is called on a recipient contract.
The transfer event MUST have been emitted to reflect the balance changes before the OIP1155TokenReceiver hook is called on the recipient contract.
One of onOIP1155Received or onOIP1155BatchReceived MUST be called on the recipient contract.
The onOIP1155Received hook SHOULD be called on the recipient contract and its rules followed.
See “onOIP1155Received rules” for further rules that MUST be followed.
The onOIP1155BatchReceived hook MAY be called on the recipient contract and its rules followed.
See “onOIP1155BatchReceived rules” for further rules that MUST be followed.
Scenario#7 : The receiver implements the OIP1155TokenReceiver interface and is the recipient of more than one balance change (e.g. safeBatchTransferFrom called).
All balance transfers that are referenced in a call to an OIP1155TokenReceiver hook MUST be updated before the OIP1155TokenReceiver hook is called on the recipient contract.
All transfer events MUST have been emitted to reflect current balance changes before an OIP1155TokenReceiver hook is called on the recipient contract.
onOIP1155Received or onOIP1155BatchReceived MUST be called on the recipient as many times as necessary such that every balance change for the recipient in the scenario is accounted for.
The return magic value for every hook call MUST be checked and acted upon as per “onOIP1155Received rules” and “onOIP1155BatchReceived rules”.
The onOIP1155BatchReceived hook SHOULD be called on the recipient contract and its rules followed.
See “onOIP1155BatchReceived rules” for further rules that MUST be followed.
The onOIP1155Received hook MAY be called on the recipient contract and its rules followed.
See “onOIP1155Received rules” for further rules that MUST be followed.
Scenario#8 : You are the creator of a contract that implements the OIP1155TokenReceiver interface and you forward the token(s) onto another address in one or both of onOIP1155Received and onOIP1155BatchReceived.
Forwarding should be considered acceptance and then initiating a new safeTransferFrom or safeBatchTransferFrom in a new context.
The prescribed keccak256 acceptance value magic for the receiver hook being called MUST be returned after forwarding is successful.
The _data argument MAY be re-purposed for the new context.
If forwarding fails the transaction MAY be reverted.
If the contract logic wishes to keep the ownership of the token(s) itself in this case it MAY do so.
Scenario#9 : You are transferring tokens via a non-standard API call i.e. an implementation specific API and NOT safeTransferFrom or safeBatchTransferFrom.
In this scenario all balance updates and events output rules are the same as if a standard transfer function had been called.
i.e. an external viewer MUST still be able to query the balance via a standard function and it MUST be identical to the balance as determined by TransferSingle and TransferBatch events alone.
If the receiver is a contract the OIP1155TokenReceiver hooks still need to be called on it and the return values respected the same as if a standard transfer function had been called.
However while the safeTransferFrom or safeBatchTransferFrom functions MUST revert if a receiving contract does not implement the OIP1155TokenReceiver interface, a non-standard function MAY proceed with the transfer.
Caller must be approved to manage the tokens being transferred out of the _from account (see “Approval” section).
MUST revert if _to is the zero address.
MUST revert if balance of holder for token _id is lower than the _value sent to the recipient.
MUST revert on any other error.
MUST emit the TransferSingle event to reflect the balance change (see “TransferSingle and TransferBatch event rules” section).
After the above conditions are met, this function MUST check if _to is a smart contract (e.g. code size > 0). If so, it MUST call onOIP1155Received on _to and act appropriately (see “onOIP1155Received rules” section).
The _data argument provided by the sender for the transfer MUST be passed with its contents unaltered to the onOIP1155Received hook function via its _data argument.
safeBatchTransferFrom rules:
Caller must be approved to manage all the tokens being transferred out of the _from account (see “Approval” section).
MUST revert if _to is the zero address.
MUST revert if length of _ids is not the same as length of _values.
MUST revert if any of the balance(s) of the holder(s) for token(s) in _ids is lower than the respective amount(s) in _values sent to the recipient.
MUST revert on any other error.
MUST emit TransferSingle or TransferBatch event(s) such that all the balance changes are reflected (see “TransferSingle and TransferBatch event rules” section).
The balance changes and events MUST occur in the array order they were submitted (_ids[0]/_values[0] before _ids[1]/_values[1], etc).
After the above conditions are met, this function MUST check if _to is a smart contract (e.g. code size > 0). If so, it MUST call onOIP1155Received or onOIP1155BatchReceived on _to and act appropriately (see “onOIP1155Received and onOIP1155BatchReceived rules” section).
The _data argument provided by the sender for the transfer MUST be passed with its contents unaltered to the OIP1155TokenReceiver hook function(s) via their _data argument.
TransferSingle and TransferBatch event rules:
TransferSingle SHOULD be used to indicate a single balance transfer has occurred between a _from and _to pair.
It MAY be emitted multiple times to indicate multiple balance changes in the transaction, but note that TransferBatch is designed for this to reduce gas consumption.
The _operator argument MUST be the address of an account/contract that is approved to make the transfer (SHOULD be msg.sender).
The _from argument MUST be the address of the holder whose balance is decreased.
The _to argument MUST be the address of the recipient whose balance is increased.
The _id argument MUST be the token type being transferred.
The _value argument MUST be the number of tokens the holder balance is decreased by and match what the recipient balance is increased by.
When minting/creating tokens, the _from argument MUST be set to 0x0 (i.e. zero address). See “Minting/creating and burning/destroying rules”.
When burning/destroying tokens, the _to argument MUST be set to 0x0 (i.e. zero address). See “Minting/creating and burning/destroying rules”.
TransferBatch SHOULD be used to indicate multiple balance transfers have occurred between a _from and _to pair.
It MAY be emitted with a single element in the list to indicate a singular balance change in the transaction, but note that TransferSingle is designed for this to reduce gas consumption.
The _operator argument MUST be the address of an account/contract that is approved to make the transfer (SHOULD be msg.sender).
The _from argument MUST be the address of the holder whose balance is decreased for each entry pair in _ids and _values.
The _to argument MUST be the address of the recipient whose balance is increased for each entry pair in _ids and _values.
The _ids array argument MUST contain the ids of the tokens being transferred.
The _values array argument MUST contain the number of token to be transferred for each corresponding entry in _ids.
_ids and _values MUST have the same length.
When minting/creating tokens, the _from argument MUST be set to 0x0 (i.e. zero address). See “Minting/creating and burning/destroying rules”.
When burning/destroying tokens, the _to argument MUST be set to 0x0 (i.e. zero address). See “Minting/creating and burning/destroying rules”.
The total value transferred from address 0x0 minus the total value transferred to 0x0 observed via the TransferSingle and TransferBatch events MAY be used by clients and exchanges to determine the “circulating supply” for a given token ID.
To broadcast the existence of a token ID with no initial balance, the contract SHOULD emit the TransferSingle event from 0x0 to 0x0, with the token creator as _operator, and a _value of 0.
All TransferSingle and TransferBatch events MUST be emitted to reflect all the balance changes that have occurred before any call(s) to onOIP1155Received or onOIP1155BatchReceived.
To make sure event order is correct in the case of valid re-entry (e.g. if a receiver contract forwards tokens on receipt) state balance and events balance MUST match before calling an external contract.
onOIP1155Received rules:
The _operator argument MUST be the address of an account/contract that is approved to make the transfer (SHOULD be msg.sender).
The _from argument MUST be the address of the holder whose balance is decreased.
_from MUST be 0x0 for a mint.
The _id argument MUST be the token type being transferred.
The _value argument MUST be the number of tokens the holder balance is decreased by and match what the recipient balance is increased by.
The _data argument MUST contain the information provided by the sender for the transfer with its contents unaltered.
i.e. it MUST pass on the unaltered _data argument sent via the safeTransferFrom or safeBatchTransferFrom call for this transfer.
The recipient contract MAY accept an increase of its balance by returning the acceptance magic value bytes4(keccak256("onOIP1155Received(address,address,uint256,uint256,bytes)"))
If the return value is bytes4(keccak256("onOIP1155Received(address,address,uint256,uint256,bytes)")) the transfer MUST be completed or MUST revert if any other conditions are not met for success.
The recipient contract MAY reject an increase of its balance by calling revert.
If the recipient contract throws/reverts the transaction MUST be reverted.
If the return value is anything other than bytes4(keccak256("onOIP1155Received(address,address,uint256,uint256,bytes)")) the transaction MUST be reverted.
onOIP1155Received (and/or onOIP1155BatchReceived) MAY be called multiple times in a single transaction and the following requirements must be met:
All callbacks represent mutually exclusive balance changes.
The set of all calls to onOIP1155Received and onOIP1155BatchReceived describes all balance changes that occurred during the transaction in the order submitted.
A contract MAY sOIP calling the onOIP1155Received hook function if the transfer operation is transferring the token to itself. onOIP1155BatchReceived rules:
The _operator argument MUST be the address of an account/contract that is approved to make the transfer (SHOULD be msg.sender).
The _from argument MUST be the address of the holder whose balance is decreased.
_from MUST be 0x0 for a mint.
The _ids argument MUST be the list of tokens being transferred.
The _values argument MUST be the list of number of tokens (matching the list and order of tokens specified in _ids) the holder balance is decreased by and match what the recipient balance is increased by.
The _data argument MUST contain the information provided by the sender for the transfer with its contents unaltered.
i.e. it MUST pass on the unaltered _data argument sent via the safeBatchTransferFrom call for this transfer.
The recipient contract MAY accept an increase of its balance by returning the acceptance magic value bytes4(keccak256("onOIP1155BatchReceived(address,address,uint256[],uint256[],bytes)"))
If the return value is bytes4(keccak256("onOIP1155BatchReceived(address,address,uint256[],uint256[],bytes)")) the transfer MUST be completed or MUST revert if any other conditions are not met for success.
The recipient contract MAY reject an increase of its balance by calling revert.
If the recipient contract throws/reverts the transaction MUST be reverted.
If the return value is anything other than bytes4(keccak256("onOIP1155BatchReceived(address,address,uint256[],uint256[],bytes)")) the transaction MUST be reverted.
onOIP1155BatchReceived (and/or onOIP1155Received) MAY be called multiple times in a single transaction and the following requirements must be met:
All callbacks represent mutually exclusive balance changes.
The set of all calls to onOIP1155Received and onOIP1155BatchReceived describes all balance changes that occurred during the transaction in the order submitted.
A contract MAY sOIP calling the onOIP1155BatchReceived hook function if the transfer operation is transferring the token(s) to itself. OIP1155TokenReceiver OIP-165 rules:
The implementation of the OIP-165 supportsInterface function SHOULD be as follows:
function supportsInterface(bytes4 interfaceID) external view returns (bool) {
return interfaceID == 0x01ffc9a7 || // OIP-165 support (i.e. `bytes4(keccak256('supportsInterface(bytes4)'))`).
interfaceID == 0x4cffff8a; // OIP-1155 ``OIP1155TokenReceiver`` support (i.e. `bytes4(keccak256("onOIP1155Received(address,address,uint256,uint256,bytes)")) ^ bytes4(keccak256("onOIP1155BatchReceived(address,address,uint256[],uint256[],bytes)"))`).
}
The implementation MAY differ from the above but:
It MUST return the constant value true if 0x01ffc9a7 is passed through the interfaceID argument. This signifies OIP-165 support.
It MUST return the constant value true if 0x4cffff8a is passed through the interfaceID argument. This signifies OIP-1155 OIP1155TokenReceiver support.
It MUST NOT consume more than 10,000 gas.
This keeps it below the OIP-165 requirement of 30,000 gas, reduces the gas reserve needs and minimises possible side-effects of gas exhaustion during the call.
Implementation specific transfer API rules:
If an implementation specific API function is used to transfer OIP-1155 token(s) to a contract, the safeTransferFrom or safeBatchTransferFrom (as appropriate) rules MUST still be followed if the receiver implements the OIP1155TokenReceiver interface. If it does not the non-standard implementation SHOULD revert but MAY proceed.
An example:
An approved user calls a function such as function myTransferFrom(address _from, address _to, uint256[] calldata _ids, uint256[] calldata _values);.
myTransferFrom updates the balances for _from and _to addresses for all _ids and _values.
myTransferFrom emits TransferBatch with the details of what was transferred from address _from to address _to.
myTransferFrom checks if _to is a contract address and determines that it is so (if not, then the transfer can be considered successful).
myTransferFrom calls onOIP1155BatchReceived on _to and it reverts or returns an unknown value (if it had returned bytes4(keccak256("onOIP1155BatchReceived(address,address,uint256[],uint256[],bytes)")) the transfer can be considered successful).
At this point myTransferFrom SHOULD revert the transaction immediately as receipt of the token(s) was not explicitly accepted by the onOIP1155BatchReceived function.
If however myTransferFrom wishes to continue it MUST call supportsInterface(0x4cffff8a) on _to and if it returns the constant value true the transaction MUST be reverted, as it is now known to be a valid receiver and the previous acceptance step failed.
NOTE: You could have called supportsInterface(0x4cffff8a) at a previous step if you wanted to gather and act upon that information earlier, such as in a hybrid standards scenario.
If the above call to supportsInterface(0x4cffff8a) on _to reverts or returns a value other than the constant value true the myTransferFrom function MAY consider this transfer successful.
NOTE: this MAY result in unrecoverable tokens if sent to an address that does not expect to receive OIP-1155 tokens.
The above example is not exhaustive but illustrates the major points (and shows that most are shared with safeTransferFrom and safeBatchTransferFrom):
Balances that are updated MUST have equivalent transfer events emitted.
A receiver address has to be checked if it is a contract and if so relevant OIP1155TokenReceiver hook function(s) have to be called on it.
Balances (and events associated) that are referenced in a call to an OIP1155TokenReceiver hook MUST be updated (and emitted) before the OIP1155TokenReceiver hook is called.
The return values of the OIP1155TokenReceiver hook functions that are called MUST be respected if they are implemented.
Only non-standard transfer functions MAY allow tokens to be sent to a recipient contract that does NOT implement the necessary OIP1155TokenReceiver hook functions. safeTransferFrom and safeBatchTransferFrom MUST revert in that case (unless it is a hybrid standards implementation see “Backwards Compatibility”).
Minting/creating and burning/destroying rules:
A mint/create operation is essentially a specialized transfer and MUST follow these rules:
To broadcast the existence of a token ID with no initial balance, the contract SHOULD emit the TransferSingle event from 0x0 to 0x0, with the token creator as _operator, and a _value of 0.
The “TransferSingle and TransferBatch event rules” MUST be followed as appropriate for the mint(s) (i.e. singles or batches) however the _from argument MUST be set to 0x0 (i.e. zero address) to flag the transfer as a mint to contract observers.
NOTE: This includes tokens that are given an initial balance in the contract. The balance of the contract MUST also be able to be determined by events alone meaning initial contract balances (for eg. in construction) MUST emit events to reflect those balances too.
A burn/destroy operation is essentially a specialized transfer and MUST follow these rules:
The “TransferSingle and TransferBatch event rules” MUST be followed as appropriate for the burn(s) (i.e. singles or batches) however the _to argument MUST be set to 0x0 (i.e. zero address) to flag the transfer as a burn to contract observers.
When burning/destroying you do not have to actually transfer to 0x0 (that is impl specific), only the _to argument in the event MUST be set to 0x0 as above.
The total value transferred from address 0x0 minus the total value transferred to 0x0 observed via the TransferSingle and TransferBatch events MAY be used by clients and exchanges to determine the “circulating supply” for a given token ID.
As mentioned above mint/create and burn/destroy operations are specialized transfers and so will likely be accomplished with custom transfer functions rather than safeTransferFrom or safeBatchTransferFrom. If so the “Implementation specific transfer API rules” section would be appropriate.
Even in a non-safe API and/or hybrid standards case the above event rules MUST still be adhered to when minting/creating or burning/destroying.
A contract MAY sOIP calling the OIP1155TokenReceiver hook function(s) if the mint operation is transferring the token(s) to itself. In all other cases the OIP1155TokenReceiver rules MUST be followed as appropriate for the implementation (i.e. safe, custom and/or hybrid). A solidity example of the keccak256 generated constants for the various magic values (these MAY be used by implementation):
bytes4 constant public OIP1155_OIP165 = 0xd9b67a26; // OIP-165 identifier for the main token standard.
bytes4 constant public OIP1155_OIP165_TOKENRECEIVER = 0x4cffff8a; // OIP-165 identifier for the `OIP1155TokenReceiver` support (i.e. `bytes4(keccak256("onOIP1155Received(address,address,uint256,uint256,bytes)")) ^ bytes4(keccak256("onOIP1155BatchReceived(address,address,uint256[],uint256[],bytes)"))`).
bytes4 constant public OIP1155_ACCEPTED = 0xa12d61b5; // Return value from `onOIP1155Received` call if a contract accepts receipt (i.e `bytes4(keccak256("onOIP1155Received(address,address,uint256,uint256,bytes)"))`).
bytes4 constant public OIP1155_BATCH_ACCEPTED = 0xedd29e3f; // Return value from `onOIP1155BatchReceived` call if a contract accepts receipt (i.e `bytes4(keccak256("onOIP1155BatchReceived(address,address,uint256[],uint256[],bytes)"))`).
The URI value allows for ID substitution by clients. If the string {id} exists in any URI, clients MUST replace this with the actual token ID in hexadecimal form. This allows for a large number of tokens to use the same on-chain string by defining a URI once, for that large number of tokens.
The string format of the substituted hexadecimal ID MUST be lowOIPase alphanumeric: [0-9a-f] with no 0x prefix.
The string format of the substituted hexadecimal ID MUST be leading zero padded to 64 hex characters length if necessary.
Example of such a URI: https://token-cdn-domain/{id}.json would be replaced with https://token-cdn-domain/000000000000000000000000000000000000000000000000000000000004cce0.json if the client is referring to token ID 314592/0x4CCE0.
The optional OIP1155Metadata_URI extension can be identified with the OIP-165 Standard Interface Detection .
If the optional OIP1155Metadata_URI extension is included:
The OIP-165 supportsInterface function MUST return the constant value true if 0x0e89341c is passed through the interfaceID argument.
Changes to the URI MUST emit the URI event if the change can be expressed with an event (i.e. it isn’t dynamic/programmatic).
An implementation MAY emit the URI event during a mint operation but it is NOT mandatory. An observer MAY fetch the metadata uri at mint time from the uri function if it was not emitted.
The uri function SHOULD be used to retrieve values if no event was emitted.
The uri function MUST return the same value as the latest event for an _id if it was emitted.
The uri function MUST NOT be used to check for the existence of a token as it is possible for an implementation to return a valid string even if the token does not exist.
pragma solidity ^0.5.9;
/**
Note: The OIP-165 identifier for this interface is 0x0e89341c.
*/
interface OIP1155Metadata_URI {
/**
@notice A distinct Uniform Resource Identifier (URI) for a given token.
@dev URIs are defined in RFC 3986.
The URI MUST point to a JSON file that conforms to the "OIP-1155 Metadata URI JSON Schema".
@return URI string
*/function uri(uint256 _id) external view returns (string memory);
}
This JSON schema is loosely based on the “OIP721 Metadata JSON Schema”, but includes optional formatting to allow for ID substitution by clients. If the string {id} exists in any JSON value, it MUST be replaced with the actual token ID, by all client software that follows this standard.
The string format of the substituted hexadecimal ID MUST be lowOIPase alphanumeric: [0-9a-f] with no 0x prefix.
The string format of the substituted hexadecimal ID MUST be leading zero padded to 64 hex characters length if necessary.
{
"title": "Token Metadata",
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Identifies the asset to which this token represents"
},
"decimals": {
"type": "integer",
"description": "The number of decimal places that the token amount should display - e.g. 18, means to divide the token amount by 1000000000000000000 to get its user representation."
},
"description": {
"type": "string",
"description": "Describes the asset to which this token represents"
},
"image": {
"type": "string",
"description": "A URI pointing to a resource with mime type image/* representing the asset to which this token represents. Consider making any images at a width between 320 and 1080 pixels and aspect ratio between 1.91:1 and 4:5 inclusive."
},
"properties": {
"type": "object",
"description": "Arbitrary properties. Values may be strings, numbers, object or arrays."
}
}
}
An example of an OIP-1155 Metadata JSON file follows. The properties array proposes some SUGGESTED formatting for token-specific display properties and metadata.
Metadata localization should be standardized to increase presentation uniformity across all languages. As such, a simple overlay method is proposed to enable localization. If the metadata JSON file contains a localization attribute, its content MAY be used to provide localized values for fields that need it. The localization attribute should be a sub-object with three attributes: uri, default and locales. If the string {locale} exists in any URI, it MUST be replaced with the chosen locale by all client software.
JSON Schema
{
"title": "Token Metadata",
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Identifies the asset to which this token represents",
},
"decimals": {
"type": "integer",
"description": "The number of decimal places that the token amount should display - e.g. 18, means to divide the token amount by 1000000000000000000 to get its user representation."
},
"description": {
"type": "string",
"description": "Describes the asset to which this token represents"
},
"image": {
"type": "string",
"description": "A URI pointing to a resource with mime type image/* representing the asset to which this token represents. Consider making any images at a width between 320 and 1080 pixels and aspect ratio between 1.91:1 and 4:5 inclusive."
},
"properties": {
"type": "object",
"description": "Arbitrary properties. Values may be strings, numbers, object or arrays.",
},
"localization": {
"type": "object",
"required": ["uri", "default", "locales"],
"properties": {
"uri": {
"type": "string",
"description": "The URI pattern to fetch localized data from. This URI should contain the substring `{locale}` which will be replaced with the appropriate locale value before sending the request."
},
"default": {
"type": "string",
"description": "The locale of the default data within the base JSON"
},
"locales": {
"type": "array",
"description": "The list of locales for which data is available. These locales should conform to those defined in the Unicode Common Locale Data Repository (http://cldr.unicode.org/)."
}
}
}
}
}
Localized Sample
Base URI:
{
"name": "Advertising Space",
"description": "Each token represents a unique Ad space in the city.",
"localization": {
"uri": "ipfs://QmWS1VAdMD353A6SDk9wNyvkT14kyCiZrNDYAad4w1tKqT/{locale}.json",
"default": "en",
"locales": ["en", "es", "fr"]
}
}
es.json:
{
"name": "Espacio Publicitario",
"description": "Cada token representa un espacio publicitario único en la ciudad."
}
fr.json:
{
"name": "Espace Publicitaire",
"description": "Chaque jeton représente un espace publicitaire unique dans la ville."
}
The function setApprovalForAll allows an operator to manage one’s entire set of tokens on behalf of the approver. The counterpart isApprovedForAll , which provides introspection into any status set by setApprovalForAll.
An owner SHOULD be assumed to always be able to operate on their own tokens regardless of approval status, so should SHOULD NOT have to call setApprovalForAll to approve themselves as an operator before they can operate on them.
The symbol function (found in the OIP-20 and OIP-721 standards) was not included as we do not believe this is a globally useful piece of data to identify a generic virtual item / asset and are also prone to collisions. Short-hand symbols are used in tickers and currency trading, but they aren’t as useful outside of that space.
The name function (for human-readable asset names, on-chain) was removed from the standard to allow the Metadata JSON to be the definitive asset name and reduce duplication of data. This also allows localization for names, which would otherwise be prohibitively expensive if each language string was stored on-chain, not to mention bloating the standard interface. While this decision may add a small burden on implementers to host a JSON file containing metadata, we believe any serious implementation of OIP-1155 will already utilize JSON Metadata.
The requirement to emit TransferSingle or TransferBatch on balance change implies that a valid implementation of OIP-1155 redeploying to a new contract address MUST emit events from the new contract address to replicate the deprecated contract final state. It is valid to only emit a minimal number of events to reflect only the final balance and omit all the transactions that led to that state. The event emit requirement is to ensure that the current state of the contract can always be traced only through events. To alleviate the need to emit events when changing contract address, consider using the proxy pattern. This will also have the added benefit of providing a stable contract address for users.
The standard supports safeTransferFrom and onOIP1155Received functions because they are significantly cheaper for single token-type transfers, which is arguably a common use case.
The standard only supports safe-style transfers, making it possible for receiver contracts to depend on onOIP1155Received or onOIP1155BatchReceived function to be always called at the end of a transfer.
As the OKB Chain ecosystem continues to grow, many dapps are relying on traditional databases and explorer API services to retrieve and categorize data. The OIP-1155 standard guarantees that event logs emitted by the smart contract will provide enough data to create an accurate record of all current token balances. A database or explorer may listen to events and be able to provide indexed and categorized searches of every OIP-1155 token in the contract.
The function setApprovalForAll allows an operator to manage one’s entire set of tokens on behalf of the approver. It enables frictionless interaction with exchange and trade contracts.
Restricting approval to a certain set of token IDs, quantities or other rules MAY be done with an additional interface or an external contract. The rationale is to keep the OIP-1155 standard as generic as possible for all use-cases without imposing a specific approval scheme on implementations that may not need it. Standard token approval interfaces can be used.
There have been requirements during the design discussions to have this standard be compatible with existing standards when sending to contract addresses, specifically OIP-721 at time of writing. To cater for this scenario, there is some leeway with the revert logic should a contract not implement the OIP1155TokenReceiver as per “Safe Transfer Rules” section above, specifically “Scenario#3 : The receiver does not implement the necessary OIP1155TokenReceiver interface function(s)”.
Hence in a hybrid OIP-1155 contract implementation an extra call MUST be made on the recipient contract and checked before any hook calls to onOIP1155Received or onOIP1155BatchReceived are made. Order of operation MUST therefore be:
The implementation MUST call the function supportsInterface(0x4cffff8a) on the recipient contract, providing at least 10,000 gas.
If the function call succeeds and the return value is the constant value true the implementation proceeds as a regular OIP-1155 implementation, with the call(s) to the onOIP1155Received or onOIP1155BatchReceived hooks and rules associated.
If the function call fails or the return value is NOT the constant value true the implementation can assume the recipient contract is not an OIP1155TokenReceiver and follow its other standard’s rules for transfers.
Note that a pure implementation of a single standard is recommended rather than a hybrid solution, but an example of a hybrid OIP-1155/OIP-721 contract is linked in the references section under implementations.
An important consideration is that even if the tokens are sent with another standard’s rules the OIP-1155 transfer events MUST still be emitted. This is so the balances can still be determined via events alone as per OIP-1155 standard rules.
This standard can be used to represent multiple token types for an entire domain. Both fungible and non-fungible tokens can be stored in the same smart-contract.
The safeBatchTransferFrom function allows for batch transfers of multiple token IDs and values. The design of OIP-1155 makes batch transfers possible without the need for a wrapper contract, as with existing token standards. This reduces gas costs when more than one token type is included in a batch transfer, as compared to single transfers with multiple transactions.
Another advantage of standardized batch transfers is the ability for a smart contract to respond to the batch transfer in a single operation using onOIP1155BatchReceived.
In order to keep storage requirements light for contracts implementing OIP-1155, enumeration (discovering the IDs and values of tokens) must be done using event logs. It is RECOMMENDED that clients such as exchanges and blockchain explorers maintain a local database containing the token ID, Supply, and URI at the minimum. This can be built from each TransferSingle, TransferBatch, and URI event, starting from the block the smart contract was deployed until the latest block.
OIP-1155 contracts must therefore carefully emit TransferSingle or TransferBatch events in any instance where tokens are created, minted, transferred or destroyed.
The following strategies are examples of how you MAY mix fungible and non-fungible tokens together in the same contract. The standard does NOT mandate how an implementation must do this.
The top 128 bits of the uint256 _id parameter in any OIP-1155 function MAY represent the base token ID, while the bottom 128 bits MAY represent the index of the non-fungible to make it unique.
Non-fungible tokens can be interacted with using an index based accessor into the contract/token data set. Therefore to access a particular token set within a mixed data contract and a particular non-fungible within that set, _id could be passed as <uint128: base token id><uint128: index of non-fungible>.
To identify a non-fungible set/category as a whole (or a fungible) you COULD just pass in the base id via the _id argument as <uint128: base token id><uint128: zero>. If your implementation uses this technique this naturally means the index of a non-fungible SHOULD be 1-based.
Inside the contract code the two pieces of data needed to access the individual non-fungible can be extracted with uint128(~0) and the same mask shifted by 128.
uint256 baseTokenNFT = 12345 << 128;
uint128 indexNFT = 50;
uint256 baseTokenFT = 54321 << 128;
balanceOf(baseTokenNFT, msg.sender); // Get balance of the base token for non-fungible set 12345 (this MAY be used to get balance of the user for all of this token set if the implementation wishes as a convenience).
balanceOf(baseTokenNFT + indexNFT, msg.sender); // Get balance of the token at index 50 for non-fungible set 12345 (should be 1 if user owns the individual non-fungible token or 0 if they do not).
balanceOf(baseTokenFT, msg.sender); // Get balance of the fungible base token 54321.
Note that 128 is an arbitrary number, an implementation MAY choose how they would like this split to occur as suitable for their use case. An observer of the contract would simply see events showing balance transfers and mints happening and MAY track the balances using that information alone. For an observer to be able to determine type (non-fungible or fungible) from an ID alone they would have to know the split ID bits format on a implementation by implementation basis.
Another simple way to represent non-fungibles is to allow a maximum value of 1 for each non-fungible token. This would naturally mirror the real world, where unique items have a quantity of 1 and fungible items have a quantity greater than 1.
