I have a question if Someone could help with it .. it will be super! Why some words with the same numbers of letters , have differents dates of auction ended? For example according to Open Sea eth Auctions Names with 5 letters will finalized in 2 days, but You can notice that some others Names in Auction like pimco.eth will finalized in 4 days... So... Why this happens? Why Names with the same numbers of letters have a different duration?
Posted by Varyea 4 months ago
As I understand, whenever I make an order I have to sign it by my private-key with ECDSA algorithm. But when I store my ERC721 tokens in a multisig-wallet, I can make orders because the multisig-wallet can not sign. Do you support EIP1271(https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1271.md)?
Posted by Phu 4 months ago
Oops, the Ethereum network rejected this transaction :( The OpenSea devs have been alerted, but this problem is typically due an item being locked or untransferrable. The exact error was "The execution failed due to an exception...." Whats the reason for this? It appears when I want to accept an offer made to one of my items....
Posted by Crypto Wizard 5 months ago
Hi there, I am currently working on an ERC-721 which generates images on the fly. My api sends the information to OpenSea ok, (checked with `/validate`) but the image doesn't seem to be showing. I am sending a stringified svg with escaped `\"`'s in the `image_raw` field. Are there any examples of how the svg data should be sent down?
Posted by Nic Smith 6 months ago
I get this error when trying to buy an item - Ethereum network rejected the transaction. Item being locked or untransferrable - Exact error: gas required exceed allowance or always failing transaction
Posted by Alvaro A Pinzon C Pinzon 9 months ago
rinkeby-api.opensea.io/asset_contract/0x1C4C47F305deB95c775971F4D00cD76d90007332/create/:1 Failed to load resource: the server responded with a status of 500 () Reply More Options GET /asset_contract/0x1C4C47F305deB95c775971F4D00cD76d90007332/create/ HTTP 405 Method Not Allowed Allow: OPTIONS, POST Content-Type: application/json Vary: Accept { "detail": "Method "GET" not allowed." }
Posted by Anou Mana 9 months ago
Hi, I'm trying to create a burnable ERC721 token. So far I've called the openzeppelin ERC721Burnable contract and added the functions as well. My contract deploys just fine, but I am having trouble understanding how to 'trigger' the burn. In the the tutorial we are using 'mint.js' to mint tokens, could a similar thing, like 'burn.js', be created to handle burning? Is there an implementation of this by the opensea team (probably asking for too much here, ha). Is this the preferred implementation to burn, since we are using mint.js to mint? How would I pass the correct token ID to burn?
Posted by jay sun 9 months ago
Hi There, I have a Dapp whose metadata resides on blockchain itself. We do not use external URLs for our metadata as we want it to be public and changes can be tracked. We have 3 JSONs that can be fetched using a smart contract function `getWeaponMetaData(weaponid)`. How can I get listed here and see my data as well? Don't you guys support fetching data directly from the smart contract?
Posted by Prashant Prabhakar Singh 9 months ago
First of all, loved the tutorial and the project! I'm new to smart contract developing and followed along just fine. I used the open-sea-creature api (https://opensea-creatures-api.herokuapp.com/api/creature/) to populate the metadata of my NFT's (success!). I then tried to change the URI in Creature.sol to point to my own API. I then tried to migrate the contract w/ truffle, but cant get it to use the updated URI. I realized, since the blockchain is immutable does that mean I cannot change anything in the Creature.sol contract? Basically, if you're making a project, once you've set the API link it's over and cannot be changed right ? I'd have to deploy a new smart contract to mess with these attributes?
Posted by go0t 9 months ago
Some of our new cards seem to be missing metadata, but the json file is present on our server where it should be. Did maybe something go wrong when the new tokens were minted and the tokenURI didn't stick? Can you guys see a tokenURI for this one: https://opensea.io/assets/0x4e01124b127ae8d0573efc4a026d9d7505fcd5bb/206 Thanks
Posted by Kevin Phillips 10 months ago
The OpenSea validator returned a message that my ERC-721 contract on rinkeby did not meet the standard. I'm using Zepkit and I was pretty sure it was legit. I looked for a validator, but I only found one for mainnet. Is there a way to get more detailed info for troubleshooting?
Posted by Chris Lumpkin 10 months ago