contextwtf / nfte Goto Github PK

I got the Error -- Request failed with status code 400

I see that ERC-721 is supported but I am unable to troubleshoot support for hash.pob.studio $HASH tokens. Let me know if this is a non-issue and I'll close and continue to troubleshoot 💪🏻

• Contract Address: 0xE18a32192ED95b0FE9D70D19e5025f103475d7BA

@dave4506

Trying to pin down this issue, very likely it's my NPM configuration, but wanted to ask.

Is it possible to add opensea as a known contract?

Would be cool for NFTE to support sidechains like Polygon

One Rarible contract address works with NFTE endpoint: 0x60f80121c31a0d46b5279700f9df786054aa5ee5

(Example item: https://rarible.com/token/0x60f80121c31a0d46b5279700f9df786054aa5ee5:335911?tab=details)

(Working request: https://nfte.app/api/embed.js?contract=0x60f80121c31a0d46b5279700f9df786054aa5ee5&tokenId=335911)

An alternative Rarible address is not included in knowncontracts/Rarible.js and fails: 0xd07dc4262bcdbf85190c01c996b4c06a461d2430

(Example item: https://rarible.com/token/0xd07dc4262bcdbf85190c01c996b4c06a461d2430:542153?tab=history)

(Failing request: https://nfte.app/api/embed.js?contract=0xd07dc4262bcdbf85190c01c996b4c06a461d2430&tokenId=542153)

Loving the NFTE service, thanks so much for creating it

I have been using the NFTE Data function to retrieve a json object and wrap my own embed.
Recnetly Foundation stopped working and I am trying to track down the issue, here is an example output

{ "contract": "0x3B3ee1931Dc30C1957379FAc9aba94D1C48a5405", "tokenId": "23473", "metadata": { "name": "Deep Blue", "description": "Rafaël Rozendaal\n2021", "image": "ipfs://QmaqMPDQ2C9XWSVEB31JQLqkQLPnZbnysyUZvBauCn2cuu/nft.mp4" }, "name": "Deep Blue", "description": "Rafaël Rozendaal\n2021", "ownerOf": "0xcDA72070E455bb31C7690a170224Ce43623d0B6f", "ownerOfUrl": "https://etherscan.io/address/0xcDA72070E455bb31C7690a170224Ce43623d0B6f", "creatorOf": "0x0F441cFaD93287109F5eF834bF52F4aaaa8d8ffa", "creatorOfUrl": "https://etherscan.io/address/0x0F441cFaD93287109F5eF834bF52F4aaaa8d8ffa", "platform": "Foundation", "platformUrl": "https://foundation.app", "mediaUrl": "https://gateway.pinata.cloud/ipfs/nft.mp4", "mediaPageUrl": "https://foundation.app/nft/nft-23473", "mediaMimeType": "text/plain; charset=utf-8", "blockNumber": 12226975, "timestamp": 1618253638, "media": "https://gateway.pinata.cloud/ipfs/nft.mp4", "mintedBy": "Foundation", "mintedByUrl": "https://foundation.app", "minted": "2021-04-12T18:53:58.000Z" }

the mediaurl now points to https://gateway.pinata.cloud/ipfs/nft.mp4 which is odd. Could be of course on the foundation side of things.

First off, huge work so far. This is great.

It could be useful to have an example in the documentation on how to self-host the Next API route. For instance, if it could be possible to import it into an API route within my Next build, and update a prop or environment variable so it uses my endpoint instead of the nfte.app endpoint?

When using the NFTE React component, started getting some {error: "Cannot retrieve nft data"} this afternoon.

Not sure if I misconfigured something, of if your https://nfte.app/api is overloaded at the moment

Hey @sammdec!

When attempting to load an NFT from Foundation it does not appear to correctly return the media. Here is an example of the returned data from the NFTE API. You can see below that media is a generic placeholder. Did something change on Foundation’s end which would cause this to break?

{
  contract: '0x3B3ee1931Dc30C1957379FAc9aba94D1C48a5405',
  tokenId: '25621',
  metadata: {
    name: 'Chrysalide II — Monarch',
    description: 'Digital Composition\n1/1\n3600x3600',
    image: 'ipfs://QmeYre1gcRHniBJiiTxUxbLfCs5BbFKW36BawamF6446Zo/nft.png'
  },
  name: 'Chrysalide II — Monarch',
  description: 'Digital Composition\n1/1\n3600x3600',
  ownerOf: 'erichu.eth',
  ownerOfUrl: 'https://etherscan.io/address/0x4628D77ba8fCc7a7F2B6bd4A0363061a06E7a20F',
  creatorOf: 'erichu.eth',
  creatorOfUrl: 'https://etherscan.io/address/0x4628D77ba8fCc7a7F2B6bd4A0363061a06E7a20F',
  platform: 'Foundation',
  platformUrl: 'https://foundation.app',
  mediaUrl: 'https://gateway.pinata.cloud/ipfs/nft.png',
  mediaPageUrl: 'https://etherscan.io/address/0x3B3ee1931Dc30C1957379FAc9aba94D1C48a5405?a=25621',
  mediaMimeType: 'text/plain; charset=utf-8',
  blockNumber: 12262016,
  timestamp: 1618720712,
  media: 'https://gateway.pinata.cloud/ipfs/nft.png',
  mintedBy: 'Foundation',
  mintedByUrl: 'https://foundation.app'
}

I'd like to create a customized embed (using the React component). My primary interest is creating a custom box size, but exposing other style/layout CSS features to the top level component would also be really helpful.
If I understand correctly, the only way to change embed size currently is to copy the contents of components/Embed.jsx into my own custom component, since the max-height/max-width and aspect values aren't exposed to the top level props. Maybe there's a way to achieve this I haven't yet discovered?