Ether Rock Wrapper
If you own a rock, you can use this page to wrap it so it can be sold on Opensea and other marketplaces. Wrapping your rock means it gets turned into an ERC721 token which these marketplaces require. To wrap your rock, you have to transfer it to the wrapper contract (after the wrapper contract knows you're the owner of the rock), and any subsequent trading of the rock on marketplaces like Opensea will be done through this wrapper contract. At any time you can unwrap your rock and have the wrapper contract send it back to you so you'll be recorded as the owner in the Ether Rock contract again (unless someone buys it from you on Opensea, after which only they will be able to unwrap it).
Here are the 3 steps for wrapping a rock:
- Make sure the wrapper contract knows you are listed as the current owner of the rock ID you want to wrap (it probably already does). This page will check if this is the case when you enter a rock ID below, but you can also manually check yourself by going to the wrapper contract page on Etherscan and entering your rock ID in the '2. checkIfUpdateRequired' section (should return false) and the '3. checkOwnerRecord' section (should return your Ethereum address).
- Send your rock to the wrapper contract through the Ether Rock contract. This involves calling the giftRock() function in the Ether Rock contract. You can double check that the transaction is interacting with the Ether Rock contract, it's calling giftRock(), and it is sending your rock to the wrapper contract. If you're using MetaMask, your transaction details should be the same as the red highlights in this image.
- Call the wrap() function in the wrapper contract to have your rock ID wrapped.
Enter your rock ID below to get started.
Status: You are not connected to the Ethereum mainnet. Make sure you're using something like MetaMask and are connected to the Ethereum mainnet, then refresh this page.
NB: While the wrapper contract has been reviewed by several solidity developers and has had an open bug bounty since 16 September, it hasn't been professionally audited. While no serious issues have been found by the numerous people who have combed over it, there still remains a possibility (however small) that there's an unfound bug.