The EIP is a Redeemable NFT extension which adds a redeem function to EIP-721. It can be implemented when an NFT issuer wants his/her NFT to be redeemed for a physical object.
An increasing amount of NFT issuers such as artists, fine art galeries, auction houses, brands and others want to offer a physical object to the holder of a given NFT. This standard allows EIP-721 NFTs to signal reedemability.
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.
EIP-721 compliant contracts MAY implement this EIP to provide a standard method of receiving information on redeemability.
The NFT issuer MUST decide who is allowed to redeem the NFT, and restrict access to the redeem() function accordingly.
Anyone MAY access the isRedeemable() function to check the redeemability status: it returns true when the NFT redeemable, and false when already redeemed.
Third-party services that support this standard MAY use the Redeem event to listen to changes on the redeemable status of the NFT.
Implementers of this standard MUST have all of the following functions:
The Redeem event is emitted when the redeem() function is called.
The supportsInterface method MUST return true when called with 0x2f8ca953.
When the NFT contract is deployed, the isRedeemable() function returns true by default.
By default, the redeem() function visibility is public, so anyone can trigger it. It is RECOMMENDED to add a require to restrict the access:
After the redeem() function is triggered, isRedeemable() function returns false.
Redeem eventWhen the redeem() function is triggered, the following event MUST be emitted:
This standard is compatible with EIP-721.
Here's an example of an EIP-721 that includes the Redeemable extension:
Needs discussion.
Copyright and related rights waived via CC0.